Zed Editor

Zed is a high-performance editor with built-in AI assistant support. It can connect to any OpenAI-compatible API, making Vikat a natural fit for universal model access across providers, plus governance features like virtual keys and built-in observability.

If your Allowed Headers are already set to *, you can skip this note. If not and you face issues integrating Vikat with Zed, try switching to * or adding the specific headers required by your client. By default, Vikat whitelists: Content-Type, Authorization, X-Requested-With, X-Stainless-Timeout, and X-Api-Key.

Setup

1. Configure Vikat Provider

Add Vikat to Zed’s language_models.openai_compatible configuration. This is typically in your Zed settings (JSON) or workspace config.

"language_models": {
  "openai_compatible": {
    "Vikat": {
      "api_url": "http://localhost:8080/openai",
      "available_models": [
        {
          "name": "anthropic/claude-sonnet-4.5",
          "max_tokens": 200000,
          "max_output_tokens": 4096,
          "capabilities": {
            "tools": true,
            "images": true,
            "parallel_tool_calls": true,
            "prompt_cache_key": false
          }
        },
        {
          "name": "openai/gpt-4o",
          "max_tokens": 128000,
          "max_output_tokens": 4096,
          "capabilities": {
            "tools": true,
            "images": true,
            "parallel_tool_calls": true,
            "prompt_cache_key": false
          }
        },
        {
          "name": "openai/gpt-5",
          "max_tokens": 256000,
          "max_output_tokens": 4096,
          "capabilities": {
            "tools": true,
            "images": true,
            "parallel_tool_calls": true,
            "prompt_cache_key": false
          }
        }
      ]
    }
  }
}

Replace http://localhost:8080/openai with your Vikat gateway URL + /openai.

2. Model Capabilities

Field	Description
`tools`	Enable tool/function calling
`images`	Enable image input (vision)
`parallel_tool_calls`	Support multiple tool calls in one response
`prompt_cache_key`	Enable prompt caching (set `false` if not supported)

Use Vikat model IDs in provider/model format (e.g. openai/gpt-5, anthropic/claude-sonnet-4.5). Ensure these models are configured in Vikat.

3. Reload Workspace

After changing the configuration, reload the workspace so Zed recognizes and reloads the provider list.

Virtual Keys

When Vikat has virtual key authentication enabled, add an api_key field to the Vikat provider config (check Zed’s documentation for the exact field name - it may vary by version):

"Vikat": {
  "api_url": "http://localhost:8080/openai",
  "api_key": "bf-your-virtual-key-here",
  "available_models": [...]
}

This lets you enforce usage limits, budgets, and access control per user or team. For team deployments, create a separate virtual key for each team or environment - each key can have its own rate limits, budgets, and provider access rules configured in the Vikat dashboard.

Model Selection

Zed lets you assign models to different AI features. Use Vikat model IDs in provider/model format to access any configured provider:

Use powerful models like openai/gpt-5 or anthropic/claude-sonnet-4-5-20250929 for complex code generation and refactoring
Use fast models like groq/llama-3.3-70b-versatile for quick completions and inline suggestions

Using Multiple Providers

Vikat routes requests to the correct provider based on the model name. Use the provider/model-name format to access any configured provider through the single OpenAI-compatible endpoint:

anthropic/claude-sonnet-4-5-20250929
openai/gpt-5
gemini/gemini-2.5-pro
mistral/mistral-large-latest

Supported Providers

Vikat supports the following providers with the provider/model-name format: openai, azure, gemini, vertex, bedrock, mistral, groq, cerebras, deepseek, cohere, perplexity, xai, ollama, openrouter, huggingface, nebius, parasail, replicate, vllm, sgl

Non-native models must support tool use for Zed’s AI features (code actions, refactoring) to work properly. Models without tool use support will only work for basic chat and completions.

Zed connects to Vikat via a single OpenAI-compatible endpoint. Vikat handles routing to the correct provider based on the model name - no per-provider configuration needed.

Observability

All Zed requests through Vikat are logged. Monitor them at http://localhost:8080/logs - filter by provider, model, or search through conversation content to track usage.

Next Steps

Provider Configuration - Configure AI providers in Vikat
Virtual Keys - Set up usage limits and access control

CLI Agents & Editors

SDKs & Frameworks

Identity Providers (SSO)

Content Safety (Guardrails)

Observability

Vector Databases

Setup

1. Configure Vikat Provider

2. Model Capabilities

3. Reload Workspace

Virtual Keys

Model Selection

Using Multiple Providers

Supported Providers

Observability

Next Steps

​Setup

​1. Configure Vikat Provider

​2. Model Capabilities

​3. Reload Workspace

​Virtual Keys

​Model Selection

​Using Multiple Providers

​Supported Providers

​Observability

​Next Steps

Setup

1. Configure Vikat Provider

2. Model Capabilities

3. Reload Workspace

Virtual Keys

Model Selection

Using Multiple Providers

Supported Providers

Observability

Next Steps