2d • 🎉 Wins
How Long-running
Long-running Codex/Claude sessions work best when you stop thinking of them as “one giant conversation” and start treating them as a continuous work process.
The idea is to define a clear objective with /goal, let the agent work in cycles: analyze → execute → test → fix → continue — and keep important state outside the conversation in files like goal.md, plan.md, state.md, progress.md, and failures.md.
The key rule is:
As long as there is a clear, safe next action aligned with the objective, keep going without waiting for new instructions.
For runs lasting many hours or even days, the ideal setup is:
clear objective + success criteria + state files + compaction + continuous testing + controlled autonomy.
And the main conclusion from the 11-day experiment is this: very long sessions can work, but the real limit is not the size of the JSONL file — it is the point where continuity starts to reduce quality, cost efficiency, or operational effectiveness.
Examples:
0
0 comments
How Long-running
Leaderboard (30-day)
1
+5
2
+2
3
+2
4
+1
5
+1
Powered by