Team Interrupt
SendMessage is for idle/hibernated agents only. If the agent is working, the message sits in the queue and is processed later against stale context - answers will be obsolete and queued instructions may already be wrong. To reach a working agent, use Interrupt + SendMessage. Never queue status checks, redirects, or corrections behind active work.
Procedure
- Run (use
developer-cliexactly as written - do not expand to an absolute worktree path):dotnet run --project developer-cli -- claude-command send-interrupt-signal --team <team> --agent <agent> - Capture the stdout line - a single
#<id>interrupt ID. - Send a follow-up
SendMessageto the same agent with the body prefixed by that ID:#<id> <your instruction> - STOP - no follow-ups.
The ID links the signal to the correct queued message; the active agent skips stale messages until it sees the matching ID.