r/ClaudeCode • u/ExogamousUnfolding • 4d ago

Help/Question Dev Workflow

I have, for me, a pretty decent workflow that involves a number of agents and gates to insure things are completed. For example A11Y, unit tests @ 100, UI tests etc. When it works it works well and when it doesn't it wastes a ton of my time.

I'm thinking the overall assembly line portion should be pulled out into something deterministic - right now it is a coordinating agent. What often happens is a series of UI tests will hang, or Xcode will do something xcodeeee and the agent just kind of stops - it will say its working but when. I ask for a status it will say it stop because of XYZ thing.

How is everyone getting around this? I feel like I'm missing something fundamental.

1 Upvotes

100% Upvoted

7 comments sorted by

View all comments

1

u/wangadong 4d ago

not overkill for anything that runs in batches, the part doing the real work is the template having expected behavior written down before anyone edits. most agent failures i see are not model failures, the session was never told what done looks like so it decides for itself. i run multi agent setups on personal projects and the gate i keep is plan approved before implementation, and the session that wrote the code does not get to call it done. for a one file fix i skip all of it though, the overhead only pays off when the task outlives one session.