Support Nebius Token Factory Model Provider

[shivaylamba]

Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

Similar to #9303

I would like to propose a solution for Warp to support Nebius Token Factory AI models which provided an OpenAI compatible API end point and very cheap pricing for various OSS LLM models.

I have already implemented it in local and it should look like this

Is your feature request related to a problem? Please describe.

Currently there is only supported for a limited LLM providers. There should be a way to provide an OpenAI compatible API endpoint to be add self hosted LLMs

Additional context

No response

Operating system (OS)

macOS

How important is this feature to you?

5 (Can't work without it!)

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

Ignore

[oz-for-oss]

@shivaylamba

You can view the triage session on Warp.

Here's what I found while triaging this issue:

This looks closely related to #9303: supporting custom OpenAI-compatible provider endpoints would likely cover Nebius Token Factory. I verified Nebius exposes an OpenAI-compatible API, so this is a concrete provider/use case for that broader request.

Maintainer details

I concluded that feature request to support Nebius Token Factory, likely as a concrete OpenAI-compatible custom provider endpoint for Warp AI models..

Initial triage

This is an enhancement request to support Nebius Token Factory models in Warp, either as a Nebius-specific model provider or as part of a broader custom OpenAI-compatible endpoint feature. The report is clear and includes a screenshot of the reporter's local implementation.

Evidence

• The issue is explicitly framed as similar to Custom OpenAI-Compatible Provider Endpoints (BYO Endpoint for Local & Remote LLMs) #9303, which requests custom OpenAI-compatible provider endpoints.
• Nebius Token Factory documentation describes an OpenAI-compatible API with https://api.tokenfactory.nebius.com/v1/, /v1/chat/completions, /v1/models, and bearer-token authentication.
• Current client code models known providers with a fixed provider enum and pulls available model choices from Warp's GraphQL-backed feature model catalog.
• The inspected BYOK settings UI exposes provider API key fields for existing known providers, but not a base URL/model-id configuration for arbitrary OpenAI-compatible endpoints.

Likely implementation area

This likely crosses the AI model/provider catalog, BYOK credential storage, AI settings UI, and execution profile model picker. A Nebius-specific integration could be added through the existing provider/model catalog flow, while the broader product direction in #9303 would require a generic custom OpenAI-compatible endpoint configuration path.

Duplicate check

#9303 is a strong related/canonical broader request, but the duplicate workflow requires at least two likely duplicate candidates before marking this issue as a duplicate. I did not find a second matching issue in the provided recent/open issue list, so this is not labeled as a duplicate in this pass.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[shivaylamba]

The current Nebius support is a local OpenAI-compatible chat adapter, not a full Warp model backend.

Main limitations:

It can answer text in Agent, but it cannot call Warp tools yet.
It does not run the full terminal automation loop: command execution, file edits, structured
tool calls, approvals, etc.
Need to get to support the full agentic terminal loop next -

Do you know if OpenAI-compatible endpoints would automatically get support for the full agentic experience or do we need make it manually?