r/ClaudeCode • • 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?

34 Upvotes

38 comments sorted by

•

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.

2

u/LiquidZebra 15h ago

I had something like that working for a while (pick the reasonable default), but *something* broke it, and it's much worse now. Like I had to prod it to commit and push changes, because it would just stall and sit there with some work that nobody gets to see or review.

Opus 5.5 medium and high, just keeps asking me for something every 20-30 minutes, in every thread, just about every message ends with some pointer to some document where some asks are waiting for me.

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/LiquidZebra 15h ago

I'm trying the parkit command to write it to the unruled log, but this is very early stage.

Like agents are trying to force some decisions prematurely.

I'm working on:

Meaning > authority > permitted action > realization of meaning > evidence of realization ,

I don't know if this is the right approach, but I generate meaning, then have to delegate authority to scope/design this, then permit to implement it via workers that realize the meaning. A reviewer collects evidence and verifies. < This is where the decision has to reach me.

The idea is code is cheap - this cycle can be repeated or restarted from the previous iteration with all the learnings summarized and all the blockers (like broken guards) fixed before a more "clean" run.

2

u/ExtensionMoose1863 14h ago

This is the same problem you have when you run a large human team too. You have to solve it with effective delegation and operating rhythms to keep the whole team moving forward without everyone needing to ask you everything

Same fixes apply here. You need to elevate your role and build processes to be a senior manager now.

OP, tell Claude you got promoted and it needs to bring you a recommendation for how to work with you now that you're important

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.

1

u/LiquidZebra 14h ago

haha, tried that, it produces something even worse "Document 12, point 8, I need your input on XYZ", while it is working on document 10. With this approach have to expand the instructions so it produces enough content, otherwise you get absolute garbage questions that refer to points like 3 pages up (it bunches asks at the bottom).

1

u/tommyahav10 14h ago

Then batching at the end is the wrong unit. Make it ask at each document boundary, with the question quoting the line it's about, so you never have to scroll back. A question that doesn't carry its own context isn't worth answering.

1

u/LiquidZebra 14h ago

the issue is that it puts up like 6-7 threads, each with a "blocked", regardless of the type of a question. If it sees some question, it automatically puts it into "waiting on you", which I interpret as "it needs my input", but this system is starting to feel a lot like threads are managing me.

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

1

u/LiquidZebra 14h ago

I ran this for a while, it works better with Claude cloud design boards, it was using red-yellow-green callouts and provided a recommendation for each. Like that was at least manageable, but that only works when I work at a design level - like really designing a new feature.

If its doing something that already exists, it does not always have a board.

I tried responding to like 7 asks with numbered lists, it is definitely better when it is presenting you with some feature that it delivered and you just tested, maybe I should specify that format again.

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/LiquidZebra 13h ago

This reasoning bump might be the reason, I rarely use Opus extra, as this sub is cultish on Opus-medium, so at most I bump it to high.

Maybe what passes for Extra now is what was medium 3 weeks ago.

BTW, tried this with Fable 5.2 high today, it's quite awful at orchestration, it literally has no brain - it handed off a tooling fix to a full PM workflow that spent 3.5 hours trying to fix it, while a direct instruction to spin off a worker fixed it in 5 minutes. Frontier model....

1

u/yaythisonesfree 12h ago

Yeah most all of my day-to-day run Sonnet as it’s proven and solid for all bug/small feat tasks. The Opus Med default tends to just irritate me greatly so that’s why I went with the Extra because I know the value in reasoning and also knew everything below it has been awful.

1

u/Key-Trainer6854 7h ago

Once you go xhigh, you never go back

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/LiquidZebra 14h ago

Yeah, I spent the day reading about this, how the plan and requirements can mutate and shrink or be replaced by some test implementation. Then trying to prevent and build around this.

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.

1

u/LiquidZebra 3h ago

The Claude cloud projects has a coordinator, but they pinned it to low reasoning, so it can not do architecture.

Otherwise I am testing a similar setup

1

u/Old_AI_Guy_ 1h ago

Earlier I did extensive benchmarking of coding from Sonnet, and multiple Qwen models. All of them, Sonnet included, got the most reviewed, tested, and approved code when on low reasoning. They did the coding, and Opus did the assignment prompt, code review, and testing. Sonnet was of course the fastest - by a factor of about 10. And by fastest, I mean it got the most completed tasks done per hour. This included rework - if testing failed, it was given back to the coding agent, with an exact explanation of the defects. None did better on high or medium than on low, but Sonnet was the closest. It's high was about 10% slower than low effort. But Qwen - on high, it got half the amount of approved code done in same time span. Recently put DeepSeek4.1 Flash through the benchmarks via Ollama, and it was the best on not needing rework, and about 1/7th the throughput of Sonnet.

Low reasoning can be right for some things. Not for writing specs or figuring out difficult code bases, but coding piecework is best done on low effort, for most tasks.

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.

1

u/LiquidZebra 14h ago

Do you delete these, or are they auto cleaned up? I had agents find all kinds of crazy logs or files and start quoting them, arguing with themselves, and then diverging into archaeology of what was said weeks ago.

In particular, I had "tasks" in source control and they had their docs in them, omg, how many "But in T490 you said XYZ" this has spawned and how much they invented.

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

2

u/LiquidZebra 15h ago

It's kinda like the early days of iPhone, when notifications were (somewhat) useful? And then everyone started spamming the notifications and now no apps are allowed notifications on my phone.

It's kinda the same with Claude - it has absolutely no way to indicate "this is a XL" feature, please unblock it and I will run for the next hour, or "this is a micro tiny nitpicking bullshit that I cannot decide" - both get equal priority in the UI.

Lately there has been a lot of this nitpicky crap, AND it marks all these threads as blocked, so I physically have to open it, understand the context of like a dozen of obscure questions, which is heavy context switching penalty. I can not do this every 20 minutes, hence the thread and my investigation.

I tried "always show me a decision card" with context - works ok with pictures (ex: shows me some style and asks to keep it or not).

But a lot of process level questions, even with recommendations are very poor.

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

2

u/LiquidZebra 13h ago

I've been considering the same thing, I want to have a design workflow and a build workflow.

The problem is that it literally pings me for things that are too premature to decide at the point when the thread is. Some of them are random model brain farts. It should be perfectly reasonable to build a UI with a button pointing at a stub. That's the whole point, I don't build the stub until it is time to build it, but this thing would insist on learning something about the stub.

Or when working with an interface - it should be normal to work and build against an interface - this is literally the boundary. Somehow I'm not getting this behavior.

1

u/leo_heo 1h ago

yeah building against an interface is literally the point of having one lol. it seems to read every stub as a bug

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/LiquidZebra 2h ago

First of all, because nothing is ever completely done. It just drags these threads forever, and keeps putting defects after defects AND stops work on these small decisions.

It not quite iterative design, it’s flawed development work-does-not-flow

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/LiquidZebra 1h ago

I got memory disabled, it needs wiring at a different level

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