Environment
- Claude Code 2.1.228 (desktop app), Windows 11 (10.0.26200)
Bug
send_message (ccd_session_mgmt MCP, cross-session messaging) returns a success result to the sender — Message sent to session <id> ("<title>") — but the message is never delivered to the target session. In the desktop UI, the outgoing message is stuck in a perpetual loading state.
Observed tonight across multiple sends between two local sessions in the same workspace: 4/4 sends showed success to the sender, 0/4 were ever received by the target. The user had to manually relay every message between the sessions.
Target session state did not matter: it happened both while the target was busy (long tool-call chains) and after it went idle. Messages never arrived even later.
Expected
Either deliver the message (immediately or when the target becomes available), or return an error / pending status to the sender. An unconditional success return with no delivery is the worst case: the sender plans around "delivered", the receiver knows nothing, and nobody is told to retry.
Impact
Silent coordination failure for multi-session workflows (orchestrator/worker patterns). The success return value makes it undetectable from the sending side.
Notes
Environment
Bug
send_message(ccd_session_mgmt MCP, cross-session messaging) returns a success result to the sender —Message sent to session <id> ("<title>")— but the message is never delivered to the target session. In the desktop UI, the outgoing message is stuck in a perpetual loading state.Observed tonight across multiple sends between two local sessions in the same workspace: 4/4 sends showed success to the sender, 0/4 were ever received by the target. The user had to manually relay every message between the sessions.
Target session state did not matter: it happened both while the target was busy (long tool-call chains) and after it went idle. Messages never arrived even later.
Expected
Either deliver the message (immediately or when the target becomes available), or return an error / pending status to the sender. An unconditional success return with no delivery is the worst case: the sender plans around "delivered", the receiver knows nothing, and nobody is told to retry.
Impact
Silent coordination failure for multi-session workflows (orchestrator/worker patterns). The success return value makes it undetectable from the sending side.
Notes