Vibecape documentation
Start with local Spaces, documents, and Chat, then add collaboration, extensions, or a server when needed.
Vibecape is a local-first workspace for documents, repositories, context, and AI agents. Content remains in ordinary files on your computer. Start with a local Space, then add collaboration only when you need it.
Choose a path
- First time in the app: start with The App and local Spaces, then complete your first document and Chat workflow.
- Everyday work: learn the document tree and editor, Chat with documents, and import, sharing, and backup.
- Configure capabilities: see Settings, models, and troubleshooting and Extensions and Skills.
- Team collaboration: follow Collaboration getting started, then learn about accounts, Groups, and Remote Spaces.
- Hosting collaboration: follow Vibecape Server to initialize a server, create a Group, and approve membership requests.
- Customizing the workspace: build an extension or connect custom models.
- Working from a terminal: use the CLI reference.
How collaboration fits together
There are two servers with different responsibilities:
- A Downcity Federation identifies the user and issues the login session.
- A Vibecape Server manages Groups, membership, Spaces, repositories, and sync authorization.
The Vibecape App uses your Federation account to request access to a Group. After a server administrator approves the request, the Group's Spaces appear in the App. The Vibecape Server does not issue a second user account or a second token.
Local-first by default
Remote Spaces are full local Git clones. You can edit while offline and use editors, agents, shell tools, or Git tools directly. Synchronization checkpoints local changes, fetches remote work, integrates it, and pushes when your role allows it.
Phase 1 stores text and ordinary images in Git and rejects any single file larger than 20 MiB. Video and other large assets will use Git LFS in a later phase.