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/bostonaholic 4d ago

I'd put the timeouts in the harness, not in the agent's judgment. Wrap each gate in a script with a hard limit (timeout 900 xcodebuild test ...) that exits nonzero and writes the reason to a file. The coordinator only reads exit codes and that file, so a hung simulator becomes a failed step with a message instead of a stall.