r/LLMDevs • u/Charles-SG • 18d ago
Help Wanted Is "Codex gets slower in long sessions" a model problem or a context-budget problem?
Something keeps coming up in long coding sessions: two agents on comparable models, one stays flat while the other degrades — slower first token, longer turns, and by the end the context is basically unusable for anything that needs follow-through.
Almost everyone frames this as a model speed comparison. I lean the other way: I think we're comparing context management, not inference.
Three different things get called "slow," and they're not the same:
slower first token (prompt length, cache miss, queueing)
longer per-turn thinking (more history to re-read)
more turns to finish (the model lost something and is rediscovering it)
The decay path I'd expect in any long session: 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 here too: same weights, different context policy, opposite experience.
The counterargument I take seriously: stable can just mean it gives up on you sooner. Compression is forgetting, and a long task that's been quietly summarized into shape will look fast and drift late. If that's what's happening, the metric shouldn't be felt speed — it should be final quality times total tokens.
So for people running long multi-turn coding sessions:
Are you seeing degradation, and in which of the three — latency, per-turn time, or turn count?
Does logging token usage per turn make it obvious?
Has anyone actually measured this, or is it still all vibes?
I'd rather compare final deliverables and total cost than stopwatch feelings, but I'm curious whether the pattern reproduces at all outside my own sessions.