Back to Signal Feed
ProductionTracked since May 22, 2026

cc-connect opencode tool calls return blank outputs on Feishu under Windows/WSL

An open issue in cc-connect v1.2.1 reports that opencode mode can start sessions and complete turns but returns empty output for tool calls such as `whoami` and file reads, which means the assistant’s core command/result flow is no longer observable for end users, a critical functional regression for operators relying on tool execution.

cc-connectopencodeFeishuWindows 11

What Happened

  • An open issue in cc-connect v1.2.1 reports that opencode mode can start sessions and complete turns but returns empty output for tool calls such as `whoami` and file reads, which means the assistant’s core command/result flow is no longer observable for end users, a critical functional regression for operators relying on tool execution.
  • An open issue in cc-connect v1.2.1 reports that opencode mode can start sessions and complete turns but returns empty output for tool calls such as `whoami` and file reads, which means the assistant’s core command/result flow is no longer observable for end users, a critical functional regression for operators relying on tool execution.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Pinpoints a concrete behavior defect in the opencode tool-response path where session lifecycle logs are present but response payloads are not delivered, which is vital for debugging and prioritizing a fix because it blocks verified command-based workflows rather than minor UI or config noise.

Why Track This

Why It Matters

Operators using cc-connect as an Lark/Feishu assistant on Windows/WSL cannot get command output or file-read results, so automated or interactive tool-driven workflows become non-functional even though tasks appear to complete. The logs repeatedly show session start/complete events without visible response content, so teams should watch whether response frames are dropped after execution, especially in the stream/preview branch (`hasHandle=false`, `degraded=true`), and validate fixes in both command and read-file paths in upcoming versions.

Impact

Operators using cc-connect as an Lark/Feishu assistant on Windows/WSL cannot get command output or file-read results, so automated or interactive tool-driven workflows become non-functional even though tasks appear to complete. The logs repeatedly show session start/complete events without visible response content, so teams should watch whether response frames are dropped after execution, especially in the stream/preview branch (`hasHandle=false`, `degraded=true`), and validate fixes in both command and read-file paths in upcoming versions.

What To Watch Next

  • Watch whether cc-connect becomes a repeated pattern.
  • Track follow-up changes around Tool Calling.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: tool_output_dropped, opencode_session_response_gap.
Open Topic TimelineOpen Technical EventOpen Original Sourcetool_output_dropped / opencode_session_response_gap / windows_wsl_feishu_integration / degraded_stream_mode_handling

Supporting Evidence

GITHUB ISSUEHigh Trust

cc-connect opencode tool calls return blank outputs on Feishu under Windows/WSL

Open the original source to review the supporting evidence.