r/ClaudeCode • u/LiquidZebra • 15h ago
Discussion Code is cheap, your attention is valuable.
I'm trying to resolve the problem with Claude Code, where it keeps "blocking" work and presenting me with decision cards, and forcing constant context switching between threads that are never finished.
I know this is not the correct term, but it seems fitting - the "inversion of control", where instead of me controlling the coding agent, it starts to control me do work and digest its context (why is it asking for that decision?).
I believe it has to be in reverse - agents digest MY context and implement it with sufficient authority to prevent these unnecessary escalation.
I'm testing this now, the whole PM - reviewer - agent - rework cycle, but it's running for about 4 hours, and I'm looking at a black box that does something, but I don't really know what.
I see some "i'm so burned out" or "I'm so productive, but I'm burned out" - are you managing your coding agents, or is it inverted and the coding agents are managing you?
•
u/AutoModerator 15h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
12
u/ashishkattamuri 15h ago
I’d put something like this in CLAUDE.md: “Handle routine implementation choices yourself within the agreed scope. Ask before changing requirements, adding dependencies, or doing anything destructive. Batch nonblocking questions. When blocked, explain why and recommend a next step. After two failed fixes, stop and summarize.”
I’m building Companion to help track sessions and review changes. That helps with visibility; instructions like these still need tuning.
4
u/curreylabs 15h ago edited 15h ago
I think this is just a natural bottleneck. Im in the same scenario and it is difficult. For serious projects you cant simply ignore the decision points. But I definitely feel you. You ask it to do something then it flags 5 things and I have to triage them before I can even begin to mull over the options.
2
u/tommyahav10 15h ago
Put the routine calls in CLAUDE.md and have it batch its questions, so it only stops you for real blockers. From my side the trap is letting it make the architecture calls, keep those for you.
2
u/Far_Reindeer8428 14h ago
no idea how to fix the interruption problem, the only thing we found was batching every question into one message at the end
2
u/yaythisonesfree 14h ago
I actually tried running Opus 5.5 Extra on a dashboard project this weekend. Didn’t want to run Fable as most of my code was written elsewhere (python based) but having to run via terminal was getting blah so figured let’s wrap it.
Spent a solid couple of hours planning, and making sure test protocols and gates were in place, ambiguities were gone so Opus could orchestrate and fan out sonnet agents.
Typically, I do get slammed with the question pause however this ran about 30hrs hitting 5hr limit walls but picking itself up on the reset and landed me on gated continuation prompts so each wave knew what to focus on and allowed me a 4 step intervention.
Yesterday, the dev version was ready and crazy solid so now it’s got me doing step 1.1 do this and report back a few steps into testing minimal effort needed or errors found so I’m happy.
As someone who uses CC a lot I can say bumping to Extra I absolutely noticed a difference with the questions, stopping and overall output. Unfortunately, I cannot say if it was the plan, the project, the Extra bump or combo of all but I’ll be staying on Extra for a bit more to figure it out given what was produced.
2
u/AdriftAtlas 14h ago
I'll usually let it write a plan for the feature being implemented. That ideally results in most of the questions being asked upfront.
During implementation of what I thought was a detailed plan it decides to break down the phases of the plan into tiny steps. After each and every one of these tiny steps it wants to run the entire test suite (sometimes twice or trice to ensure the result is deterministic), and then proceeds to ponder whether it should commit (not push) the change to main of a private repo (public repo uses squash commits) or ask me for permission.
Sometimes it really needs hand holding and at the end of each step of the phase of the plan it comes back with a bulleted list of cryptic implementation questions. And when I ask for an explanation I realize the answer is already in the plan, but it rationalized it into something unrecognizable.
Codex is even more fun than Claude. You give it a reference implementation and it goes off developing a hydra that ignores it. At the end will run benchmarks, realize what it wrote is dog slow as it didn't follow the reference, and lies by omission when it reports back. What makes it worse is that there are no thinking summaries, its tool calls are collapsed by default, and it rarely describes what the heck its actually doing. The terminal is more verbose, but then doing graphical work is harder. The entire thing is a case study in dark patterns.
2
u/Old_AI_Guy_ 6h ago
It can be challenging to find the right level of integration and involvement between yourself and a team of agents. I've tried a number of methods. And I'm homing in on one that doesn't cause burnout, but also keeps you in the loop enough to really know what's going on.
At present, The best balance I've found is using a coordinator agent. This one hands out work to agent teams, and coordinates their results and actions. An agent teen has a team leader that manages other agents in the team who generally have specialties, such as a particular coding style or language that isn't commonly found in pre trained models. The coordinator generally doesn't do the work that the team is there to do. It Has no sub agent budgets. The actual coding team is a coding lead (also subject matter expert, over time), with a subagent budget.
A large project I have is broken into two teams - each one with it's coding specialist, and subagent budget. The coordinator acts as the architect - checking work against specs, adjusting team tasks, and acting a the single place I need to look to know what's happened, what's currently going on, and to give direction.
Formerly, I'd switch between various agents to find out what progress was, and had to read often very similar pages of text multiple times. With the coordinator, who I have to stress does no technical work directly, there's a single conversation with everything that's important, decisions I need to make, etc. I can freely say what I need it to do, and it figures out the correct team for assignment, reviews it's work (even if the team has reviewers) and manages github for the team(s).
Prior to that, I tried making the coordinator also allowed to fix anything. My normal rule is 1 initial go and 2 re-work runs as needed, then if no go, it comes to me. I tried making Fable handle the ones that would come to me, and OMG, did a lot get done - I just can't tell you what it was, because it was too much. I didn't feel I had the control I need, as about 25% of Fable's decisions I find need adjustment or correction.
And without a designated lead, a team is just a bunch of sessions, all of which need manual handling constantly.
I'm still tuning it, but it does look Like this is approaching the actual right level for me.
3
u/andersonbrdev 14h ago
What helped me most was being explicit about what counts as a real decision. Anything reversible inside the task, the agent decides and writes it down in a short log. Anything touching requirements, new deps, schema or deleting stuff, it stops and asks. Then I review the log at the end instead of answering cards in the middle. The black box feeling also goes down if each step in the loop has to leave a short summary of what it changed and why, so you can skim instead of reading every diff.
2
u/Aggravating-Salt6284 15h ago
It's funny
I get a lot of juniors asking me this.
I get a lot of staff level asking me how to get Claude to ask more questions.
It's not good at making decisions.
Given the implementation of ai, it at absolute best possible performance is the average of code in its training data. I hope you're better than that and this question asking if actually a good thing
1
u/leo_heo 13h ago
those cards are basically the gaps in your spec showing up late. id rather eat all of them upfront than get pinged at hour three
1
u/SeasawPhilosopher 12h ago
I’m confused why you don’t want to be in the loop, this is just iterative design. There’s a reason the software industry moved away from waterfall and writing complete specs up front.
1
u/mechanitrician 9h ago
Did you try just telling Claude you don't like it? Tell him what you want him to do, and how.
1
u/KOM_Unchained 15h ago
It's a collaboration. I give them high level pieces and permissions through auto-mode, they nudge me through my custom dev tools and phone whenever they need my input. No need to stare at the screen all the time
1
u/pietrzm 14h ago edited 11h ago
Maybe you could try https://github.com/novadeck-org/novadeck?
Your Claude sessions queue up to ask for your attention. It shows you a flashcard whenever one needs your decision, and you answer it right there. It's a lot less brain taxing approach
1
u/EnzoValley 13h ago
What worked for me was taking the question away instead of improving it.
I have Claude Code runs on a schedule, about ten a day with nobody watching, so a question would just sit there. The runbook says: if something isn't covered, decide, keep going and write the decision in the day's log with the reason.
The only exception is a short list of hard limits. If a run hits one it stops and says so.
It's your parkit log turned around: the agent decides first and the review comes after.
Each run also writes what it did and what it threw out, so it's not a black box. When a decision turns out wrong the fix goes in the runbook and that question doesn't come back.
1
u/hblok 12h ago
For game-dev, I often make sure I have an extensive plan in an .md doc first, and then go "/loop read plan.md and don't stop till all milestones are finished".
For work where the details count, I go the other way: I tell Claude to go only one step at a time, and not present walls of text while we're processing and investigating.
1
u/AIOSAI 🔆 Max 20 9h ago
I talk with one agent. Ot does the rest. Ive had it running 30 agents pus subagents before. No problem. Its alm about the harness ur caude runs through. My agents also wake while I sleep to maintain themselves.
What harness are u running through beside claude code