Skip to content

Free Models Thinking/Reasoning level causing crashes. Nemotron 3 Super Free Limiting. GPT-5 Nano Limiting. #26107

Closed as not planned

Description

@elijahshepherd

Description

Multiple free models in OpenCode v1.14.40 intermittently fail during generation, returning a generic error:

“Provider did not respond”

This behavior appears under specific conditions including long generations, repeated usage, and modified reasoning parameters. The issue is reproducible across multiple free-tier models and impacts stability of responses.


Affected Models

  • Nemotron 3 Super Free (primary and most consistent failure case)
  • GPT-5 Nano (observed after extended usage sessions)
  • Other free-tier models (inconsistent but recurring reports)

Environment

  • OpenCode version: v1.14.40
  • Operating System: Windows 11 Pro (Version 10.0.26200, Build 26200)
  • Terminal: Windows Terminal (Desktop)
  • Plugins: None

Steps to Reproduce

Case 1: Nemotron 3 Super Free (mid-generation failure)

  1. Open OpenCode v1.14.40 on Windows 11

  2. Select Nemotron 3 Super Free

  3. Send a moderately long prompt

  4. Allow full generation to begin

  5. Observe failure mid-response with:

    Provider did not respond

Case 2: Reasoning parameter instability

  1. Select Nemotron 3 Super Free or similar free model

  2. Modify reasoning parameters from default settings (any non-default configuration)

  3. Submit prompt

  4. Observe either:

    • No response
    • Immediate “Provider did not respond” error

Case 3: GPT-5 Nano session degradation

  1. Use GPT-5 Nano continuously for multiple prompts (extended session usage)

  2. After several successful responses (5–15+ interactions)

  3. Submit another prompt

  4. Observe failure:

    Provider did not respond


Expected Behavior

  • Model should consistently return complete responses
  • Reasoning parameter changes should not affect availability or connectivity
  • Long sessions should not degrade into provider failure states

Actual Behavior

  • Intermittent mid-generation termination
  • Immediate request failure when reasoning parameters are modified
  • Session-based degradation leading to temporary loss of model availability

Notes / Observations

  • Error is not tied to a single prompt type; both short and long prompts can fail, but longer outputs increase likelihood.
  • Retry sometimes succeeds immediately, suggesting transient provider instability rather than deterministic crash.
  • Issue appears more frequent on free-tier models compared to paid or stable endpoints.
  • No plugin involvement.

Impact

  • Disrupts reliability of free-tier model usage
  • Breaks long-form generation workflows
  • Reduces usability when experimenting with reasoning settings
  • Causes inconsistent developer experience in OpenCode environment

Activity

  1. added
    needs:complianceThis means the issue will auto-close after 2 hours.
    and removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on May 7, 2026
  2. github-actions commented on May 7, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! The steps to reproduce and environment details look good now. We appreciate you taking the time to improve the report.

  3. elijahshepherd commented on May 7, 2026

    @elijahshepherd
    Author
    Image
  4. github-actions commented on Jul 8, 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

No one assigned

    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