How do I make Cursor or Claude Code remember my codebase decisions?
Feed them a decisions log. bRRAIn's Key-Decisions log + module map + risk registry is auto-consolidated into a master context file Claude Code reads at boot. Decisions from 2023 still influence today's suggestions.
Why IDE agents forget your decisions
Cursor and Claude Code are stateless between sessions by default. They read the open files, maybe a few neighbours, and call it context. Your 2023 decision to standardise on Postgres over DynamoDB, or to reject GraphQL for the public API, is nowhere in that window. So every morning the agent re-proposes the alternatives you already killed. The fix is not a smarter model — it is a durable decisions log the agent rehydrates at session start. That is the core of the bRRAIn architecture.
What a usable decisions log looks like
A usable decisions log is structured, not a wiki dump. Each entry captures the question, the chosen option, the rejected options, the reasoning, and the date. bRRAIn stores these as nodes in the POPE graph, tagged with the modules they touch and the risks they mitigate. The Consolidator merges new ADRs into the master context file as PRs land, so the agent never reads a stale version. Your key-decisions layer becomes the institutional memory the IDE reads from.
How Cursor and Claude Code read it at boot
At the first prompt of a session, the IDE's agent queries bRRAIn through the MCP Gateway and receives a ready-to-inject bundle: module map, active decisions, risk registry, and recent commits. The Embedded SDK makes this a one-call fetch. Claude Code reads the bundle into its context window before it sees your first instruction, so it already knows the codebase's shape. When you ask "should we use Redis or Memcached?", it replies with your own 2023 answer and the reasoning — not a generic StackOverflow summary.
What durable memory changes day to day
The observable change is fewer re-litigated debates. The agent stops proposing patterns your team already rejected. New hires ask the agent instead of pinging the senior in Slack. Decisions made three years ago still shape suggestions, because they live in the graph, not in someone's head. The Handler applies them as soft constraints during generation, so code emerges aligned with house style and past trade-offs. The codebase gets a memory; the IDE becomes the interface.
Relevant bRRAIn products and services
- Memory Engine / Handler — assembles the master context file Cursor and Claude Code read at session boot.
- Consolidator — merges new decisions into the master context as they land.
- MCP Gateway — the connector the IDE's agent calls to fetch the bundle.
- Embedded SDK — one-call memory fetch for Cursor, Claude Code, or any agent.
- SDK quickstart — step-by-step guide to wiring decisions into your IDE agent.
- Book a demo — watch Claude Code pull a 2023 decision into today's suggestion.