Agent Sessions Are Documentation

Fri Jul 10 2026

Ever since I started using agents for coding, I’ve had a feeling in the back of my head that a lot of documentation gets lost in the conversations with the agents.

Some of it gets transferred into the .md files: plans, ADRs, “docs”. These are not connected to each other in a way that a human can navigate and get a grasp on the project. Features get left half-finished, buried in the conversations with the agents, or overwritten by later changes.

I still haven’t seen a team that treats agents’ output as project memory in the same way they treat email threads, GitHub discussions, or JIRA comments. Agent sessions are treated more like Slack threads: discarded and forgotten. The difference is that agent sessions could relatively easily be turned into reference documents inside the codebase: taggable, scannable, and searchable.

In practice, not every session should be included in the project archive or memory, but there should at least be a mechanism that allows adding some of them as references.