Command reference

Run 0b --help for everything; the ones you'll use most:

• 0b setup: sign in and add 0bridge to every AI tool
• 0b status: is this machine and this repo set up? A checklist with the command that fixes each item. Ask your agent to "set up this repo" and it runs this, does the safe fixes and tells you the rest
• 0b connect <name or address>: connect any service (--label, --spec, --api). In your terminal it lists the ways in to pick from: its MCP server (sign in in the browser), its API (you type the key; it stays with 0bridge) or its CLI (wrangler, gh: signed in to a profile on this machine). 0bridge's own connector is picked first, then the service's own MCP server; other people's servers are shown only when the service has nothing of its own. 0b key <service> adds an API's key
• 0b cloud: your connections
• 0b project link: make this repo a project and point its tools at it
• 0b project use <service>: limit a connection to this project
• 0b secret import .env [--dry-run] [--only A,B], 0b exec -- <cmd> (sets ZEROBRIDGE_ENV): secrets
• 0b secret off|on|note <NAME>
• 0b vault unlock: open your vault on a new machine
• 0b files add <file>, 0b files pull: personal files
• 0b history on, 0b history search <words>
• 0b clip, 0b clip listen on: the clipboard
• 0b profile add <name> wrangler gh, 0b profile use <name>: which CLI accounts this repo uses. A wrangler that's only in the repo's node_modules works too. Over SSH, paste the localhost address the browser ends on after you approve, and 0b passes it to the login on this machine
• 0b background on: sync history and files every 30 minutes (a background job on macOS; elsewhere it prints the crontab line to add)

Several Claude Code accounts#

A second Claude Code account run with CLAUDE_CONFIG_DIR=~/.claude-b gets what ~/.claude gets: 0b apply writes 0bridge, your MCP servers, skills and instructions there too, and 0b project link adds the project endpoint to that account's settings. Any ~/.claude-* folder Claude Code has used (it has a .claude.json) counts, as does CLAUDE_CONFIG_DIR itself.

Several 0bridge accounts#

A company's 0bridge account and your own can both be signed in. 0b login while signed in adds another account; 0b account lists them, 0b account use <email> picks the default (the one every AI tool's 0bridge entry uses) and 0b logout <email> signs one out. A repo linked with 0b project link --account <email> belongs to that account: its AI tools use that account's project, and repo commands run inside it (connect, secret, exec, project, …) use that account on their own. --account <email> works on any command.

In the dashboard, the account menu lists the accounts signed in in this browser, switches between them and adds another. The consent screen claude.ai and ChatGPT open, and the 0b login approval screen, show which account you're using and switch right there. An app that already has your consent goes straight to the account that's active in the browser, so switch first to connect it to another.