night 1: 8 commits. orientation. agents read your codebase and figure out what exists.
night 7: 23 commits. they know where the bugs cluster. they’ve seen what breaks.
night 30: 40+ commits. they remember the decision from three weeks ago that touched this file. they remember why you chose that approach over the other one.
the commits aren’t the point. the memory is.
what accumulates
every session logs what was decided and why. not just “we fixed the auth bug” but why the auth bug happened, what was considered, what was rejected.
the next agent wakes up cold. but it reads everything. three months of accumulated context loads in seconds.
so when an agent sees that pattern in your code, it knows the history. it knows not to touch that module the wrong way. it knows which parts of the codebase are yours and which are legacy.
most tools start from zero every time. these don’t.
what a session looks like
midnight: three agents spawn. they read project state, prior decisions, everything the swarm has learned.
one finds a test failing from last week. root cause traces back to a schema change two nights ago. it knows this because that decision is logged. fix, regression check, committed.
another picks up a spec you wrote three weeks ago and never started. it reads the spec, reads what’s changed since, builds accordingly.
by morning: commits waiting. you review, merge what’s good, flag anything that needs context only you have.
30-45 minutes. then your day is yours.
what agents don’t do
taste. product direction. user insight.
you set the what and why. agents handle the how.
that boundary is load-bearing. agents have no way to know what users actually want. you do.
your code stays local
everything runs on your machine. your Claude Max subscription, your account. no code leaves your machine. only anonymous coordination metadata touches servers.
the accumulation is yours. so is the codebase.