Day 4 on same session....
retained text
Lately I've noticed something. Some sessions are great and get things done right every time. Some are frankly shit from the get go and need to be closed. A couple days ago I started an opus session to control codex on tasks. It was nailing it for awhile. then codex went to shit. Every task was producing worse and worse output. Opus was catching it at every turn having to fix it. I decided maybe the task was too much for codex and had opus use fable for subagents. Even worse then codex... same thing. Every task progressively kept breaking more and more. Wouldn't follow directions and kept assuming. Told opus to to use its own subagents with opus but for some reason it tore thru tokens like crazy and my reset didnt expire but disappeared anyway. So I told it to go back to codex using 6.1 sol and its killing it again. But everytime something breaks its on it catching all mistakes. Fixing it. Understanding the project. Im checking code myself and running tests and this one session is just on fire. 4 days now and its still going strong. Ive also noticed with codex sometimes it will nail image Gen every time. Then a new session will stray after first attempt. So I'll close it immediately and until I find a session nailing it and its amazing. I was always concerned and having to keep the ledger updated and handoffs going. Changing after a few sessions due to context. But im really starting to rethink things now. Anyone else noticed anything similar?
document fetched 2026-10-24 10:42 · canonical https://reddit.com/r/ClaudeCode/comments/1xdbodo/day_4_on_same_session