Skip to content

[FEATURE]: Use Responses api for providers that support it #10601

Closed as not planned

Description

@joshrad-dev

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Now that openresponses.org is out and adopted by many providers (including Huggingface, LM Studio, OpenRouter), I think it would be beneficial if these providers used the v1/responses api rather than the chat/completions API. From my testing, it seems as though its as simple as setting the npm field to be @ai-sdk/openai rather than @ai-sdk/openai-compatible and it will default to responses as documented here. Also, might be helpful to change the docs for setting up LM Studio to use the openai provider rather than openai-compatible. Not sure if this is a change that needs to take place here or on the models.dev repo but I thought I'd put it here.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Jan 26, 2026
  2. github-actions commented on Jan 26, 2026

    @github-actions
    Contributor

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

    Issues #9628 and #7793 appear to be the strongest duplicates as they directly address the same feature request and underlying problem.

    Feel free to ignore if this doesn't address your specific case.

  3. openSourcerer9000 commented on Feb 28, 2026

    @openSourcerer9000

    Any update on this? LM studio locally is rough to set up first of all (your LM Studio (local) routes to some unknown API), but it's impossible to use because it doesn't have persistent context.

  4. assigned and unassigned on Apr 26, 2026
  5. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on May 3, 2026
  6. github-actions commented on Jul 6, 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