DotbrainPrivate context for coding agents
Give each coding agent your project's decisions, vocabulary, and issues. Keep that context versioned and outside your code repo.
Skip to content
The repo stays clean
Each project's Brain and issue tracker live under ~/dotbrain/. Gitignored links and generated runtime files connect the code repo to that private home, so agents load the context at session start and private material stays out of commits.
Context that carries work forward
The Brain keeps project knowledge, the design captures current intent, and Beads tracks the issues. Focused skills connect them throughout the work.
Load the context
Start from the project's vocabulary and decisions. Surface constraints and open questions before changing code.
Settle the design
Record the approach, unknowns, and success criteria in a living design. Turn it into scoped issues.
Work the issues
Implement and check each change. Feed discoveries back into the design and affected issues.
Review and learn
Review the result, record the evidence, and keep useful decisions in the Brain for the next session.
For example, an unexpected API constraint becomes a design question before a workaround. Once settled, the design and issues carry that decision forward. Explore the skills.
Wire a project in four steps
Install the plugin
In Claude Code, send these as two separate prompts. For Codex, follow the installation guide.
text/plugin marketplace add arminzou/dotbraintext/plugin install dotbrain@dotbrainGet the CLI
Invoke
wire-brainin your coding agent. It installs the CLI and prerequisites if needed, then wires the repo. For manual setup, follow the CLI installation guide.Wire a repo
If you installed the CLI manually, create or repair the project's Brainspace and link it into the repo.
bashdotbrain wire --repo ~/repos/my-appCheck the wiring
A read-only health check. Then start a fresh agent session in the repo.
bashcd ~/repos/my-app dotbrain doctor