Skip to main content

All agents

Every agent below runs on Sideren. Each page carries the exact, tested config for that agent — plus the quick check that it works.

Claude Code

Anthropic Messages dialect, four environment variables.

Codex CLI

OpenAI Responses protocol, one provider block in config.toml.

Cursor

OpenAI base-URL override in Cursor’s models settings.

opencode

A Sideren provider in opencode.json.

Crush

An openai-compat provider in Charm’s crush.json.

Goose

Goose via the built-in openai provider.

Hermes Agent

A named provider in ~/.hermes/config.yaml.

OpenClaw

models.providers in ~/.openclaw/openclaw.json.

Qwen Code

Three variables in a .qwen/.env file.

OpenHands

Advanced LLM settings with an openai/-prefixed model.

Aider

~/.aider.conf.yml on the OpenAI-compatible route.

Zed

An openai_compatible provider in settings.json.

Continue

One models entry per catalog id in config.yaml.

Cline

OpenAI Compatible provider in Cline’s GUI.

Kilo Code

Custom provider dialog in the VS Code GUI.

Compatibility at a glance

Every tool here speaks the OpenAI Chat Completions dialect, which the gateway serves at https://api.sideren.io/v1/chat/completions. The only thing that differs between tools is where you set the three values and whether the API base carries the /v1 suffix.
Almost every tool wants the base URL to include /v1 — it appends the method path (/chat/completions) itself. Goose is the one exception on this page: its OPENAI_HOST takes the bare origin and adds /v1/chat/completions for you. Claude Code and Codex have their own pages — Claude Code, Codex CLI, Cursor. Cursor CLI (agent), Antigravity (agy), and Kiro CLI have no OpenAI-compatible hook — npx sideren setup --tool cursor-cli,antigravity,kiro prints that and a Hermes/Codex/Claude one-liner instead of writing a fake config.

Anything OpenAI-compatible

The universal recipe, for tools not listed here:
  • Base URL: https://api.sideren.io/v1 (append /v1 unless the tool documents that it adds it — as Goose and Claude Code do).
  • API key: your Sideren key, usually in the tool’s “OpenAI API key” field. The gateway accepts it as either an Authorization: Bearer or x-api-key header, so whichever the client sends works.
  • Model: any id from the catalog — the tool does not need to know the list in advance. Use the public id (@sdn/glm-5 for an open-weight model, gpt-6.1-sol for a closed-weight one); older spellings such as sdn-glm-5 and glm-5 work too.
The setup helper (npx sideren) automates every setup it can write a file for: Claude Code, Codex, opencode, Hermes, Aider, Continue, Crush, Goose, Qwen Code, OpenClaw, Zed, Kilo Code, Cline and more — see setup helper. Cursor CLI, Antigravity (agy), Kiro and Gemini CLI are recognized --tool ids too; they have no custom OpenAI hook, so setup prints that limit instead of writing a config that would fail. For every tool above, the by-hand config lives on its page.