xonecas.io
60255
Zn

Zoea-Nova / commit 18e900d

docs: document OpenCode input_tokens crash issue

Added documentation for the undefined input_tokens error that causes
myses using OpenCode providers (zen-nano, zen-pickle) to crash.

Issue Details:
- Error: Cannot read properties of undefined (reading 'input_tokens')
- Observed: nano mysis crashed at 2026-02-09 04:14:57 UTC
- Impact: Mysis enters errored state and stops operating
- Root cause: OpenCode response may not include usage.input_tokens field

Recommended fixes:
- Add defensive null checks for usage statistics
- Make usage statistics optional/non-fatal
- Log raw response on parsing failure for debugging

This is separate from the existing gpt-5-nano endpoint workaround
issue and affects response processing rather than endpoint selection.

xonecas2026-02-09 18e900d61f744261c3d1e9e21a5e65366745574e parent b0e8a92

1 file changed

documentation/current/KNOWN_ISSUES.md+14−0
@@ -29,6 +29,20 @@ Active todo list of known issues, bugs, and planned improvements for Zoea Nova.
2929
3030 ### Provider Reliability
3131
32+- [ ] **OpenCode provider crashes with undefined input_tokens** - Provider returns 500 errors when processing usage statistics
33+ - **Error:** `Cannot read properties of undefined (reading 'input_tokens')`
34+ - **Impact:** Causes myses to enter `errored` state and stop operating
35+ - **Observed:** 2026-02-09 04:14:57 UTC - `nano` mysis (zen-nano provider) crashed after multiple successful turns
36+ - **Pattern:** Error occurs during response processing, likely in usage statistics handling
37+ - **Root cause:** OpenCode provider response format may not include expected `usage.input_tokens` field, or field is null/undefined
38+ - **Location:** Provider response parsing in `internal/provider/opencode.go` or OpenCode SDK
39+ - **Workaround:** None currently - requires provider restart to recover
40+ - **Action needed:**
41+ - Add defensive null checks for usage statistics fields
42+ - Make usage statistics optional/non-fatal
43+ - Log raw response when usage parsing fails for debugging
44+ - **Related:** May be connected to zen-nano vs zen-pickle provider differences
45+
3246 - [ ] **OpenCode Zen endpoint workaround for gpt-5-nano** - Using `/chat/completions` instead of documented `/responses` endpoint
3347 - **Issue:** Official docs specify `gpt-5-nano` uses `/v1/responses` endpoint, but this returns HTTP 500 errors
3448 - **Error:** `request failed after 3 retries: chat completion status 500` with server error mentioning `input_tokens` (Anthropic field)