AI Editors

Zed

Add a compatible language-model provider and store its key through the credential UI.

ConfigurableOpenAI Chat CompletionsDocs checked 2026-09-18

The vendor documents custom endpoints. Check model capabilities and verify the connection.

On this page

Before you begin

Install the package for your OS and use a version with openai_compatible settings. Do not assume a chat model supports edit prediction.

Have an A2Agent API key ready and copy an accessible model ID from the catalog. Replace every placeholder, back up existing settings and keep keys out of repositories.

Manage API keys Browse models

Setup

File contents are usually shared; switching OS changes commands and paths. For WSL on Windows, select macOS / Linux.

01Open user settings
After installing Zed, run zed: open settings file from the command palette.
Open official documentation

02Merge provider configuration

Merge language_models into user settings. max_tokens is an example context budget; adjust it to the model’s capabilities.

json

{
  "language_models": {
    "openai_compatible": {
      "a2agent": {
        "api_url": "https://a2agent.me/v1",
        "available_models": [{
          "name": "YOUR_MODEL_ID",
          "display_name": "A2Agent",
          "max_tokens": 32768
        }]
      }
    }
  }
}

03Add the key and select the model
Find a2agent in Agent provider configuration, enter your A2Agent key, and select the model. Keep the key out of settings.json.

Capabilities and limits

Agent chat and Edit Prediction have separate configurations.
Tool, image and reasoning capabilities must match the model. Defaults do not establish gateway support.

Verify the connection

Replace every placeholder and run locally. Expect JSON containing OK. Then start a new client conversation, test one read-only tool call separately, and confirm the requests in A2Agent usage records. This test incurs a small amount of model usage.

Shell

curl --fail-with-body --silent --show-error --max-time 60 'https://a2agent.me/v1/chat/completions' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_A2AGENT_API_KEY' \
  -d '{"model":"YOUR_MODEL_ID","max_tokens":128,"messages":[{"role":"user","content":"Reply with OK."}]}'

Troubleshooting

For an empty list, check openai_compatible nesting and the model name. For authentication errors, re-enter the key in the provider UI.

401 / 403: authentication or access denied

Use a key issued by A2Agent, without extra spaces, and check that it is active and unexpired. Confirm the group permits the model and protocol. A vendor subscription credential cannot replace an A2Agent key.

404 / model not found: endpoint or model mismatch

Check the root URL, /v1 prefix and full request path against this guide; avoid duplicated paths. Model IDs are case-sensitive and must be accessible to the current key.

429: quota or rate limit

Check your balance, key limits, concurrent usage and service status. Wait before retrying and reduce simultaneous agents; repeated retries do not remove a quota limit.

Chat works, but tools fail or streaming stops

Test a short text request, then a single read-file tool call. Check tool support, output budget, proxy timeouts and client version. Inspect the diff before resuming a long task to avoid repeating actions.

Restore previous settings

Select the previous model, remove language_models.openai_compatible.a2agent, and remove its credential in the provider UI.

Sources and check date

Status is based on official configuration docs, not end-to-end client testing with A2Agent.

Docs checked 2026-09-18