The reply lands in the parent
Two CC 2.1.248 changes to cross-session messaging that every ork agent and skill granting SendMessage now states in its own text (#3772, #3773). Pick who sends; watch where the answer goes.
1. Who sent it decides where the reply goes
The main session sent, so the peer's reply arrives in the main conversation. Nothing surprising.
Before 2.1.248 the tool result from a subagent's SendMessage said nothing about this, and a subagent could reasonably wait for an answer that could never reach it. The changelog entry is filed as breaking for exactly that reason: the rule did not change, the visibility of it did. ork's text now says it where the tool is granted: send and move on, the parent reads the answer.
2. Where it works
| Setup | before 2.1.248 | 2.1.248 and later |
|---|---|---|
| Anthropic first party, telemetry on | works | works |
| Amazon Bedrock | no peers | works |
| Google Vertex | no peers | works |
| Microsoft Foundry | no peers | works |
telemetry disabled (DISABLE_TELEMETRY=1) | no peers | works |
Same machine, macOS and Linux, unchanged. "No peers" was silent: ListAgents returned an empty list and the caller fell back to polling files. That fallback is no longer justified by the provider or by telemetry being off.
3. Proof that every mention states it
| Surface | grants or mentions SendMessage | states both facts |
|---|---|---|
src/agents/*.md (frontmatter grant) | 19 | 19 |
src/skills/*/SKILL.md (any mention) | 10 | 10 |
Enforced from now on by tests/agents/test-agent-messaging-scope.sh rule (c) and tests/skills/test-skill-sendmessage-reply-note.sh; both rosters are derived by grep, so the 20th agent is covered the day it lands. Negative control: deleting one note makes each test fail.