Projects

A project is a repo, like github.com/acme/web. It has its own secrets, the connections its agents see, personal files and conversations.

Make one#

On the dashboard, open the switcher at the top left and choose Create project: pick repos from GitHub (after connecting it) or type one. Or in a clone:

0b project link

0b project link makes the repo a project and points that clone's Claude Code, Codex and Cursor at the project's own endpoint, https://0bridge.dev/mcp/p/<id>. Run it in each clone. The token it writes only opens that project.

Connections per project#

On the dashboard, open a connection's ⋯ menu → Scope and turn off Everywhere to pick the projects it's for. It then disappears everywhere else, claude.ai included. A project's Connections tab shows which ones its agents get. From a clone:

0b project use slack --label acme
0b project unuse slack --label acme

The other way round: keep a connection everywhere but out of one project, like another company's Slack in this company's repo. In the project's Connections tab, ⋯ → Hide here (or in Scope, check the projects under Except in). From a clone:

0b project hide slack --label other-company
0b project show slack --label other-company

Strict#

A strict project's agents see only its own connections, not the global ones, and their conversation search stays in the repo. Good for a company repo: its agents can't reach your personal accounts.

0b project strict on

Where the files go: Claude Code keeps the project endpoint in ~/.claude.json for that folder; Codex in .codex/config.toml and Cursor in .cursor/mcp.json in the clone, kept out of git. Codex reads it once you trust the folder.