## Environment - Claude desktop app (Windows, MSIX): **1.28929.0** (auto-updated from 1.26832.0 on 2026-08-12 ~10:10 local) - Claude Code runtime: broken on **2.1.227**; **retested after updating Claude Code to 2.1.231 (2026-08-13, app restarted) — still broken** (session resumes and loads the transcript on delivery, but no responding cycle starts; no reply received). Release notes for 2.1.229/2.1.231 mention no related fix. - Windows 10 Pro 10.0.19045 - Messages sent via the `ccd_session_mgmt`

Cross-session send_message delivers to the target session's queue but never triggers a responding turn (regression in desktop 1.28929.0 / CC runtime 2.1.227, still broken in 2.1.231)

Status Closed — duplicate

Reported on v2.1.227

Maintainer reply None cached

Workaround ✓ Mentioned in thread ↓

Activity 5 comments · opened Aug 13, 2026 · closed Aug 15, 2026

Environment

Claude desktop app (Windows, MSIX): 1.28929.0 (auto-updated from 1.26832.0 on 2026-08-12 ~10:10 local)
Claude Code runtime: broken on 2.1.227; retested after updating Claude Code to 2.1.231 (2026-08-13, app restarted) — still broken (session resumes and loads the transcript on delivery, but no responding cycle starts; no reply received). Release notes for 2.1.229/2.1.231 mention no related fix.
Windows 10 Pro 10.0.19045
Messages sent via the ccd_session_mgmt MCP send_message tool between local sessions

Summary

Since the 1.28929.0 update, a message sent from one local session to another with send_message is correctly enqueued into the target session (it appears in its transcript as a <cross-session-message> user turn), but the receiving agent never runs a turn over it. The queued message only surfaces when the user manually types anything into the receiving session — it then flushes into that turn together with the user's input.

On 1.26832.0 the receiving session responded to cross-session messages automatically. This broke agent-to-agent report delivery workflows.

Steps to reproduce

Have two local sessions, A and B; leave B idle.
From A, call ccd_session_mgmt send_message targeting B.
Observe B: the message appears in B's transcript, but no response cycle produces output. main.log shows either no query cycle at all, or a delivery cycle that runs and ends with hadFirstResponse=false (observed: 65s and 235s cycles with zero output, one killed by warm-lifecycle/MCP-reconfig housekeeping).
Type anything into B (even "."): the queued message is processed immediately in that turn.

Evidence from `%APPDATA%\Claude\logs\main.log`

Cross-session send to an unloaded session: Resuming session <id> fires (wake works), then LocalSessions.interrupt + healthy cycle … (235s, hadFirstResponse=false) — no output ever produced.
Same pattern on a loaded session: cycle ends (65s, hadFirstResponse=false).
User-typed input to the same session immediately afterward: LocalSessions.sendMessage → healthy cycle with hadFirstResponse=true, and the queued cross-session message is answered in the same turn.
Every send that produced a real response has a preceding LocalSessions.sendMessage (user-typed input); cross-session sends never do after the update.

What we ruled out

Not message loss — content always reaches the target's transcript/queue.
Not fixed by app restart — failures span a full relaunch.
Not session age — brand-new sessions (created after the update) fail identically.
Also reproduced between two sessions both created under CC runtime 2.1.231 (2026-08-13): send logged (Sending message to session <target>) at 16:22:43; no query-start or model activity follows.
UI side effect (2.1.231 repro): the receiving session's UI shows the message plus a pulsing Claude indicator and a running timer (kept counting past 11 minutes), without the usual token counter / activity verbs of a real query — a stalled "processing" state.
Smoking gun (2.1.231 repro): the incoming cross-session message is delivered as a held steer. When the user typed one character into the receiving session (16:34:05), main.log shows [LocalSessionManager] flushed held steers (1 steer(s)) for <target> (16:34:35), the model responded within seconds, and the cycle closed as healthy cycle … (718s, hadFirstResponse=true) — i.e. one cycle had been open since delivery (16:22:43) with the message held the whole time. The regression appears to be that cross-session messages are classified as steers that are held indefinitely; nothing flushes them until a user-typed message arrives.
Post-flush behavior is also degraded (2.1.231 repro): after the flush, the receiving agent replied only to the user's typed character ("the dot arrived, ready") and completely ignored the cross-session message's instruction (it was told to send a labeled ACK back via send_message; no ACK was ever sent, and the agent showed no awareness of the message). The message is visible in the session's transcript UI, but the model's flushed turn behaves as if it only received the user's character. In earlier repros on 2.1.227 the flushed message was answered in the same turn, so this may be a second regression or an intermittent variant.

Expected

The receiving session runs a responding turn over an incoming cross-session message automatically, as in 1.26832.0.

View original on GitHub ↗

3 Comments

MilkyWay008 · 17 days ago

