Viro API

Integrations / Cursor

Cursor

Cursor has a built-in OpenAI base URL override, so it can call Viro directly — no extension, no proxy.

Status: unverified. Chat and completions work. We have not run a live Agent-mode session against Viro, so treat that as untested.
Configure
  1. Open Settings → Models.
  2. Under the OpenAI API Key section, toggle Override OpenAI Base URL on.
  3. Set the base URL to https://api.viro.app/v1 and paste your Viro API key (from API Keys) into the API Key field.
  4. Add the model slugs you want under Model Names — e.g. viro/optimized, viro/frontier, anthropic/claude-sonnet-5.
  5. Select one from the model dropdown in the chat panel.

Cursor sends a probe request through the same auth header when you save — a green check means your key and base URL are both accepted.

Picking a model for Agent mode

Agent mode leans on reliable, multi-step tool calling more than chat does. Start with viro/frontier or a specific frontier model (anthropic/claude-sonnet-5, openai/gpt-5.6-terra) while you evaluate — those plus viro/kimi-k2.5 and viro/qwen3-235b-instruct are the models verified for sustained tool-call sequences elsewhere in these docs — see Server tools. viro/optimized is worth trying once you have a reliability baseline, since it costs less on average.

Limitations

Tab completion doesn't route through Viro. Cursor's inline autocomplete always uses Cursor's own model regardless of provider settings — this is true for every custom provider, not specific to Viro. Only chat and Agent mode use the model you configure here.

Some Cursor-exclusive features are gated to specific first-party models and won't be available through a custom provider.

An organization can lock the base URL override in admin settings, which would block this setup for managed Cursor installs.