Summary
deepseek app-server --stdio advertises response_delta support, but thread/message returns accepted without streaming any real model text to stdout.
Environment
- DeepSeek-TUI version: observed on
v0.8.14
- Transport:
deepseek app-server --stdio
- Integration impact: third-party stdio clients cannot consume assistant output in real time
Steps to reproduce
- Start the app server:
deepseek app-server --stdio
- Start a thread:
{"jsonrpc":"2.0","id":1,"method":"thread/start","params":{"cwd":"/tmp"}}
- Send a message:
{"jsonrpc":"2.0","id":2,"method":"thread/message","params":{"thread_id":"thread-xxx","input":"Say hello"}}
- Observe stdout events.
Expected behavior
Between response_start and response_end, stdout should contain one or more response_delta push events with real assistant text.
Actual behavior
The stdio stream only emits response_start and response_end, then returns a JSON-RPC result with status: "accepted". No actual assistant text is streamed.
Impact
Any third-party integration that depends on the documented stdio event stream sees an empty model response and cannot function correctly.
Additional context
I already opened PR #1141 with a fix and regression coverage for this behavior.
Summary
deepseek app-server --stdioadvertisesresponse_deltasupport, butthread/messagereturnsacceptedwithout streaming any real model text to stdout.Environment
v0.8.14deepseek app-server --stdioSteps to reproduce
{"jsonrpc":"2.0","id":1,"method":"thread/start","params":{"cwd":"/tmp"}}{"jsonrpc":"2.0","id":2,"method":"thread/message","params":{"thread_id":"thread-xxx","input":"Say hello"}}Expected behavior
Between
response_startandresponse_end, stdout should contain one or moreresponse_deltapush events with real assistant text.Actual behavior
The stdio stream only emits
response_startandresponse_end, then returns a JSON-RPC result withstatus: "accepted". No actual assistant text is streamed.Impact
Any third-party integration that depends on the documented stdio event stream sees an empty model response and cannot function correctly.
Additional context
I already opened PR #1141 with a fix and regression coverage for this behavior.