Does Continue need a plugin or a fork?

No. In config.yaml add a model with provider openai, apiBase the router's /v1 and 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?

Chat, edit and autocomplete each routed to the model the task deserves. Budgets and redaction. 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.

Continue through the router

Continue, with the router as the provider.

Continue's config takes an OpenAI-compatible provider with an apiBase; set it to OpenSmartRoute and chat, autocomplete and edits are routed, governed and traced.

Chat, edit and autocomplete each routed to the model the task deserves
Budgets and redaction
A trace per request

Create a free account Continue docs

Continue settingsbash

export OPENAI_BASE_URL=https://api.opensmartroute.ai/v1
export OPENAI_API_KEY=$OSR_API_KEY
# then: In config.yaml add a model with provider openai, apiBase the router's /v1 and model auto.

Continue 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

Continue and the router

Does Continue need a plugin or a fork?: No. In config.yaml add a model with provider openai, apiBase the router's /v1 and 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?: Chat, edit and autocomplete each routed to the model the task deserves. Budgets and redaction. 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 Continue 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.