Skip to content

[ISSUE]: I send a message and it not responds #25793

Closed as not planned
Closed as not planned

Description

@EduardoCortezB

Description

I just sent a message and OC doesnt respond Codex 5.3

Plugins

Default

OpenCode version

1.14.34

Steps to reproduce

Just send a message usong Codex 5.3

Screenshot and/or share link

No response

Operating System

Windows11

Terminal

WSL

Activity

  1. github-actions commented on May 5, 2026

    @github-actions
    Contributor

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

    If your issue is different from the above, please add more detail about what you observe (any error messages, logs, or screenshots) to help distinguish it.

  2. VitalyM commented on Jun 13, 2026

    @VitalyM

    Workaround: empty/no response with Azure gpt-5.3-codex via the Responses API

    If opencode (or any client) hangs/returns nothing with gpt-5.3-codex on Azure while simple curl calls work, it's an Azure-side issue with one specific parameter combination:

    reasoning.effort = "medium" + function tools in the request → the model fails with:

    {"error":{"code":"unknown","message":"The model was unable to complete inference due to an internal error."}}

    (HTTP 503 for non-streaming; a response.failed event for streaming, which clients often swallow silently → you see no output.)

    I verified it deterministically by replaying the exact request body and only varying the effort:

    reasoning effort with tools
    low ✅ works
    medium ❌ fails (503 / "unable to complete inference")
    high ✅ works

    Removing the tools, or removing the reasoning block, also makes medium work — so the trigger is specifically medium effort + tools. The default for the build/coding agent is medium, which is why it fails every time while title generation (no tools) succeeds.

    Fix

    Force the reasoning effort to low or high for this model. In opencode config:

    "models": {
      "gpt-5.3-codex": {
        "name": "gpt-5.3-codex",
        "options": { "reasoningEffort": "high" }   // "low" also works; just not "medium"
      }
    }

    Note: "minimal" returns HTTP 400 on this deployment — use low or high.

    This looks like an Azure deployment-side regression (a client downgrade made no difference), so it may resolve itself server-side, but the config override is a reliable workaround in the meantime.

  3. TimChinye commented on Jun 24, 2026

    @TimChinye

    This is likely unrelated to #32606 and #32149 as the issue occurs regardless of when model is being used.

  4. github-actions commented on Aug 24, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions