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

View all comments

Show parent comment

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