A story in five days

This is a story about forgetting.

You use five AI coding tools. None of them remember what the others learned. Scroll through one week.

Scroll

Monday 10:14

You make a call.

Sessions live in SQLite. Redis was only there for the old job queue. It takes twenty minutes of back and forth to land on it.

Monday 10:34

It's the right call.

Claude Code agrees. The tradeoff is settled, the reasoning is sound, and you move on.

Monday 18:02

Then you close the terminal. The decision goes with it.

Nothing carries the reasoning forward. The next session, in any tool, starts from zero.

Claude Code · api

You

Let's drop Redis. Sessions live in SQLite; Redis was only for the old job queue.

Claude

Agreed. I'll keep sessions in SQLite and remove the Redis client from the API.

decision made

session closed · context gone

Tuesday 09:02

New day. New tool.

You open Cursor to build the session endpoint. It has never heard of Monday.

Tuesday 09:05

It suggests Redis.

Confidently, with a code sample, because nothing told it otherwise.

Cursor · sessions.ts

import { db } from "./sqlite";

export async function getSession(id) {
+ import Redis from "ioredis";+ const cache = new Redis(); // cache sessions  return db.get("sessions", id);
}

contradicts Monday's decision

Wednesday 16:40

You explain it. Again.

This time to Codex, which wants to add a Redis health check to the deploy script.

Wednesday 16:52

Three tools. Three explanations.

Every tool starts from zero, so you become the memory. You're the only thing connecting them.

Claude Code

You · Mon

Sessions live in SQLite, not Redis.

Cursor

You · Tue

No Redis. Sessions are in SQLite.

Codex · deploy.sh

You · Wed

Remove the Redis health check. We don't use Redis anymore. Sessions are in SQLite.

3×the same decision, explained this week

Claude Code Codex Cursor Antigravity

Thursday · 02:00

So you give them one shared brain.

Capture

It listens to every tool.

Parsers and file watchers read each session as it happens.

Distill

It writes down what you settled.

wiki/infra.md · Sessions live in SQLite (decided Monday).

Rank

It knows what matters.

Search relevance plus how often a memory actually helped you.

Inject

It briefs every tool before you type.

A ~2,000-token digest in CLAUDE.md, AGENTS.md and GEMINI.md.

Friday 11:30

Any tool. It already knows.

Open Cursor, Codex or Antigravity CLI. Monday's decision is in the briefing before your first message.

Friday 17:45

You never explained it a fourth time.

Decisions, fixes and the reasons behind them now carry across every tool you use.

Cursor

<!-- BRAIN:START -->
SQLite sessions, no Redis<!-- BRAIN:END -->

Cursor

Using the SQLite session store.

Codex

## from memory
No Redis in deploy (Mon)

Codex

Skipping the Redis health check.

Antigravity CLI

# GEMINI.md
Sessions: SQLite (Mon)

Antigravity

Sessions are in SQLite, so no cache layer.

One more thing

A brain like this knows a lot about you.

Your decisions, your code, your mistakes. That shouldn't sit on someone else's server.

Encryption

So it's sealed with your key.

age encryption. The key lives only in your Mac's Keychain and never leaves it.

Storage

And it lives in your GitHub.

A Release asset on your own private repo. A leaked repo or a leaked token exposes nothing readable.

Your memory4,812 observations

age keyKeychain only

Release assetyour private repo

Open source · Apache-2.0

Next week, your tools remember.

One command wires every tool on your machine, creates your private data repo and generates your key.

Get it on GitHub

curl -fsSL https://raw.githubusercontent.com/rohithhn/Open-Agentic-Brain-and-Memory/main/install.sh | bash

macOS or Linux Node 22+ git A GitHub account