Skip to content

Hidden calls Haiku #10272

Closed
Closed

Description

@jnarvaezp

Description

While using OpenCode with OpenRouter, I explicitly configured the model to MiniMax M2.1. However, the usage logs clearly show that multiple requests are being executed and billed against Claude Haiku 4.5, even though that model was never selected.

This behavior occurs silently, without any warning, visible configuration, or explicit fallback setting enabled.

Evidence

App: OpenCode
Expected model: MiniMax M2.1
Actual models used: MiniMax M2.1
Claude Haiku 4.5 (unexpected)
Billing impact: Tokens are consumed and charged for Claude Haiku 4.5
Finish types observed:
stop
tool_calls

Thank you very much for your help and guidance.
I appreciate any clarification on whether this behavior is normal or related to a missing configuration on my side.

Plugins

No response

OpenCode version

1.1.34

Steps to reproduce

No response

Screenshot and/or share link

Image

Operating System

linux ubuntu 24.04

Terminal

Ghossty

Activity

  1. github-actions commented on Jan 23, 2026

    @github-actions
    Contributor

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

    All these issues point to a potential underlying bug where Claude Haiku is being called as an unexpected fallback or default when other models are explicitly selected, particularly with OpenRouter provider.

    Feel free to ignore if your specific case differs from these.

  2. justfortheloveof commented on Jan 23, 2026

    @justfortheloveof
    Contributor
  3. adam-ah commented on Jan 25, 2026

    @adam-ah

    @justfortheloveof , a workaround Isn't a solution

    There has been multiple reports of this bug.

    The fundamental problem is that OpenCode makes assumptions about what users want to do, defaulting to models for background tasks without explicit user consent or clear UI indication.

    See also #4579

  4. justfortheloveof commented on Jan 25, 2026

    @justfortheloveof
    Contributor

    @justfortheloveof , a workaround Isn't a solution

    I'm not implying you're wrong nor that config is the solution, but rather pointing it out for awareness as it can be useful for those who aren't aware, while there is no released solution (I actually dislike the AI titles and have disabled them completely).

    I do agree that it's a problem that opencode can silently use paid models without user consent.

  5. rekram1-node commented on Jan 25, 2026

    @rekram1-node
    Collaborator

    yeah this comes from the title generation requests, it should use cheapest models instead

  6. adam-ah commented on Jan 25, 2026

    @adam-ah

    Thanks for acknowledging this @rekram1-node. The core issue is OpenCode making assumptions without user consent.

    Instead of making further assumptions and defaulting to any model (even cheap ones), title summaries should be an optional feature with explicit configuration:

    • Optional checkbox for "Enable AI-generated titles"
    • Separate model selector if enabled (suggest cost-effective defaults)
    • Transparent UI showing what's being used

    This respects user choice, prevents billing surprises, and allows customization. Would you be open to a PR implementing this approach?

  7. TheHamkerCat commented on Jan 31, 2026

    @TheHamkerCat

    Every time you send a message in OpenCode, this feature sends your message to Anthropic (correct me if I'm wrong, i just checked in httpproxy and this is the case),

    This is pretty bad for privacy for some people, if they don't want to keylog their data to anthropic (everyone had different choices), Not to mention the cost

    OC should disable this by default

  8. github-actions commented on Apr 1, 2026

    @github-actions
    Contributor

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

  9. HassanJbara commented on Jul 2, 2026

    @HassanJbara

    WHAT ??? DO NOT CLOSE THIS ISSUE

  10. marcoczen commented on Aug 11, 2026

    @marcoczen

    So no solution ? We are screwed ?

  11. ashesfall commented on Oct 27, 2026

    @ashesfall

    This is extremely bad

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions