A context window is the bounded amount of information a model can consider in one interaction. Messages, files an agent reads, and tool outputs all occupy it. Supplying an entire codebase and every policy up front can consume that space before implementation begins. section 1.3
A session that loses its decisions
A coding agent adds features across a long session. Its context fills with prompts, corrections, file reads, and tool outputs. It then forgets an earlier decision or restores behavior that was already corrected. More follow-up instructions may fix one change while adding still more context. Codex CLI’s /status command is one way to check how much window remains. section 2.3.1
Compaction summarizes earlier conversation so work can continue, but a constraint that does not survive the summary may be lost. Do not rely on the session history as the only record of intent. Extract important decisions into durable artifacts, organize them for navigation, and load what the agent needs in a future session. The aim is sufficient context for independent execution, not the largest possible prompt. section 1.3





































