Your team learns.
Your agents forget.

REM turns what engineers and coding agents learn into shared engineering knowledge your whole team can trust.

Reconciled Engineering Memory · An engineering knowledge system for software teams.

01 · The problem

Every session learns something.
Then the session ends.

Claude Code, Codex and Cursor discover how your software really works, dozens of times a day. Almost none of it survives.

Claude Code · session 281
Prisma stays pinned at 6.2. Newer versions break migration generation with our Postgres extension.
Session ended. Lesson gone.
Codex · session 882
ledger is the only service allowed to mutate balances. payment-api must call it.
Session ended. Lesson gone.
Cursor · session 113
Upgraded Prisma to 6.4. Migration generation broke.
Same mistake. Third time.

Repeated investigation. Stale assumptions. Wasted AI spend.

02 · Passive by design

When the work ends,
REM starts.

A small local daemon observes agent sessions, Git, pull requests and tests. Nothing to write down. Nothing to curate.

Commit
Pull request
Tests pass
Merge

Consolidation happens at meaningful checkpoints. Not mid-thought.

03 · REM Dream

Your team works.
REM dreams.

Like memory consolidation in sleep, REM revisits the day and keeps only what holds up.

01FilterDrop trial-and-error and dead ends.
02VerifyCheck each claim against Git, PRs and tests.
03ReconcileResolve contradictions and stale truth.
04ConsolidateMerge duplicates. Strengthen what holds.
05PublishCompile a compact, versioned team memory.

04 · Not another AI memory

REM remembers
why it believes something.

An agent saying it does not make it true. Every claim is checked against evidence and linked to it.

Agent observes

“Sessions are stored in Redis.”

Codex · session 882 · candidate claim

REM checks

Git history · Redis store removed
PR #918 · sessions moved to PostgreSQL · merged
CI · session tests pass on main

Team memory

Active Sessions use PostgreSQL since PR #918.

Superseded Sessions used Redis. Kept as history, never served as truth.

Old knowledge is superseded, never silently overwritten.

05 · By morning

Learn it once.
Build on it together.

The next session starts where the team left off. Delivered through REM’s MCP server and agent skill, so developers just keep working.

Add retries to the refund job

Claude Code asks REM before writing code, and starts with what the team already knows.

From team memory

Refund retries must reuse the original idempotency key.

PR #942 · duplicate-refund fix · merged
Constraint · verified · payment-api

Illustrative workflow

06 · Team-wide, not session-wide

Your architecture crosses repos.
So does REM.

Knowledge lives at the team level, across every related repository. Git decides what is current, branch-specific or stale.

Payments team

checkout-web
payment-api
ledger
fraud-worker

Cross-repo knowledge

ledger is the source of truth for balances. payment-api and fraud-worker read, never write.

Architecture · verified across 3 repositories

Humans remember toorem remember “Only the reconciliation job may write balances directly.”

Explicit human memory is strong evidence. It still gets reconciled.

Built for company code

Secrets and personal data are filtered on the developer machine before anything syncs.

Sensitive-data protection powered by Velum Privacy.

Good work
deserves
a memory.

Evidence is immutable.
Claims are versioned.
Truth is reconciled.
Context is compiled.

We are working with engineering teams that already run coding agents in production workflows. Join the private beta.

Starting with GitHub, Claude Code & Codex.

Your team learns.Your agents forget.

Every session learns something.Then the session ends.

When the work ends,REM starts.

Your team works.REM dreams.

REM rememberswhy it believes something.

Learn it once.Build on it together.

Your architecture crosses repos.So does REM.

Good workdeservesa memory.

Give your team a memory.