File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -17,6 +17,14 @@ That failure is worse than it sounds: the offending tool result is already in
1717session history, so ** every subsequent turn fails too** — the session is
1818permanently poisoned until you manually roll messages back.
1919
20+ Tracked upstream as
21+ [ anomalyco/opencode #58354 ] ( https://github.com/anomalyco/opencode/issues/58354 )
22+ — reproduction confirmed through ` dev ` (` 09399e3 ` ); see also
23+ [ #51351 ] ( https://github.com/anomalyco/opencode/issues/51351 ) (NUL in the shell
24+ * command* hangs the tool) and
25+ [ #57833 ] ( https://github.com/anomalyco/opencode/issues/57833 ) (` read ` and
26+ invalid UTF-8).
27+
2028Common sources of NUL bytes in tool output:
2129
2230- Raw git protocol output. Git's pkt-line protocol separates the ref list
Original file line number Diff line number Diff line change 11// nul-guard: strips NUL bytes out of tool output before it reaches the model.
22//
3+ // Upstream: anomalyco/opencode#58354 (shell tool output with NUL bytes bricks
4+ // the session with "Invalid request parameters"; reproduced through dev).
5+ //
36// Raw git protocol output (git-upload-pack / serv handshakes), binaries catted
47// to stdout, and similar sources contain literal \0 bytes. Providers such as
58// venice/z-ai validate request content and reject any string containing NUL
You can’t perform that action at this time.
0 commit comments