← all posts site ↗

sessions are disposable, the repo is the memory

i had four chat sessions open on the same project, each doing something different. one was cleaning up the readme, another was writing the container, another was pushing it, another was fixing bugs on the side. that is how you lose work, because two agents writing one tree will silently drop each other's diffs. the mess was not the code, it was the structure.

the rule that fixed it: one session equals one task, never one session equals one project. next day, open a new session on the project folder and read the state file first. do not resume yesterday's four hundred message thread. resuming costs you context, triggers compression, and drags stale assumptions into today's work. parallel ideas are separate workstreams with separate files, never two sessions fighting over one checkout.

the durable home for the project is the repo, so it needs a status file with four sections: decisions, current work, next actions, blockers. every session ends by updating it. old sessions are still good for one thing, asking what we decided about something. they are not for continued building.