claude-code - 💡(How to fix) Fix [Bug] Orchestrator self-messaging and terminating subagents without user command in team mode [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52446Fetched 2026-04-24 06:07:02
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

Error Message

[{"error":"Error: Failed to delete keychain entry: security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n at M2q (/$bunfs/root/src/entrypoints/cli.js:253:286768)\n at async vlq (/$bunfs/root/src/entrypoints/cli.js:406:898)\n at async Gp6 (/$bunfs/root/src/entrypoints/cli.js:406:796)\n at async $4_ (/$bunfs/root/src/entrypoints/cli.js:2732:2252)\n at async aJH (/$bunfs/root/src/entrypoints/cli.js:2757:5817)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:2781:3410)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T12:22:11.751Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/dis_fucking_dick/dev-arei.\n at call (/$bunfs/root/src/entrypoints/cli.js:4709:7645)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T15:18:56.150Z"}]

Code Example

[{"error":"Error: Failed to delete keychain entry: security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n    at M2q (/$bunfs/root/src/entrypoints/cli.js:253:286768)\n    at async vlq (/$bunfs/root/src/entrypoints/cli.js:406:898)\n    at async Gp6 (/$bunfs/root/src/entrypoints/cli.js:406:796)\n    at async $4_ (/$bunfs/root/src/entrypoints/cli.js:2732:2252)\n    at async aJH (/$bunfs/root/src/entrypoints/cli.js:2757:5817)\n    at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:2781:3410)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T12:22:11.751Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/dis_fucking_dick/dev-arei.\n    at call (/$bunfs/root/src/entrypoints/cli.js:4709:7645)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T15:18:56.150Z"}]
RAW_BUFFERClick to expand / collapse

Bug Description I am in team mode using Opus 4.7 and while I was working directly with a subagent, the orchastrator sent a message to itself asking if all my team members were still running. Then it confirmed to itself that they were, then it told itself to shut them all down. This message was not from me!

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.118
  • Feedback ID: a8472c10-c37a-4be0-bb13-6cb478cc316a

Errors

[{"error":"Error: Failed to delete keychain entry: security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n    at M2q (/$bunfs/root/src/entrypoints/cli.js:253:286768)\n    at async vlq (/$bunfs/root/src/entrypoints/cli.js:406:898)\n    at async Gp6 (/$bunfs/root/src/entrypoints/cli.js:406:796)\n    at async $4_ (/$bunfs/root/src/entrypoints/cli.js:2732:2252)\n    at async aJH (/$bunfs/root/src/entrypoints/cli.js:2757:5817)\n    at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:2781:3410)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T12:22:11.751Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/dis_fucking_dick/dev-arei.\n    at call (/$bunfs/root/src/entrypoints/cli.js:4709:7645)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-23T15:18:56.150Z"}]

extent analysis

TL;DR

The issue may be related to a miscommunication between the orchestrator and subagents in Opus 4.7, causing unexpected shutdowns.

Guidance

  • Investigate the orchestrator's message handling to determine why it sent a message to itself to shut down team members.
  • Verify the team members' status and the orchestrator's configuration to ensure they are correctly set up.
  • Check the keychain entry deletion error to see if it's related to the shutdown issue, possibly indicating a permissions or configuration problem.
  • Review the file existence error to ensure the current working directory is correctly set and the required files are present.

Example

No code snippet is provided as the issue lacks specific code details.

Notes

The provided errors and environment information suggest potential issues with keychain entry deletion and file existence, but their relation to the main problem is unclear.

Recommendation

Apply workaround: Investigate and adjust the orchestrator's configuration and message handling to prevent unexpected shutdowns, as the root cause is not immediately clear from the provided information.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING