A Retention Policy for Thinking Out Loud

The bug is ugly but ordinary.

A developer opens a chat beside the repository and pastes a stack trace, a failed query, and the theory they are almost embarrassed to have. The theory changes twice. They ask the agent to inspect a file, correct its interpretation, and abandon a fix that made sense for eleven minutes. Somewhere in the middle, they mention the customer whose report finally made the problem legible.

This feels like a scratchpad.

The interface encourages that feeling. There is a text box, a blinking cursor, and one conversational turn after another. The agent is addressed with the loose language people use while thinking: try this, wait, no, look over there. Finished work will eventually leave as a commit or pull request. The conversation feels like the temporary room where the finished work was found.

GitHub is changing the lifespan of that room. In an upcoming Copilot policy change, chat on github.com and mobile will move into the same agent-sessions experience as its cloud agent. The separate policies will become one. The unified experience will be enabled by default, and web-chat data that was retained for 28 days will instead be kept for the life of the account.

The chat window still looks conversational. Its institutional shape has become an archive.

There are good reasons for this. Agent work routinely outlives one sitting and one surface. GitHub's August VS Code release lets people continue sessions across applications and windows, search a complete transcript, navigate a prompt timeline, and reopen the files changed by a particular exchange. A durable session can explain why a strange branch exists, recover an abandoned hypothesis, or help someone resume work after the details have fallen out of working memory.

The archive is useful because the scratchpad contained real work.

That is also why its record status matters. A prompt history can contain more than instructions. It can hold diagnostic output, internal names, failed reasoning, provisional judgments, copied customer language, and the emotional weather of a difficult afternoon. These fragments may be entirely appropriate to the task. They were supplied under the social expectation of a conversation, though, not always the deliberate posture people bring to a durable work record.

Software teams know this distinction in other places. A commit message is written for later readers. A pull request comment is understood to belong to a shared decision. A local notebook can be messy because its audience and lifespan are small. The same developer writes differently in each surface because the interface makes the record boundary legible.

Agent chat has begun to collapse those surfaces together.

GitHub's current CLI documentation describes a searchable history of sessions spanning the CLI, cloud agent, code review, VS Code, JetBrains, the Copilot app, and GitHub.com. Local session files include prompts, responses, tools, and modified-file details. By default for individual use, that history can also sync to the person's GitHub account; managed organizations can control whether cloud storage is available. The resulting record can generate standups, surface recurring mistakes, and answer questions about past work.

It is tempting to treat this as ordinary product memory. The more precise description is record infrastructure. The session has a storage location, an owner, an audience, a retention period, a deletion path, and possible downstream uses. Those properties should be visible before someone begins typing, not discovered when an administrator changes a policy or a search result resurrects an old conversation.

Audience needs particular care. Account-synced history is accessible only to the person by default, and GitHub says an organization enabling session sync does not itself gain access to that history. A separate, explicitly enabled feature for enterprise-managed users can stream prompts, responses, and tool calls into an organization's monitoring systems. Private, cloud-stored, and employer-visible are different states. A humane interface should not make workers guess which one they are in.

Deletion has the same problem. In the CLI, deleting one synced session can remove its remote copy when the person confirms that choice. Pruning old local sessions does not remove the copies already synced to GitHub. Hiding a remote session removes it from search; deleting it removes it from the list. These distinctions are reasonable implementation details. They are poor surprises.

The interface needs a record posture.

Before the first prompt, it could state where this session will live, how long it will remain, who can retrieve it, and whether organizational streaming is active. When policy changes extend retention, the product should treat that as a change to the room rather than a line in a release note. Deletion should name the copies affected. Moving a conversation from local scratch space into durable team context should be an explicit action, closer to saving a document than minimizing a chat bubble.

This gives The Transcript Had Second Thoughts a workplace counterpart. That Field Note asked when fluid speech becomes an authoritative record. Agent sessions ask the same question of reasoning in progress. A chat can look settled enough to search long before the person who made it would consider its contents finished, contextualized, or fit for another audience.

It also changes the room in The Room Was Full Of Private Conversations. Private agent threads can pull questions away from coworkers and into small machine-mediated exchanges. Once those exchanges become durable working history, they form a new documentary layer of work, one with its own ownership and labor questions.

A useful archive can preserve context that would otherwise disappear. It can make delegated work easier to review and interrupted work easier to resume. The answer is not to force every agent session to evaporate.

The answer is to stop borrowing the manners of a disposable chat for a system that remembers like a filing cabinet.

The scratchpad was already an archive. The person typing deserved to know when the room changed.