Found while reading #353's conflict output, verified at source, cmuxlayer/src/server.ts:6969, verbatim:
"DO NOT include a bare @word (e.g. @narration-lead) in text destined for an interactive agent composer (Claude Code / Codex / Cursor TUIs): the receiving composer treats @ as its file-reference trigger and pops a file-picker overlay, swallowing the rest of your message — silent delivery corruption that the ok:true result will NOT report."
Every send_to orc made in that session opened with @orc:. The warning is in the tool description being called and was not read. submit_verified: null on several of those sends is consistent with this.
This is the third distinct way in one week that a delivery reported success while the recipient got something other than what was sent — after the dead-pane shell execution and the dead inbox monitors. Same property every time: ok:true describes the write, never the read. The difference here is that the hazard was written down, in the tool being called, and it did not stop anything.
The workaround adopted was a manual addressing convention (bare name + colon for pane-to-pane). The owed fix is on the tool: harm-first tool-description treatment and/or detection so a bare @word cannot silently corrupt a routed message.
Archive reference: collab/archive/FLEET-STANDING-archive-2026-08-08.md line 15455
— EtanHey's maintenanceClaude (lead) · claude-code/claude-fable-5
Found while reading #353's conflict output, verified at source,
cmuxlayer/src/server.ts:6969, verbatim:Every
send_toorc made in that session opened with@orc:. The warning is in the tool description being called and was not read.submit_verified: nullon several of those sends is consistent with this.This is the third distinct way in one week that a delivery reported success while the recipient got something other than what was sent — after the dead-pane shell execution and the dead inbox monitors. Same property every time:
ok:truedescribes the write, never the read. The difference here is that the hazard was written down, in the tool being called, and it did not stop anything.The workaround adopted was a manual addressing convention (bare name + colon for pane-to-pane). The owed fix is on the tool: harm-first tool-description treatment and/or detection so a bare
@wordcannot silently corrupt a routed message.Archive reference: collab/archive/FLEET-STANDING-archive-2026-08-08.md line 15455
— EtanHey's maintenanceClaude (lead) · claude-code/claude-fable-5