entity_readLABSCO SUMMARY
It says no, which is the part that matters.
Most memory servers store and retrieve; this one returns a verdict. Checking a proposal against logged decisions and getting back "conflict" with the original reasoning and the alternatives you already rejected is what stops an agent quietly reopening a settled question three weeks later. The decision review inbox is the other half — it proposes and you confirm, so nothing archives itself.
What it is
A local-first memory server for the state a conversation log does not carry: what was decided and why, what is blocked, what is active, and what should not be reopened. The wedge is enforcement — before acting, an agent can check a proposal against your logged decisions and be told it is re-litigating a settled choice.
What you get
- Decisions with teeth —
decision_logrecords the reasoning and the rejected alternatives,decision_checkreturns clear, caution or conflict on a proposal,decision_refreshupdates review dates and evidence without touching the content,decision_reviewbuckets overdue decisions and recommends an action for each - Entities —
entity_readandentity_updatetrack projects and initiatives with status, momentum, blockers and next moves - Plans —
plan_setmakes step 1 the active next move,plan_advancecompletes or skips a step and requires evidence or a reason,plan_addandplan_read - Prioritization —
focus_getrecommends what to work on, andproject_evidence_scangrounds it in the repository's own state: STATE.md, HANDOFF, ROADMAP, git activity and dirty files context_resolve— works out which entity the current work belongs to from mentions, aliases and files, deterministic and confidence-scored rather than guessed- Hygiene —
pattern_detectfinds recurring blockers, stale work and avoidance signals,memory_checkflags contradictions and noise,memory_commitsaves at end of session,audit_logreads the full mutation history - Safety —
risk_assessclassifies risky actions including destructive and public-release ones,action_guardapplies guard templates before proceeding,wrap_checkandwrap_autocatch accumulated state changes semantic_recallfor searching memory by meaning, and slash commands installed into.claude/commands/so the agent has a fixed vocabulary
Requirements
No account and no key for the core. Node.js 20 or newer; npx brain-os init in your project creates .brain/, installs the slash commands, and drops AGENTS.md plus thin pointer files for Claude Code, Copilot, Cursor, Zed and Windsurf — --minimal skips all but the first two. Connect with claude mcp add brain-os -- npx brain-os serve, or a command/args entry elsewhere. semantic_recall is the one tool that needs more: install openai alongside and set BRAIN_EMBEDDINGS to openai, which uses text-embedding-3-small. Reference OPENAI_API_KEY from your shell rather than pasting it into the MCP config, which is plaintext. Without the provider, that one tool returns a setup error and everything else keeps working. Package brain-os, MIT.
Setup effort
One command — npx brain-os init
USE CASES
Stopping an agent re-litigating a settled choice
Check the proposal before acting and surface the original reasoning if it conflicts.
Answering what to work on this morning
Read the prioritized recommendation grounded in the repository's actual state, not just the ticket list.
Keeping a multi-step plan on rails
Set the plan so step one becomes the active next move, and require evidence before advancing.
Noticing you keep getting stuck on the same thing
Run pattern detection across entities for recurring blockers, stale work and avoidance signals.
Clearing decisions that are past their review date
Read the review inbox, which buckets each one as still true, changed, or needing evidence, and confirm what to do.
22 tools
Listed in project docs. Your client may show a different list.
entity_updatedecision_logdecision_checkdecision_refreshdecision_reviewcontext_resolvefocus_getproject_evidence_scanpattern_detectmemory_checkmemory_commitsemantic_recallaudit_logwrap_checkwrap_autoplan_setplan_advanceplan_addplan_readrisk_assessaction_guardBEFORE YOU INSTALL
What to know first
Tools you get
22 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
npx brain-os initMCP Clients
Claude Code
claude mcp add brain-os -- npx brain-os serveCursor, Any MCP client
{
"mcpServers": {
"brain-os": {
"command": "npx",
"args": [
"-y",
"brain-os",
"serve"
]
}
}
}