From d48537b7a54d942357ffd144c07b50d2d435110f Mon Sep 17 00:00:00 2001 From: gsxdsm Date: Wed, 15 Jul 2026 13:07:59 -0700 Subject: [PATCH] docs: correct FN-7779 changeset dev field to the shipped ACP path The dev field described the pre-ACP adapter: stderr capture, NDJSON error event bridging, and subprocess exit-code inspection. That implementation was replaced by the native ACP transport rewrite (grok agent stdio) on 2026-07-11, which carries the FN-7779 invariant forward through onText diagnostics rather than stderr scraping. The user-facing summary was already accurate; only the developer-facing mechanism was stale. Describe the paths that actually ship. Co-Authored-By: Claude Opus 4.8 (1M context) --- .changeset/fn-7779-grok-empty-message-root-cause.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 .changeset/fn-7779-grok-empty-message-root-cause.md diff --git a/.changeset/fn-7779-grok-empty-message-root-cause.md b/.changeset/fn-7779-grok-empty-message-root-cause.md new file mode 100644 index 0000000000..ff31936f0a --- /dev/null +++ b/.changeset/fn-7779-grok-empty-message-root-cause.md @@ -0,0 +1,7 @@ +--- +"@runfusion/fusion": patch +--- + +summary: Grok CLI failures now show the actual error instead of an empty chat message. +category: fix +dev: `GrokRuntimeAdapter` surfaces every silent-failure path as visible `onText` text plus an assistant message and `state.errorMessage`, instead of resolving into a blank bubble. Covers session-create failure (`describeCreateFailure`, which returns a dead session), prompt failure (`describePromptFailure`), a dead/disposed session with no ACP connection on a follow-up turn, and a turn ending with a non-`end_turn` stopReason and no assistant text. A turn with genuinely empty assistant text stays silent. Resolve-never-reject is preserved so chat/executor always receive a well-formed turn. Fixes the root cause behind the FN-7779 "No message" placeholder.