Astra is introducing a new way for Codex to preserve and retrieve information after a coding session reaches its context-window limit. A post by @daniel_mac8 describes an experimental system that keeps notes across context windows and makes earlier messages and tool calls searchable.

Original post on X

Load the post to view it as published on X. X may receive connection data.

View the original post on X ↗

How Astra’s Codex compaction works

A context window is the amount of information a model can actively use at one time. In a long debugging session or large refactor, earlier work eventually has to be compacted so the task can continue. Conventional compaction summarizes that work, but a summary may leave out details such as why a fix failed or how a component behaved.

Astra’s approach separates persistent notes from searchable history. Codex can carry accumulated details forward in notes instead of repeatedly compressing them into a single summary. It can also search earlier context windows for information that was not captured in those notes, including a previous requirement, test result or tool output.

For developers, that could make multi-stage tasks easier to continue after several context windows. For example, Codex may be able to retrieve an earlier failed test or an established requirement before deciding how to proceed, rather than relying only on the latest summary. This does not make the active context window unlimited; it provides a way to preserve and retrieve information outside the current window.

The feature is experimental and can be enabled through a Codex config.toml file, according to the announcement. It is expected to become the default for Astra in the coming weeks.