Use case

The decision is saved, with its reason

For engineers and technical leads: when a new engineer asks "why didn't we do it that way?", the answer is written down with its date.

Request trial access

A decision rejected a year ago, reasons intact

Claude
You

We rejected moving to a managed database service: three times the cost. Revisit if we pass 50,000 users.

Claude

Saved.

Saved to memory · Database decision
One memory
Cursor
You

A new engineer suggests moving to a managed service. Have we discussed this before?

With Memory Bridge

Yes. You rejected it because it costs three times as much, and agreed to revisit at 50,000 users. If you have not reached that number, the decision stands.

From memory · Database decision

Illustrative example

What is worth saving

  • The decision in one sentence, with its date.
  • The reason: what tipped it, and which alternatives were rejected.
  • The review condition: when to look at it again.
  • What was tried and failed, so it is not tried twice.
  • Client and regulatory constraints that shape the design.

Questions you ask months later, and get answered

WhenThe questionWhat comes back
When a new engineer joins"Why did we choose this design?"The decision, its reasons and its date
Six months on"Which decisions are due for review?"Decisions with their review conditions
During an incident"Have we hit this problem before?"What was tried and what worked

Start like this

  1. 1

    Create a project per product

    Each product's decisions stay in place.

  2. 2

    Save the decision when it is made

    At the end of the discussion say: "Save this decision, its reason and its review date."

  3. 3

    Connect your coding tools

    So Cursor or Claude Code reads the decision before suggesting something that contradicts it.

Common questions

How is this different from decision records in the repository?

Records in the repository are read by whoever opens them. Memory is read by your tools when needed, and covers what was decided outside the code.

Does it work for a whole team?

It is built for personal use today. You keep your own decisions and your projects' decisions; team memory is not available yet.

Keep reading

Memory for coding agents

Instruction files tell a coding agent how to write code. How to give coding tools a memory of decisions and reasons that lasts across sessions and tools.

Claude Code

Connect Claude Code to Memory Bridge and it reads from the memory of your work. What you save in Claude Code is there in your other AI tools.

Cursor

Rules say how you write code. Connect Cursor to Memory Bridge and stop re-explaining your work.

One memory. Every tool you use.

The trial is invite-only for now. Request access and we will write to you when your seat opens.

Request trial access