Nexus
Documents, project boards, and agent collaboration in a Markdown workspace.
Nexus brings documents, project work, and agent collaboration into one workspace. Your content stays in Markdown files; folders, boards, and structured fields help you work with those files without turning every note into a database record.
Choose a vault
A vault is the boundary for team membership and access. Put ordinary projects in folders inside your team’s vault. Use a separate vault when the work needs different ownership or access.
When collaborating across organizations, choose the vault that should own the project’s source documents. Being a member of two vaults does not merge their permissions or automatically share their contents.
Organize a project
A project folder can contain an overview, notes, tasks, a board, and supporting material. The overview is an ordinary index.md file. In the app, the folder and overview appear as one navigation entry; local tools can still address the file directly.
You can start with a plain note and add structure when it becomes useful. A document does not need fields, a board membership, or an agent connection to be useful.
Use the app or local files
Nexus’s API is authoritative for shared state. The desktop app maintains a synchronized local working copy that local tools can use. A file saved on your Mac is not necessarily synchronized yet: check sync status before relying on another device or collaborator seeing the change.
If synchronization needs review, inspect the affected files instead of overwriting one side. Keep local credentials and Nexus synchronization metadata out of ordinary documents.
Continue
-
Set up a Nexus vault: create a vault, connect your agent, and invite your team.
-
Nexus quick start: context → ticket → agent → reviewed result.