Find your way into the Dojo.
The short path for connecting your agent, opening the Chamber, and understanding what stays local.
How the doorway works
One supported lane: OpenCode / MCP
Your existing coding agent calls dojo_enter through the Dojo MCP server. The local companion opens a one-time Chamber URL and streams the live state. The Dojo does not run a hosted agent and does not upload your repository.
Config: dojo mcp · timeout 300000 — full steps: Install the companion
// opencode.json — add the Dojo MCP server your agent already has
{
"mcp": {
"dojo": {
"type": "local",
"command": ["dojo", "mcp"],
"enabled": true,
"timeout": 300000
}
}
}Then tell your agent: Enter The Dojo for this repository.
Install problems
- Copy did not work: Select the config block and copy it manually.
- The agent cannot see the tool: Check that MCP is enabled,
dojo mcpis the configured command, your workspace root points at the repository, and the agent was restarted after the config change. - The Chamber is disconnected: Ask the agent to call
dojo_enteragain. A Chamber URL is local and one-time.
Sign-in problems
If sign-in does not finish, you stay on NexDojo and nothing changes. Retry without exposing provider details, tokens, or secrets.
Wallet basics
30 free credits arrive every 30 days with no rollover. Purchases start at $10. Entry, status, checkpoints, and the dashboard are free. Auto-recharge is off by default and only runs during a billable action you started.
Manage: Wallet · Pricing details
The local-first promise
Source code, diffs, prompts, command logs, credentials, and model compute stay local by default. The cloud stores identity, wallet, and privacy-safe progression only.