Is "Codex gets slower in long sessions" a model problem or a context-budget problem?

Charles-SG · reddit · 2026-11-03

The author keeps seeing the same pattern in long coding sessions: two agents on comparable models, one stays flat while the other degrades — slower first token, longer turns, and a context window that becomes unusable for follow-through. His claim: we're comparing context management, not inference speed.

Three different things get called "slow":

The expected decay path: history grows linearly → tool returns dump file contents and search results into the window → compression triggers → detail drops → the model re-reads what it lost → turns go up. Whoever offloads context earlier — subagents, external files, summaries — looks stable without being faster in any single turn. Prompt cache hit rate fits the same frame: same weights, different context policy, opposite experience.

The counterargument he takes seriously: stable may just mean it gives up on you sooner. Compression is forgetting; a long task quietly summarized into shape will look fast and drift late. If so, the metric should be final quality × total tokens, not felt speed.

He asks the community: are you seeing degradation, and which of the three? Does per-turn token logging make it obvious? Has anyone actually measured this, or is it all vibes?

Original post →

More from coding & agent

coding & agent channel →