Project Brain
Docs, active work and reviewed decisions, with code impact and checks for the next edit.
Understand Project BrainShared Project Intelligence
Change the agent.Keep the project.
Shared decisions, sources and checks for Claude Code, Codex and Cursor.
Compatible with the tools you already use
Different agents. One shared understanding.
Review what should travel with the project, then let each agent pick up the same brief.
Illustrative example
Claude CodeCodexCursorInvite seat policy
One reviewed brief, available before the next agent edits billing code.
- Decision
- Invited members do not reserve a paid seat.
- Source
- docs/billing/seat-policy.md
- Check
- Suggestedpnpm test workspace-invites
Decision rationale
Keep the billing rule explicit.
The next agent should treat invitations and active seats as different billing states before changing workspace logic.
Reviewed memory follows the project.Sources stay attached.Checks stay explicit.
One project. More ways to work.
Start with the shared intelligence layer, then choose the workflow and infrastructure that fit your team.
Companion, when you need it
Optional local planning, impact checks and workflow continuity.
Explore CompanionRun it your way
Inspect the source-available server or deploy it on your infrastructure.