BrainOS
Use Brain OS as a local-first MCP server for persistent project operational memory, planning, and guarded agent actions across AI tools.
Track and update entities such as projects, products, and initiatives with status, momentum, blockers, priorities, and next moves.
Log, check, refresh, and review decisions with reasoning, alternatives, assumptions, invalidation conditions, and review dates.
Resolve which project/entity the current work belongs to and get prioritized focus recommendations.
Create, advance, extend, and read ordered plans for an entity.
Detect recurring patterns, blockers, avoidance signals, and memory-quality issues.
Search memory semantically, inspect mutation history, and wrap sessions with automatic safety-net staging.
Scan repository evidence and run read-only operational-state checks against package/Git facts.
Assess action risk and apply policy guard decisions before high-risk operations like publishing, pushing, deleting, or public release.
Set up Brain OS in a project with a preview/confirmation flow that avoids overwriting existing instruction files.
Keep data local as JSON files under
.brain/, with no cloud, database, or account required.
Provides semantic search via OpenAI's text-embedding API for memory recall.
Brain OS
Your AI remembers conversations. It still forgets project state.
Brain OS gives agents operational state: decisions, plans, blockers, and priorities that survive across sessions.
What is this?
AI agents are powerful inside a session, but long-running work has more state than any one chat: what you decided, what's blocked, what's active, and what should not be reopened. Brain OS gives agents operational state, not conversation logs:
Entities — track projects, deals, initiatives with status, momentum, blockers, and next moves
Decisions — log what was decided, why, what alternatives were rejected, and when to revisit
Patterns — detect recurring blockers, stale work, avoidance signals, and theme convergence
Focus — prioritize what to work on based on urgency, momentum, leverage, and staleness
Verified operational state — compare package/Git facts with claimed and desired state without changing anything
Semantic recall — search memory by meaning, not just ID
Brain OS is an MCP server that works with any MCP-compatible client: Claude Code, Cursor, Zed, GitHub Copilot, OpenAI Codex, Windsurf, or any agent that speaks the protocol.
Related MCP server: MCP Memory System
What it looks like in use
Before the agent acts, it can check whether a proposed move conflicts with an existing decision:
> decision_check({ proposal: "switch to Postgres for the new service" })
{
"verdict": "conflict",
"conflicting_decision": {
"id": "dec_2026_03_14_db_choice",
"decision": "Use SQLite for all local-first projects",
"reason": "Lower ops burden, no infra to run, fits single-user scope",
"rejected_alternatives": ["Postgres", "DuckDB"],
"logged_at": "2026-03-14"
},
"guidance": "Re-litigating a settled choice. Surface the prior reasoning to the user before proceeding."
}That's the wedge: structured state with enforcement, so agents stop re-opening questions you already answered.
Quick start
Requires Node.js 20 or newer.
1. Connect the server
Claude Code:
claude mcp add brain-os -- npx -y brain-os serveCursor (.cursor/mcp.json) and other MCP clients:
{
"mcpServers": {
"brain-os": {
"command": "npx",
"args": ["-y", "brain-os", "serve"]
}
}
}VS Code uses .vscode/mcp.json with a "servers" key and "type": "stdio" in place of "mcpServers".
2. Set up the project, from chat or from the terminal
From chat (no terminal): open your project and ask the agent:
Set up Brain OS in this project.The agent calls brain_setup. It shows the folder and the exact files it would create, and writes nothing until you say yes. Your existing AGENTS.md / CLAUDE.md are never overwritten. If you already have your own AGENTS.md, the Brain OS rules go to .claude/brain-os/AGENTS.md, and the setup lists any of your files that need a one-line pointer to it. Nothing is written outside the project.
From the terminal:
# In your project
npx brain-os initEither way, setup does three things:
Creates a
.brain/directory with your entity, decision, and pattern stores.Installs slash commands into
.claude/commands/so you can run/brain,/brain:focus,/brain:decide, etc. directly in Claude Code. Bare aliases (/focus,/decide, etc.) install alongside them.Adds agent instructions so every MCP-compatible client behaves the same way.
AGENTS.mdis the canonical file. Thin pointer files cover Claude Code (CLAUDE.md), GitHub Copilot (.github/copilot-instructions.md), Cursor (.cursor/rules/brain-os.mdc), Zed (.zed/rules.md), and Windsurf (.windsurfrules).
Flags (brain_setup takes the same options as minimal / include_commands):
npx brain-os init --minimal: install onlyAGENTS.md+CLAUDE.mdand skip the other client pointers (clean-repo mode)npx brain-os init --no-commands: skip the slash commands (MCP server only)npx brain-os init --no-agent-instructions: skip all agent-instructions pointer files
Check live operational state
Brain OS can independently read a small, explicit set of repository facts and show drift without updating memory or project state:
npx brain-os reconcile --check .The matching MCP tool, operational_state_check, observes only package.name, package.version, the current Git branch, and Git HEAD. Optional claimed state, desired state, and decision context are returned as separate layers: observations may be verified, stale, conflicting, unavailable, or different from a claim, but the checker never chooses a winner or applies a change.
The report is ephemeral JSON written to stdout. It creates no fact, evidence, issue, memory, entity, decision, plan, or audit record.
Configure semantic search (optional)
The semantic_recall tool needs an embeddings provider. Everything else (entity_update, decision_log, plan_*, etc.) works without one.
Brain OS does not install an embeddings SDK by default. This keeps the core install small and avoids pulling native ONNX/Sharp dependencies into users who do not need semantic search. Install the optional OpenAI provider beside brain-os, then add BRAIN_EMBEDDINGS to your MCP server env:
npm install brain-os openaiThen configure the provider in your MCP server environment:
{
"brain-os": {
"command": "npx",
"args": ["-y", "brain-os", "serve"],
"env": {
"BRAIN_EMBEDDINGS": "openai",
"OPENAI_API_KEY": "${OPENAI_API_KEY}"
}
}
}Mode | What it does | Setup |
| Temporarily unavailable while the former provider carries unresolved High-severity transitive advisories. | Use keyword recall or the OpenAI provider until an audited local backend ships. |
| Uses | Install |
If BRAIN_EMBEDDINGS is unset, the OpenAI provider is missing, or local mode is requested, semantic_recall returns a clear setup error. No silent provider install, model download, or API call occurs. Core tools continue working normally.
Never paste a raw
sk-...key into your MCP config.~/.claude.jsonand similar MCP config files are plaintext and easy to expose on screen or in backups. Instead, export the key once in your shell and reference it from the MCP process environment.
Tools
Tool | Description |
| Read operational state of one or all tracked entities |
| Update entity state — status, momentum, blockers, next moves |
| Log a strategic decision with reasoning and alternatives |
| Check a proposed action against active decisions — returns clear/caution/conflict |
| Refresh an existing decision: bump review_date, append evidence, change status. Metadata only — does not mutate decision content. |
| Review-debt inbox: buckets overdue decisions (still-true / changed / archive / needs-evidence) and recommends an action for each. Read-only — proposes, you confirm. Auto-detects duplicate-stub decisions. |
| Resolve which entity the current work belongs to, from explicit mention / alias / files / lexical signals. Deterministic and confidence-scored — routes known context, never guesses intent. |
| Get prioritized recommendations on what to work on |
| Read-only scan of a repo's native operating state (STATE.md, FLAGS, HANDOFF, ROADMAP/PLAN/TODO, git activity, dirty files) for human gates, next moves, and do-not-touch — grounds focus in repo reality. |
| Ephemeral read-only comparison of allowlisted package/Git facts with optional claimed and desired state; reports evidence-backed drift/conflict without applying changes. |
| Set up Brain OS in the open project from chat. Previews the folder and exact file plan, then writes only after the user confirms (single-use preview token). Never overwrites existing instruction files. Local stdio server only. |
| Analyze patterns across all entities |
| Audit memory quality — flags stale data, contradictions, noise |
| End-of-session commit — save all state changes |
| Search memory by meaning using natural language |
| Read the full mutation history — what changed, when, by whom |
| Detect whether meaningful state changes have accumulated since the last wrap |
| Non-interactive safety-net wrap: applies low-risk fields and stages high-risk changes for review |
| Set an ordered plan for an entity — step 1 becomes active next_move |
| Complete or skip a step (requires evidence/reason) — auto-promotes next |
| Add steps to an existing plan |
| View plan progress and current step |
| Classify risky actions before execution, including public-release and destructive-operation risks |
| Apply built-in guard templates to common high-risk actions before proceeding |
Slash commands
brain-os init installs slash commands into .claude/commands/ so the agent has a clear vocabulary for working with operational state. Each command installs in two forms: /brain:* (canonical, documented form) and a bare alias (/decide, /focus, etc.) for power-user brevity. /brain is the namespace root and installs once.
It also installs:
BRAIN_OS_PROTOCOL.mdat.claude/brain-os/PROTOCOL.md(project) and~/.claude/brain-os/PROTOCOL.md(user; written bynpx brain-os init, or bybrain_setuponly withinclude_user_protocol=true). The protocol governs tool routing: when an agent runs a Brain OS slash command, it reads the protocol first, then callsentity_read/plan_read/focus_get/etc. as primary. Pulse files become fallback only.brain-os-modesubagent at.claude/agents/brain-os-mode.md. When the main agent delegates Brain OS work to a subagent (e.g. Claude Code's Task tool), it picks up under the same protocol — no risk of subagents falling back to generic file search.Optional routing-guard hook at
templates/hooks/brain-os-routing-guard.py. Opt-in PreToolUse hook that warns if pulse files are read while a.brain/workspace exists. Install instructions are printed bybrain-os init.
Command | Alias | What it does |
| — | Project scanner: overview of all entities, freshness, decisions, alerts |
|
| "What should I work on today, and why?" with evidence |
|
| Capture a strategic decision (with conflict check before logging) |
|
| Strategic thinking partner: think a decision through before building |
|
| Session wrap: update entity state, capture decisions, detect momentum shifts |
|
| Detect patterns across entities: recurring blockers, avoidance, themes |
|
| Weekly or monthly retrospective: what shipped, what stalled, what's hidden |
|
| Show how entities connect, leverage opportunities, shared decisions |
Idempotent install
Re-running init is safe and repair-aware: existing Brain OS commands are preserved, and any missing form is installed. If a command path is taken by another tool, that path is skipped and reported — your file is never overwritten. You can install Brain OS into a project with existing /decide or /focus commands and the namespaced /brain:* forms will still land.
How it works
Brain OS stores everything as local JSON files in a .brain/ directory:
.brain/
entities/ — one file per tracked entity
decisions/ — decision log
patterns/ — detected patterns
config.json — workspace settingsNo cloud. No database. No account. Your data stays on your machine.
Why no UI?
The interface is the agent. Brain OS is read and written through MCP tool calls — /brain, /focus, /decide, decision_check, etc. — surfaced inline by whichever client you use (Claude Code, Cursor, etc.). There's no separate dashboard to keep open, no second tab to context-switch into, no UI state that can drift from the underlying files.
This is a design choice, not a missing feature. Brain OS state lives at the same level as your code; the agent is already there, already in the conversation, already the right surface to ask "what's the priority right now?" Adding a human dashboard would split attention between two interfaces for the same data.
If you want a visual at-a-glance view, .brain/ is plain JSON — render it however you want. The public MCP server stays agent-native by design.
Teams & sync
Brain OS is single-user by design today. But because .brain/ is just local JSON files, teams can share a brain through any synced filesystem — no product changes needed:
Approach | Pros | Cons |
Git — commit | Diff/merge tools, version history, intentional sync points | Manual |
Dropbox / Drive shared folder | Real-time-ish, no manual steps | Concurrent writes can create conflict files; |
NFS / SMB / S3 mount | Truly real-time | Requires infrastructure setup |
This works without any built-in sync because every Brain OS tool call reads fresh from disk — there's no in-memory cache to invalidate. Whatever your filesystem syncs, the next tool call sees. Same applies cross-tool: log a decision from Claude Code on Monday, open Cursor on Tuesday — same brain, both agents.
Native encrypted team sync with proper merge semantics is on the roadmap. The local-first foundation today is what makes that federation additive, not a retrofit.
Auto-loaded status
When an MCP client connects, Brain OS exposes a brain://status resource with an operational overview — active entities, alerts, top priority, and recent decisions. The agent starts every session with context, not amnesia.
Testing
Brain OS ships a smoke test suite at tests/smoke.mjs, wired to npm test and run on every push by .github/workflows/audit.yml. Run locally:
npm testCurrent coverage (regression + happy-path):
decision_log— type-collision no-supersede, explicitsupersedesworks, cross-entity supersession rejecteddecision_check— keyword-only flag stays caution without embeddings (no false STOPs), asymmetric semantic comparison (rejected vs chosen facet)decision_refresh— clears danglingsuperseded_bywhen status transitions away fromsupersededplan_advance— no over-promotion when an active step already existsentity_update— apply diff and record changes, create missing entity,mode_reasonrequired when parking, status-only updates apply, guarded ranking skips are visiblesemantic_recall— throwsEmbeddingsNotConfiguredError(not generic Error) whenBRAIN_EMBEDDINGSis unsetStore resolution — fails closed in a storeless cwd instead of silently creating an empty
.brain/
Known gaps (no direct coverage yet): focus_get scoring, pattern_detect heuristics, memory_*, plan_set/add/read, and the brain://status resource. Expanding the suite is on the roadmap.
If you hit a bug, please open an issue with the tool, input, and output — that's the fastest path to a fix.
Community
Discord: discord.gg/9VBUGstjY — questions, feedback, what broke for you, what you're shipping with Brain OS
Site: brainos-hq.com
License
MIT
Available Tools
24 toolsaction_guardARead-only
Apply the Brain OS policy table to a risk assessment. Takes the output of risk_assess plus the concrete action type and returns a policy decision: allow (proceed), ask (stop and get explicit user confirmation), or block (do not proceed). Pure TypeScript — no LLM call. Policies in order: private_to_public → block; critical risk → block; force-push → ask; npm publish → ask; security boundary → ask; irreversible → ask; high risk → ask; hard-to-reverse external → ask; medium + requires_confirmation → ask; else → allow. Always audit what was decided and why.
Inputs: assessment (required), action_type (required), entity_id.
audit_logARead-only
Read the audit trail of all memory mutations. Use this — not semantic_recall — for recency questions: 'what's the latest update?', 'what changed recently?', 'what was the last thing written?', 'show me the most recent entry.' Pass last_n=1 for the single most recent mutation. semantic_recall is for topic-based search; audit_log is for time-ordered history, integrity checks, and debugging unexpected state.
Inputs: tool, last_n, entity_id.
brain_setupAIdempotent
Set up Brain OS in a project folder when no store exists yet (tools return 'No Brain OS store found'). Two steps, never skip the first: (1) call with no confirm — returns the proposed folder, a question for the user, and the exact files that would be created, refreshed, or preserved; nothing is written. It also returns a single-use preview_token. (2) Only after the user explicitly says yes, call again with confirm=true, the same target_dir and options, and that preview_token; writes without a matching token are refused. Existing instruction files are never overwritten; any that need a Brain OS line are listed in plan.needsIntegration — tell the user. Writes nothing outside the project unless include_user_protocol=true. If a store already exists, it reports that and does nothing.
Inputs: confirm, minimal, target_dir, preview_token, +2 more.
context_resolveARead-only
Resolve which entity the current work belongs to, with a derived confidence. Deterministic — matches explicit signals (passed entity, named mention, active mission, files touched) before weak ones (lexical, single-active); never guesses from cwd. Returns entity_id + confidence + ask_user. Call this BEFORE focus_get/decision_check when the target entity is not already known, then pass the returned entity_id into them. Confidence >= 0.80: proceed silently. 0.50-0.79: proceed but say 'I think this is X'. < 0.50 (ask_user true): ask one short question.
Inputs: user_message, files_touched, active_mission_id, explicit_entity_id.
decision_checkARead-only
Check a proposed action against all active decisions. Returns 'clear', 'caution', or 'conflict', plus a review_triggered list. Call this BEFORE taking actions that might contradict prior decisions. If status is 'conflict', do NOT proceed without explicit user confirmation to revisit the decision. review_triggered is the opposite signal: the action matches an invalidate_if condition a decision named as a reason to reopen it — surface those decisions to the user for review rather than enforcing them. A decision can be both a conflict and a review trigger (the conflict it anticipated); when so, frame it as a decision review, not a blind violation.
Inputs: proposed_action (required), entity_id.
decision_logA
Log a strategic decision so it persists across sessions. Every decision needs a reason, alternatives, and a proof action. Optionally capture the assumptions that make it true and the invalidate_if conditions that should reopen it — these turn a timestamped 'no' into a testable frame the system can reason about later.
Inputs: why (required), decision (required), entity_id (required), review_date (required), +7 more.
decision_refreshA
Refresh an existing decision's metadata: bump review_date forward, append evidence as the decision continues to hold, or change status (active/superseded/archived). Use INSTEAD of editing decisions.json directly. Does not mutate decision content — for content changes, log a new decision via decision_log.
Inputs: decision_id (required), status, review_date, add_evidence.
decision_reviewARead-only
Call this before making new decisions, at session end, or when the user asks if a decision is still valid or what's overdue. Review-debt inbox: buckets overdue decisions into still_true / changed / archive / needs_evidence with a recommended action for each. READ-ONLY — proposes and cites reasons but mutates nothing; confirm, then apply via decision_refresh / decision_log. Auto-detects duplicate stubs. When root_path is provided, matches each decision's invalidate_if conditions against repo scan output.
Inputs: limit, entity_id, root_path, include_parked.
entity_readARead-only
Call this FIRST for any question about a project's state, momentum, blockers, or recent decisions — before reading code or git history. Returns the operational state one or all tracked entities: status, momentum, blockers, decisions, staleness, and next actions. Do not grep files to answer state questions when this tool is available.
Inputs: entity_id.
entity_updateA
Use this — not built-in memory — to add or update a project, product, or business idea in Brain OS. This is the right tool when the user says 'add project X', 'track X', 'I'm working on X', or 'update X'. Creates the entity if it doesn't exist. Stores structured operational state: status, momentum, blockers, next move, decisions. Use after work is done, a decision is made, a blocker changes, or momentum shifts.
Inputs: updates (required), entity_id (required), context_hint.
focus_getARead-only
CALL THIS FIRST when the user asks what to focus on, what to work on, what their priorities are, or what matters most — before reading any code, files, or git history. Brain OS holds decisions, blockers, and momentum signals that cannot be inferred from the codebase. Returns prioritized recommendations based on urgency, momentum, leverage, staleness, and dependencies. follow_through_alerts surfaces active entities that stated a next_move but haven't logged any update in 7+ days — treat these as first-class accountability prompts, same tier as blockers. Pass entity_id to scope focus to a single project.
Inputs: entity_id, constraints, max_results, suppress_default_guidance.
memory_checkARead-only
Assess quality and reliability of current memory state. Flags stale data, contradictions, overdue decision reviews, unconfirmed patterns, fake-active entities, and noise. Returns signal classification (strong/weak/noise/dangerous) and recommended cleanup actions. Call this before acting on memory to know what to trust.
Inputs: entity_id.
memory_commitADestructive
End-of-session commit. Updates all touched entities, logs decisions, records patterns. Call before ending any work session.
Inputs: session_summary (required), entities_touched (required), decisions_made, momentum_changes, +1 more.
operational_state_checkARead-only
Read-only Verified Operational State checker. Independently derives an allowlisted set of live repository facts (package name/version and Git branch/HEAD), compares them with optional claimed and desired state, and reports verified/drift/stale/conflict/unavailable results with evidence pointers. Decision context remains visibly separate human judgment. Ephemeral: writes no Brain OS, repository, issue, memory, decision, plan, evidence, version, or audit record.
Inputs: root_path (required), claims, desired_state, decision_context.
pattern_detectARead-only
Call this when the user asks about patterns, recurring blockers, what keeps coming up, theme convergence, or avoidance signals — instead of grepping git logs or reading files to find trends. Analyzes patterns across all tracked entities and returns detected signals with entity context.
Inputs: scope.
plan_addA
Add steps to an existing plan. Use when new work is discovered mid-plan. Steps can be added at the end or immediately after the current active step.
Inputs: steps (required), entity_id (required), position.
plan_advanceA
Complete or skip the current plan step. Requires evidence (for complete) or reason (for skip). Automatically promotes the next pending step to active and updates next_move. Enforces continuity — you cannot skip without explaining why.
Inputs: action (required), step_id (required), entity_id (required), reason, +1 more.
plan_readARead-only
Read the current plan for an entity. Shows all steps, their status, the active step, and overall progress.
Inputs: entity_id (required).
plan_setADestructive
Set an ordered plan for an entity. Replaces any existing plan. Step 1 becomes the active next_move. Use when committing to a sequence of work — not for brainstorming. Each step should be a concrete, completable action.
Inputs: steps (required), entity_id (required).
project_evidence_scanARead-only
Read-only scan of a repo's native operating state (STATE.md, FLAGS*, HANDOFF*, ROADMAP.md, PLAN*.md, TODO.md, AGENTS.md + recent git activity / dirty files). Returns evidence — human gates, blockers, next moves, do-not-touch, safe parallel work — surfaced as exact lines. Call AFTER context_resolve and BEFORE building a focus answer. Mutates nothing and does no inference: it returns ALL candidate signals; deciding the focus is the agent's job. This is NOT context_resolve — do not use it to pick which project you're in.
Inputs: root_path (required), entity_id.
risk_assessARead-only
Assess the risk of a proposed action before executing it. Runs a pre-filter (returns low/skipped immediately for clearly safe actions) then applies signal detection for: private→public boundary crossings, destructive operations, release/publish actions, external communication, and security-sensitive file access. Call this BEFORE any action in the trigger set: publish, push, force-push, git tag, deploy, delete tracked files, external API writes, billing, roadmap/private state movement. Returns risk_level (low/medium/high/critical), boundary_crossed, reversibility, and risk_reasons. Pass the result to action_guard to get a policy decision (allow/ask/block).
Inputs: proposed_action (required), diff, entity_id, git_status, +3 more.
semantic_recallARead-only
Call this when the user asks what changed last session, what happened recently, or needs to find a decision/entity by description rather than exact name. Searches memory by meaning using semantic similarity. Use BEFORE reading git log or commit history for session-level context questions.
Inputs: query (required), max_results, source_kind.
wrap_autoA
Tier 2 of auto-wrap: persist a session wrap WITHOUT interactive review, when context is about to be lost (compaction, session end) or the user declined to review. Use the normal interactive /wrap when the user is present and reviewing — only reach for this as a safety net. The agent supplies the synthesized wrap; this tool applies LOW-RISK fields (next_move, open_questions, evidence_of_progress) immediately and STAGES high-risk changes (status, mode, blocked, decisions) as an unconfirmed record for /start to surface and the user to confirm. Always logs a session_wrapped marker. Never put a status change or a decision in pending_review expecting it to take effect now — staged items are proposals, not writes.
Inputs: summary (required), entity_id (required), trigger, next_move, +4 more.
wrap_checkARead-only
Check how much state-changing work has accumulated since the last wrap. Read-only — never mutates. Tier 1 of auto-wrap: call this when the user signals they are wrapping up or ending a session, or periodically during a long session, to decide whether to proactively offer a /wrap before context is lost to compaction or session end. Returns unwrapped_count, the projects touched, and recommend_wrap. When recommend_wrap is true, offer to wrap; do not auto-wrap silently from this tool.
Inputs: threshold, session_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
There are many read-oriented tools (entity_read, focus_get, memory_check, audit_log, semantic_recall, pattern_detect, decision_review, project_evidence_scan, operational_state_check), but descriptions explicitly delineate boundaries with phrases like 'not semantic_recall' and 'this is NOT context_resolve.' A few pairs (decision_check vs decision_review, semantic_recall vs audit_log) require reading the full description to separate, keeping it just shy of 5.
All names are snake_case and organized around clear prefix families (plan_*, decision_*, entity_*, wrap_*). Minor inconsistency in verb/noun ordering (memory_commit, decision_log, audit_log vs entity_read, focus_get), but the pattern remains highly predictable.
24 tools sits in the heavy band for a memory/state server, and several read-path tools could plausibly be consolidated (e.g. project_evidence_scan and operational_state_check both do read-only repo introspection). Each has a defensible role, but the surface feels broader than strictly necessary.
Plan lifecycle (set/add/advance/read), decision lifecycle (log/check/refresh/review), entity read/update, wrap (check/auto/commit), setup, audit, and risk/guard are all covered. Gaps exist around entity deletion/archival and explicit entity listing, but these are minor workarounds.
Maintenance
Related MCP Connectors
Persistent work tracking for AI agents: tasks, status and history that follow you across machines
Project memory shared by AI agents: decisions, results, tasks and handoffs across sessions.
Project management shared by people and AI agents, with persistent project state through MCP.
Persistent memory, inline redaction, per-agent access, and code localization for AI agents.
Related MCP Servers
- AlicenseAqualityBmaintenanceBasic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md21210,764 PyPI4,634AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables persistent storage and retrieval of decisions, settings, and operational rules across chat sessions, maintaining context continuity and decision consistency for long-term development projects through structured memory management.-
- AlicenseNot gradedqualityDmaintenancePersistent decision memory and contradiction detection for AI coding agents. Enforces architectural consistency across sessions — the agent cannot code until it loads prior decisions. Human resolves conflicts on a dashboard or in chat.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides operational continuity for AI coding agents, preserving task state, decisions, checkpoints, and project context across sessions and model switches via MCP.1Apache 2.0