Skip to main content
Use this guide to add Phaseo as the model provider in coding assistants that support custom OpenAI-compatible or Anthropic-compatible endpoints.

Set up with the Phaseo CLI

Sign in once, then install and configure one of the primary harnesses:
This command installs the harness when it is missing, creates its dedicated key, and writes its Phaseo configuration. OpenCode, DeepSeek Harness, Pi, and Prime Agent also receive every active text model compatible with Chat Completions. Use --skip-install, --catalog default, or --dry-run when you need narrower behavior. Use the lower-level command for other integrations or when installation is managed separately:
Supported integration names are codex, claude-code, opencode, deepseek-harness, pi, openclaw, hermes, aider, cline, roo-code, kilo-code, continue, cursor, and zed. The CLI creates a separate, non-expiring API key named for that assistant. It configures Aider and Continue automatically on clean installations, and writes Zed’s provider/model settings automatically. For assistants that keep secrets exclusively in an editor UI, it prints the exact remaining fields, links the dedicated guide, and lets you copy only that assistant’s key:
Preview any file changes before setup, and disconnect cleanly later:
Removal deletes Phaseo-owned configuration and revokes that assistant’s key. It does not remove unrelated settings.

Provider settings

Use these values unless the tool asks for a different field name: For Anthropic-compatible tools, use:

Cursor

Cursor supports custom OpenAI-compatible endpoints through its OpenAI API key settings.
  1. Open Cursor Settings.
  2. Go to Models.
  3. Enable or add the OpenAI API Key entry.
  4. Paste your Phaseo API key.
  5. Enable Override OpenAI Base URL.
  6. Set the base URL to https://api.phaseo.app/v1.
  7. Add a custom model using A Phaseo model id, for example openai/gpt-5-nano.
  8. Enable the model and verify it from the Cursor model picker.
If Cursor rejects a model id with /, create the closest local alias the UI allows and route that alias to the Phaseo model in your own config when the client supports aliases.

VS Code

VS Code supports adding models through the Language Models editor when the OpenAI-compatible provider is available in your VS Code or Insiders build.
  1. Open the Command Palette.
  2. Run Chat: Manage Language Models.
  3. Choose OpenAI Compatible or OAI Compatible.
  4. Enter your Phaseo API key.
  5. Set the endpoint or base URL to https://api.phaseo.app/v1.
  6. Add A Phaseo model id, for example openai/gpt-5-nano.
  7. Select the new model from the chat model picker.
If your VS Code build does not show an OpenAI-compatible provider, use an extension that supports custom providers, such as Continue, Cline, Roo Code, or Kilo Code.

Continue

Continue can use Phaseo through its OpenAI provider with a custom API base.
For models where Continue defaults to Responses but your workflow needs Chat Completions compatibility, set useResponsesApi: false.

Cline, Roo Code, and Kilo Code

These tools expose similar provider settings.
  1. Open the extension settings.
  2. Choose OpenAI Compatible as the provider.
  3. Set the base URL to https://api.phaseo.app/v1.
  4. Paste your Phaseo API key.
  5. Enter A Phaseo model id.
  6. Save and run a small chat request before using file-editing tools.

Aider

Set OpenAI-compatible environment variables and pass the model on launch:
Aider often expects OpenAI-compatible custom models to be prefixed with openai/. Because Phaseo model ids already include provider prefixes, the full Aider model string may look like openai/openai/gpt-5-nano.

Pi, Prime Agent, OpenClaw, and Hermes Agent

phaseo pi installs Pi and a dedicated provider extension that resolves its key from the Phaseo CLI at runtime. phaseo prime-agent installs Prime Agent on macOS or Linux and writes a command-backed provider to ~/.prime/agent/models.json. Both receive the compatible Phaseo model catalog. phaseo openclaw installs OpenClaw and registers the compatible model catalog plus an exec-backed SecretRef, without placing the API key in openclaw.json. phaseo hermes installs and configures the current Nous Research agent. It saves the previous Hermes model settings, configures Phaseo as the custom endpoint, and uses Hermes’ official hermes config set command to place the dedicated key in ~/.hermes/.env as OPENAI_API_KEY. Hermes deliberately uses this plaintext file for provider credentials; protect it like any other API-key file. Removal restores the previous model settings, removes OPENAI_API_KEY, deletes Phaseo’s recovery state, and revokes the key.

Zed

Run phaseo integrations setup zed, then follow the printed steps to add an OpenAI-compatible provider in Zed’s settings. Use the generated key only in Zed’s credential prompt.

Codex

Use the dedicated Codex guide for Codex CLI, Codex App, and the Codex IDE extension. The short version is:
Codex custom providers use the Responses wire protocol.

OpenCode

Use the dedicated OpenCode guide when you want OpenCode to call Phaseo through an OpenAI-compatible custom provider.

Claude Code

Use the dedicated Claude Code guide. Claude Code uses Anthropic-compatible gateway environment variables:
Then start Claude Code from the same shell:

Claude Desktop

Claude Desktop supports MCP servers, but it does not expose the same custom model-provider setup as coding assistants such as Cursor, Codex, or Claude Code. Use Docs MCP to add Phaseo documentation context to Claude Desktop. Use Claude Code when you need Phaseo to be the model gateway.

Deep Agents CLI and LangChain tools

Use the same base URL and API key settings as LangChain. If the tool reads OpenAI environment variables, set:
Then pass A Phaseo model id in the tool’s model field.

Notes

  • Coding assistants vary in how they handle slashes in model ids. If the UI rejects openai/gpt-5-nano, create a local alias if the tool supports aliases.
  • Test file-editing workflows carefully. phaseo:apply_patch is Responses-only.
  • Add Docs MCP when you want the assistant to read Phaseo docs during a session.
  • Prefer Chat Completions for older coding tools unless the tool explicitly supports Responses events and server tools.
Last modified on August 14, 2026