Does Zed need a plugin or a fork?

No. In settings.json set language_models.openai.api_url to the router's /v1 and list the model auto. The router is a standard endpoint; the tool is unchanged.

Which model does the tool get?

Whatever it asks for. The name auto lets the router choose per turn under your policy; a model id pins it and still routes among its providers; a workspace alias maps the tool's own default name to either.

What does the router add that the tool does not have?

Any provider behind Zed's assistant. A budget per key. A trace per request.

Can I use my own provider keys?

Yes - connect them under Model providers and the router executes on your accounts; model usage is billed by the provider, the platform meters requests.

Zed through the router

Zed's assistant, through the router.

Zed's OpenAI provider takes an api_url; point it at OpenSmartRoute and the assistant panel's calls are routed, priced and traced under your workspace policy.

Any provider behind Zed's assistant
A budget per key
A trace per request

Create a free account Zed docs

Zed settingsbash

export OPENAI_BASE_URL=https://api.opensmartroute.ai/v1
export OPENAI_API_KEY=$OSR_API_KEY
# then: In settings.json set language_models.openai.api_url to the router's /v1 and list the model auto.

Zed speaks the OpenAI API; the router serves chat completions and the Responses API at /v1 with streaming, tools and structured output passed through.

Verify

The first turn is on the activity page.

Send one message from the tool and read the row: the model that answered, the cost, the confidence and a link to the full trace with the alternatives and the policy decisions.

verify.shbash

# the tool's next turn is on the activity page with its cost, model and trace
curl -s https://api.opensmartroute.ai/api/v1/activity?limit=3 -H "Authorization: Bearer $OSR_API_KEY"

Questions

Zed and the router

Does Zed need a plugin or a fork?: No. In settings.json set language_models.openai.api_url to the router's /v1 and list the model auto. The router is a standard endpoint; the tool is unchanged.
Which model does the tool get?: Whatever it asks for. The name auto lets the router choose per turn under your policy; a model id pins it and still routes among its providers; a workspace alias maps the tool's own default name to either.
What does the router add that the tool does not have?: Any provider behind Zed's assistant. A budget per key. A trace per request.
Can I use my own provider keys?: Yes - connect them under Model providers and the router executes on your accounts; model usage is billed by the provider, the platform meters requests.

Other tools

The same router behind every tool the team runs.

Put Zed behind the router today.

A free account, one key, one command. Every turn the tool makes is priced, governed and explained from then on.

Create a free account Migrating application code instead?

Free plan, no card. Fifteen thousand decisions a month with the full trace.