Intermittent OpenAI streamed server_error (sequence_number:2) with gpt-5.3-codex; retries degrade session

[chindris-mihai-alexandru]

Description

Using OpenCode 1.2.15 with openai/gpt-5.3-codex, I intermittently get streamed JSON errors like:

{"type":"error","sequence_number":2,"error":{"type":"server_error","code":"server_error","message":"An error occurred while processing your request... [retrying in 2s attempt #2]"}}

When this happens, retries may continue but session quality degrades (manual intervention often needed).

Environment

• OpenCode: 1.2.15
• OS: macOS
• Model: openai/gpt-5.3-codex
• Config changes already applied:
  • provider.openai.options.timeout = 600000
  • compaction = { auto: true, prune: true, reserved: 15000 }

Steps to reproduce

1. Start with debug logs enabled: opencode --log-level DEBUG --print-logs
2. Use openai/gpt-5.3-codex
3. Run medium/long coding prompts (tool use involved)
4. Intermittently receive the streamed server_error envelope above

Expected

• Robust handling/recovery for transient streamed provider errors
• Clear surfaced diagnostics for retry classification and provider error details
• Session should not degrade/stall after repeated transient server_error events

Actual

• Intermittent streamed server_error
• Retry attempts occur, but session can still degrade or require manual continue/retry

Related issues checked

I checked similar issues first:

• Opencode with OpenAI stuck in loop with errors #6983 (OpenAI loop behavior)
• Infinite retry loop when StreamIdleTimeoutError occurs during tool input generation #12234 (infinite retry loop on stream idle timeout)
• Agent resets to Build after streaming error #12750 (agent reset after streaming error)

This report is specifically about the OpenAI streamed error payload with sequence_number:2 + server_error on gpt-5.3-codex.

Notes

OpenAI status has had multiple Codex/Responses elevated-error incidents recently, so this might be a combination of upstream transient faults + client-side retry UX/resilience behavior.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Infinite retry loop when StreamIdleTimeoutError occurs during tool input generation #12234: Infinite retry loop when StreamIdleTimeoutError occurs during tool input generation — covers the same core behavior: stream errors triggering retries that degrade the session without a proper exit condition
• Agent resets to Build after streaming error #12750: Agent resets to Build after streaming error — related streaming error recovery behavior
• Opencode with OpenAI stuck in loop with errors #6983: Opencode with OpenAI stuck in loop with errors — similar loop/retry behavior with OpenAI models

These issues (which you listed as "related issues checked") appear to overlap significantly with the behavior you're describing. Consider whether your report adds new information beyond what's already tracked there, or if a comment/upvote on an existing issue would be more appropriate.

[chindris-mihai-alexandru]

I reviewed #12234, #12750, and #6983.

Why I filed separately:

• This report includes a specific streamed payload from OpenAI on openai/gpt-5.3-codex:
  {"type":"error","sequence_number":2,"error":{"type":"server_error",..."[retrying in 2s attempt #2]"}}
• It is not only StreamIdleTimeoutError (Infinite retry loop when StreamIdleTimeoutError occurs during tool input generation #12234) and not only agent reset behavior (Agent resets to Build after streaming error #12750).
• It is specifically about intermittent provider-side server_error envelopes and how retry/recovery behaves afterward in OpenCode.

If maintainers prefer consolidating under an existing issue, I’m fine closing this as duplicate and moving the payload/evidence there. I can also provide additional timestamped DEBUG logs if helpful.

[chindris-mihai-alexandru]

Additional triage data:

• This is intermittent and not reliably reproducible on demand.
• I do have a captured real payload from session history:
  {"type":"error","sequence_number":2,"error":{"type":"server_error","code":"server_error","message":"... [retrying in 2s attempt #2]"}}
• Captured in exported session ses_3414e160bffeM7NlG2Ae41uXUQ.

Given intermittency, I’m providing concrete payload + session context rather than deterministic repro steps.
If useful, I can attach a redacted DEBUG log bundle with nearby successful/failing runs and timestamps.

[chindris-mihai-alexandru]

Update: I exported and redacted evidence from historical sessions/logs.

Prepared artifacts:

• opencode-error-snippets.txt (captured sequence_number:2 + server_error + retry envelope from exported session)
• opencode-debug-snippets.txt (sanitized timestamp/model/session/error summary lines)
• opencode-session-ses_3414e160bffeM7NlG2Ae41uXUQ.json (redacted session export)

I can attach these if maintainers want the full bundle in this thread.

[chindris-mihai-alexandru]

Superseding my prior note — attaching the redacted evidence inline now.

opencode-error-snippets.txt

session_id: ses_3414e160bffeM7NlG2Ae41uXUQ
session_updated_unix_ms: 1772736548377
captured_payload: {"type":"error","sequence_number":2,"error":{"type":"server_error","code":"serve... (click to expand) [retrying in 2s attempt #2]
captured_payload: {"type":"error","sequence_number":2,"error":{"type":"server_error","code":"server_error","message":"An error occurred while processing your request... [retrying in 2s attempt #2]

opencode-debug-snippets.txt

2026-02-27T174331.log:155 | 2026-02-27T19:16:23 | ERROR | provider=openai | model=gpt-5.3-codex | session=ses_35f782c21ffettEeu5b3nwNqpz | agent=build | error=AI_APICallError
2026-02-27T174331.log:160 | 2026-02-27T19:16:26 | ERROR | provider=openai | model=gpt-5.3-codex | session=ses_35f782c21ffettEeu5b3nwNqpz | agent=build | error=AI_APICallError
2026-02-27T174331.log:165 | 2026-02-27T19:16:31 | ERROR | provider=openai | model=gpt-5.3-codex | session=ses_35f782c21ffettEeu5b3nwNqpz | agent=build | error=AI_APICallError
2026-02-27T174331.log:170 | 2026-02-27T19:16:40 | ERROR | provider=openai | model=gpt-5.3-codex | session=ses_35f782c21ffettEeu5b3nwNqpz | agent=build | error=AI_APICallError
2026-02-27T174331.log:179 | 2026-02-27T19:16:56 | ERROR | provider=openai | model=gpt-5.3-codex | session=ses_35f782c21ffettEeu5b3nwNqpz | agent=build | error=AI_APICallError
2026-02-27T174331.log:184 | 2026-02-27T19:17:29 | ERROR | provider=openai | model=gpt-5.3-codex | session=ses_35f782c21ffettEeu5b3nwNqpz | agent=build | error=AI_APICallError

I also have a fully redacted session export (opencode-session-ses_3414e160bffeM7NlG2Ae41uXUQ.json) ready if needed.

[chindris-mihai-alexandru]

Attached the redacted session JSON as a secret gist:

• https://gist.github.com/chindris-mihai-alexandru/5601ad412254eaee996460156a049105

This is opencode-session-ses_3414e160bffeM7NlG2Ae41uXUQ.json referenced above.