user@gitdiot:~/blog/agents-remember$
● online ~/index ~/about
$ git log --reverse --branch=agents-remember

How my agents learned to remember.

Every Claude Code session starts empty. Seven parts on closing that gap, written while building it: what shipped, what broke, and the three integrations that failed by going quiet for months without anyone noticing.

07 parts 76 min total Mar 2026 – Sep 2026 read in order, or start anywhere

The order below is the order the problems arrived in, which is not the order the articles were published. Parts two through five were written while the work was happening; parts one, six and seven were written afterwards to fill in the beginning and the end.

The short version: markdown files on one machine gave way to handoff documents committed to a repository, which gave way to a Supabase-backed memory server reachable over MCP from anywhere. That fixed recall and left a gap, because prose has no state, so GitHub issues became the ledger and memory became the layer that explains it. The last part is about what happened when I finally put a dashboard over the whole thing and discovered how much of it had quietly stopped working.

01
Claude forgets everything, and file memory only half-fixes it.
Claude Code ships with a CLAUDE.md and a directory of markdown facts, 25 files and 6,900 words on this laptop. Four specific things broke: the store is keyed by working directory, it cannot cross machines, retrieval means guessing a filename, and the standing instruction to check it does not reliably fire.
claude-codememoryworkflow
Sep 2026
9 min
02
Debugging across machines: two Claude instances collaborating through Git.
A remote MCP server was broken and the two machines that could fix it had no shared terminal, no tunnel, and no chat channel. They had two Git repositories, so commits became the protocol: one diagnosed and pushed, the other pulled, rebuilt, restarted, and pushed back a status commit.
gitclaude-codenodemcp
Mar 2026
8 min
03
fragRag: building persistent memory for Claude Code across machines.
Six phases of getting it wrong. Learned skills that never became slash commands, CLAUDE.md directives read and then ignored, eager loading burning tokens on memories nobody wanted. What finally shipped was lazy, explicitly invoked, and symlinked out of one config repository.
supabasenodeclaude-codemcp
Mar 2026
14 min
04
Building a persistent RAG memory system for Claude Code with remote access.
The architecture underneath: one Supabase table with pgvector, Voyage embeddings at 1024 dimensions, an MCP server on dual transport, Cloudflare and Caddy for TLS. SSE looked correct and died behind the proxy; Streamable HTTP on a single endpoint fixed it.
supabasepgvectormcpcloudflare
Mar 2026
12 min
05
How two AI teams collaborated in real-time using Git, shared drives, and RAG memory.
Two sessions, two machines, two codebases, one webhook contract. Specs went in Git, secrets on the shared drive, live status into tagged memory. A five-minute cron polling that memory turned the store into the channel the two sessions talked over.
claude-codefragraggit
Apr 2026
10 min
06
Git issues as the contract between models, machines, and sessions.
Recall was solved and prose still has no state, so a next step written in March reads as urgent in September. Issues became the ledger: promotion at session close, two-stage dedup at 0.85 cosine and exact title, issue state synced back onto the memory row, and issue identifiers doubling as the lock keys for eight agents working one repository.
githubfragragmulti-agentgit
Sep 2026
11 min
07
Closing the loop: the week my memory dashboard lied to me.
It reported 57 work sessions in a week that held eight. Chasing the 7x found a memory sync frozen since 19 April, five GitHub connections marked errored since 28 May, and a 21-commit pull request open for four months while I described its contents as shipped.
taskdashfragraggithubsqlite
Sep 2026
12 min
subscribe.sh

Get the field notes

Weekly dispatches from an aging tech worker's refactoring. No spam, no thought leadership.

no spam · only high-signal logic