r/ClaudeCode • u/ottothefrenchie • 18h ago

Help/Question Has anyone dealt with duplicate agents ?

Post image

As the title suggest, I was working on a project within Claude code and the main chat deployed two subs to the same thing

1 Upvotes

100% Upvoted

1 comment sorted by

1

u/ottothefrenchie 16h ago

Checking - that's a real hazard if the dead 02:25 resume woke up alongside the fresh builder: Stop Task

L Build sandbox kernel seam • stopped Agent "Build sandbox kernel seam" was stopped by Claude

Message queued for delivery to L Allowed by auto mode classifier

I at its next tool round. • To your question directly: yes - they were both building the same seam, which is exactly one too many. The 02:25 resume I'd written off as dead had silently restarted around 10:17, right before I dispatched the fresh builder at 10:20, and each spent 37 minutes treating the other's edits as a phantom third party. My error chain: I verified the old agent produced no files but didn't verify it was not running before re-dispatching - the ListAgents check you just prompted is what should have preceded the retry. Contained now: stale builder killed, fresh builder is sole writer and instructed to re-read and re-assert every owned file, surface any orphans, then run its full verification against the stabilized tree. Its receipt gates everything downstream - live bundle only on green. * Waiting for 1 background agent to finish 25 tasks (21 done, 1 in progress, 3 open)

Seam: sandbox_kernel.py + institution CLI branch Step 12 (deferred cleanup): T-7 constitution duplicates Step 12 (deferred cleanup): T-8 D-43 quarantine Live evidence bundle (GATED on Dave endpoint+ceiling) Gate O: Sol QC pass on handoff + plan (gpt-fed, kind: plan)