Integrations
Bring the coding agent you already use
25 coding agents and editors have a step-by-step Tokens guide. Each connects with one API key by changing a base URL; 4 of them are set up for you in one command.
Set up in one command
The Tokens CLI signs you in through the browser, creates a key, lets you pick a model and writes the settings for Claude Code, Codex CLI, OpenCode, Crush. It needs Node 18 or newer and keeps a backup of every file it changes.
curl -fsSL https://tokens.bd/cli/tokens.mjs -o tokens.mjs && node tokens.mjs setup --base-url https://tokens.bdiwr https://tokens.bd/cli/tokens.mjs -OutFile tokens.mjs; node tokens.mjs setup --base-url https://tokens.bdEvery guide
Pick your agent for what it needs, which endpoint it uses and the full setup guide.
- Claude CodeConnect Claude Code to Tokens through the Anthropic-compatible endpoint, map the opus, sonnet and haiku aliases to a Tokens model, and fix the usual gateway errors.One-command setupPopularClaude CodeTerminalVS Code
- Codex CLIAdd Tokens as a custom model provider in Codex CLI's config.toml, keep the key in an environment variable, and handle models whose upstream doesn't support the Responses API.One-command setupCodex CLITerminal
- OpenCodeAdd Tokens to OpenCode as an OpenAI-compatible provider in opencode.json, keep the key in TOKENS_API_KEY, set context limits so compaction works, and switch models.One-command setupPopularOpenCodeTerminal
- CrushAdd Tokens to Charm's Crush as an openai-compat provider, using the new crushrc format or the older crush.json the Tokens CLI writes, then pick large and small models.One-command setupCrushTerminal
- OpenClawConnect OpenClaw to Tokens as a custom provider, either with non-interactive onboarding or by editing ~/.openclaw/openclaw.json, then set real context limits and switch models.PopularOpenClawTerminal
- DeepSeek HarnessPoint DeepSeek's open-source agent harness (dsh) at Tokens as a custom OpenAI-compatible provider, keep the key in an environment variable, and run DeepSeek models or the rest of the catalog through the agent loop.NewDeepSeek Harness (dsh CLI / Web UI)
- Hermes AgentPoint Nous Research's Hermes Agent at Tokens as a custom chat completions endpoint, keep the key in ~/.hermes/.env, set a context length of at least 64K, and switch models.NewHermes AgentTerminal
- Connect Cursor to TokensPoint Cursor's chat at the Tokens OpenAI-compatible endpoint with a custom OpenAI base URL, and know which Cursor features will keep using Cursor's own models.PopularCursor
- Connect Cline to TokensSet up the Cline coding agent in VS Code with the OpenAI Compatible provider, the Tokens base URL, your key and a model ID, plus the model settings that matter.PopularCline
- Connect Roo Code to TokensConfigure Roo Code's OpenAI Compatible provider for Tokens. The Roo Code repository was archived in May 2026, so this page also points to maintained alternatives.Roo Code
- Connect Kilo Code to TokensAdd Tokens to Kilo Code as a custom OpenAI Compatible provider, from the settings UI or a kilo.json file, with model limits set so context management works.Kilo Code
- Connect Continue to TokensAdd Tokens models to Continue in VS Code or JetBrains with a config.yaml entry: provider openai, apiBase, key, roles, tool use and context length.Continue
- Connect Zed to TokensUse Tokens models in Zed's Agent Panel through an OpenAI-compatible provider in settings.json, with the API key kept out of the file.Zed
- Connect GitHub Copilot to TokensUse Tokens models in GitHub Copilot Chat in VS Code with the bring-your-own-key Custom Endpoint provider and a chatLanguageModels.json entry.GitHub CopilotVS Code
- AiderRun Aider against Tokens with OPENAI_API_BASE and the openai/ model prefix, silence unknown-model warnings with a metadata file, and switch models per session.AiderTerminal
- GooseAdd Tokens to Goose as a custom OpenAI-compatible provider through goose configure or a JSON file in custom_providers, keep the key in TOKENS_API_KEY, and switch models.GooseTerminalDesktop
- Qwen CodeConnect Qwen Code to Tokens through its OpenAI protocol in ~/.qwen/settings.json or with three environment variables, then switch between Tokens models with /model.Qwen CodeTerminal
- Kimi Code CLIAdd Tokens to Moonshot's Kimi Code CLI as an openai provider in ~/.kimi-code/config.toml, read the key from TOKENS_API_KEY, and map local model aliases to Tokens model ids.Kimi Code CLITerminal
- Connect Factory Droid to TokensAdd Tokens models to Factory's Droid CLI as custom models in ~/.factory/settings.json, using the Chat Completions or Anthropic Messages protocol.Factory Droid
- Connect Warp to TokensPoint Warp's agents at Tokens with a custom inference endpoint that speaks OpenAI Chat Completions, and know where Warp will not use it.Warp
- Connect Amp to TokensRoute models in Amp's own catalog through Tokens with a Model Routing Custom URL connection. Amp cannot add arbitrary model IDs, so read the limits first.Amp
- Connect JetBrains AI Assistant to TokensAdd Tokens as an OpenAI-compatible provider in JetBrains AI Assistant for chat, and optionally for inline completion. Covers the URL field, tool calling and the known path bug.JetBrains AI Assistant
- Connect Xcode to TokensAdd Tokens as an internet-hosted chat provider in Xcode's Intelligence settings. Enter the URL without /v1, add your key and pick models in the chat model picker.Xcode
- GitHub Copilot CLIRun GitHub Copilot CLI on Tokens models with its bring-your-own-key environment variables: base URL, key, model, token limits, and what to check when it fails.GitHub Copilot CLITerminal
- OpenHandsConnect OpenHands to Tokens as an OpenAI-compatible endpoint, in the web UI or the CLI, with the right model string for ids that already contain a slash.OpenHandsTerminal
Your tool is not listed?
Any tool that takes a custom OpenAI- or Anthropic-compatible endpoint works. The compatibility table lists which can and which cannot.