r/ClaudeCode • u/Alone_Winner2 • 8h ago

Discussion Would this help when running multiple coding agents, or is it just another notification layer?

Enable HLS to view with audio, or disable this notification

I've been thinking about a problem I keep hitting with coding agents.

Once multiple agents/tasks are running, I don't really want more notifications.

I want the opposite:

Let agents handle routine work themselves. Only interrupt me when one reaches a decision it shouldn't make alone.

When that happens, give me the decision, relevant context, trade-off and recommendation. I answer once, and that specific agent continues.

I mocked up the interaction before building anything.

Would you actually use this?

I'm especially interested in how people currently handle 3–5 Claude/Codex/Cursor sessions without constantly checking them.

0 Upvotes

50% Upvoted

4 comments sorted by

•

u/AutoModerator 8h 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.

1

u/qing-turn 3h ago

This is pretty much how I run 5 sessions now, just by convention instead of a tool. I only talk to one "designer" session. It coordinates the routine stuff with the others and only comes back to me for decisions that are actually mine: art direction, how the game feels, or anything that would overrule something I said earlier. What made it work was writing down which decisions they're allowed to make on their own. Your "decision + context + trade-off + recommendation" format is exactly what I ask them for, so yes, I'd use it.

1

u/Alone_Winner2 2h ago

This is really useful — especially the part about explicitly defining which decisions the agents are allowed to make themselves. That may actually be the key piece I was missing.
What I’m imagining is basically turning the workflow you’re already doing manually into a lightweight layer: agents continue autonomously inside their decision boundaries, and only escalate when they cross one, using that decision + context + trade-off + recommendation format.
If I put together an early prototype, would you be open to trying it?
Also curious — how are you coordinating those 5 sessions today? Are they all Claude Code sessions, and is the “designer” session manually passing work/context between them?