Solid writeup \u2014 and the fact it survives the runtime bump to 2.1.231 points at the desktop shell rather than CC itself. Worth testing a rollback of the MSIX to 1.26832.0, the last known-good, and disabling auto-update while you're there; that at least unblocks agent-to-agent delivery until a fix lands. The held-steer evidence you captured should make this easy for them to reproduce.

Blackthornes · 17 days ago

<html>
<body>
<h2 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 17px; font-weight: 580; text-rendering: optimizelegibility; line-height: 22px; letter-spacing: -0.01em; color: rgb(240, 239, 236); margin-block: 24px 8px; padding-block: 0px; font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Still broken on desktop app 1.30096.1.0 + runtime 2.1.229 — and the recipient hard-freezes</h2><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Confirming this on the<span> </span><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">newest desktop build</strong>, which extends the regression window past 1.28929.0. Adding one detail that I don't see stated elsewhere in the thread and that changes the severity:<span> </span><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">the recipient does not just fail to respond — it wedges, and stays wedged until manually stopped.</strong></p><h3 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 15px; font-weight: 580; text-rendering: optimizelegibility; letter-spacing: -0.01em; margin-block: 20px 6px; padding-block: 0px; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Environment</h3><div class="overflow-x-auto" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); overflow-x: auto; text-rendering: optimizelegibility; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">
OS | Windows 11 Home, 10.0.26200
-- | --
Desktop app | 1.30096.1.0 (MSIX, auto-updated from 1.28929.0.0 on 2026-08-13)
Bundled runtime | 2.1.229 (both sender and recipient)
Transport | mcp__ccd_session_mgmt__send_message, two local desktop sessions, same project directory

</div><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Both sessions were created fresh after the app update, so this is not a stale-session artifact.</p><h3 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 15px; font-weight: 580; text-rendering: optimizelegibility; letter-spacing: -0.01em; margin-block: 20px 6px; padding-block: 0px; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Repro</h3><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Two idle sessions in one project. Sender asked the recipient to reply with a single line confirming receipt — no tools, no file access, nothing but a text reply.</p><ol style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px 0px 0px 20px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); list-style: decimal; text-rendering: optimizelegibility; gap: 6px; flex-direction: column; display: flex; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">Sender receives<span> </span><code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: anthropic-mono, ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">Message sent to session …</code>.</li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">Recipient's<span> </span><code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: anthropic-mono, ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">lastActivityAt</code><span> </span>advances, and the message lands on the recipient side — it renders in its window and is present in its transcript.<span> </span><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">Delivery itself is real; the break is entirely on the receiving end.</strong></li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">The recipient's working indicator starts spinning and<span> </span><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">never stops</strong>. No thinking trace, no output, no error, no timeout.</li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">It stays in that state indefinitely. The only way out is stopping the turn manually, which returns the session to a normal prompt.</li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">Typing the same text directly into the recipient's input box immediately afterwards works first try.</li></ol><h3 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 15px; font-weight: 580; text-rendering: optimizelegibility; letter-spacing: -0.01em; margin-block: 20px 6px; padding-block: 0px; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Why this is worse than a silent drop</h3><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">The thread so far reads as "messages don't arrive" or "the recipient stays quiet." In practice each send<span> </span><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">costs a manual intervention and puts the recipient's in-flight state at risk</strong>:</p><ul style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px 0px 0px 20px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); list-style: outside; text-rendering: optimizelegibility; gap: 6px; flex-direction: column; display: flex; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">Messaging cannot be used unattended at all. A send to an idle session parks it until a human notices and intervenes.</li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">The success receipt makes it invisible from the sending side, so a coordinating session believes the handoff landed and keeps going.</li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">It retroactively explains earlier confusion in multi-session workflows: sessions that appeared to<span> </span><em style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; font-style: italic;">ignore</em><span> </span>a relay were most likely hung on it the whole time — not declining the work, not missing it.</li></ul><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(240, 239, 236); font-family: anthropic-sans, system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(21, 21, 21); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">We run a multi-session setup where roles hand findings to each other, and we've had to disable cross-session messaging entirely and route every handoff through a shared markdown file. That workaround is stable, but it means the feature is currently unusable for its main purpose here.</p>
</body>
</html>

arthurmoraesfernandes-afk · 17 days ago

This looks like the "wedge" mechanism documented in the follow-up comment on #86298, with app-log evidence: an injected cross-session message that the CLI holds (consent gate) gets drained into the CLI at a turn boundary and is never "echoed" back as a user turn; the app then logs isRunning held by unechoed input at result … pendingEchoUuids: […] and treats the session as busy indefinitely — phantom turn, watchdog kills, and the user's own typed prompts queue/stall behind a turn that never ends until a priority=next send (typing another message force-flushes) or a restart reclaims it. Matches the queue-delivery-without-responding-turn you describe.

Showing cached comments. Read the full discussion on GitHub ↗