| The rhythm issue is real. What helped me: 1. Don't watch it work. Give CC a clear task with success criteria, then go do something else, directory submissions, Quora answers, whatever. Come back to finished work or a clear error. 2. Batch related work into one session. Instead of "fix this button" then "add this feature" - give it a full plan with 6-8 items. It enters plan mode, works through them sequentially, and you review once at the end. 3. CLAUDE.md with workflow rules. CC reads it at session start. Mine includes "never mark a task complete without proving it works" and "after any correction, update lessons.md." This eliminated the cycle of fix break ask fix. 4. Accept the async mental model. Agentic coding isn't pair programming. It's more like delegating to a junior who's incredibly fast but needs clear specs. Write the spec well, step away, review the output. The broken rhythm only hurts when you try to synchronously watch and steer. The moment I started treating CC sessions like async tasks, everything clicked. |