Trying to nail down a workflow and I keep going back and forth, so I want to hear from people actually doing this daily. My situation: after I’m doing QA, I usually end up with a list of ~10 things I want done. A mix of bug fixes and improvements. A few are trivial, but some are genuinely big (multi-file refactors). What I want is to dump the whole list in one message, hit go, and walk away completely. No tending, no sitting there approving every file write. My main concern is big context choking my quota. Here’s where I’m stuck:
- Is one giant message actually better, or worse? Part of me thinks batching everything into one prompt is efficient (context loads once). But I’ve also seen people say long autonomous runs bloat the context window with tool output and the model starts drifting halfway through. So is “one big message” a trap for anything non-trivial? Should I force it to write a plan/todo file first instead?
- Opusplan, does it actually help here? Everyone recommends it (Opus plans, Sonnet executes). But doesn’t it require manually entering plan mode with Shift+Tab, which always needs me in the loop to approve? Feels like opusplan and “walk away” are kind of contradictory unless I’m missing something. Also, honestly I feel Opus is needed for most of this. I’d rather choke my quota than have it do the same tasks twice or more because Sonnet wasn’t sharp enough. For those of you running 10+ task batches while you’re AFK: what’s your actual setup? Sonnet-only? opusplan? Auto Mode? Headless with –max-turns ? Checkpoint-to-disk loops? So Trying to avoid the “looks great in a demo, falls apart at task 6” version of this. Real workflows over theory. Thanks 🙏 submitted by /u/ToLoveThemAll
Originally posted by u/ToLoveThemAll on r/ClaudeCode
You must log in or # to comment.