Skip to main content

VS Code and JetBrains IDEs

/ API docs

← API quickstartView as Markdown

OpenCheese works inside your editor through the official Claude Code and Codex integrations. Each one reads the same settings as its command-line tool, so set up the CLI once and the IDE follows.

IDE Integration Settings it reads
VS Code, Cursor and other VS Code forks Claude Code extension ~/.claude/settings.json
VS Code, Cursor and other VS Code forks Codex IDE extension ~/.codex/config.toml
IntelliJ IDEA, PyCharm, WebStorm, GoLand and other JetBrains IDEs Claude Code plugin ~/.claude/settings.json

On Windows, ~ is your user folder, %USERPROFILE%.

Claude Code in VS Code and Cursor

  1. Set up Claude Code: its env block in ~/.claude/settings.json holds ANTHROPIC_BASE_URL and your OpenCheese key.
  2. Install the Claude Code extension from the Extensions view.
  3. Open VS Code settings, search for Claude Code login and check Disable Login Prompt, so the extension uses your settings instead of asking you to sign in to Anthropic. In VS Code's own settings.json that is:
json
{
  "claudeCode.disableLoginPrompt": true
}

The extension and the CLI share the settings file, the conversation history and the model aliases, so /model opus works the same way in both. Keep the variables in the settings file rather than in your shell: VS Code does not always pass the shell's environment to the extension.

Claude Code in JetBrains IDEs

The JetBrains plugin runs the claude command in the IDE's terminal and connects to it, so it uses the CLI's settings unchanged:

  1. Set up Claude Code and check that claude runs in a terminal.
  2. Install the Claude Code plugin from the JetBrains Marketplace and restart the IDE.
  3. Run claude in the IDE's terminal, or run /ide in an external terminal to connect.

If the IDE cannot find claude, set its full path under Settings → Tools → Claude Code.

Codex in VS Code and Cursor

  1. Set up Codex: the opencheese model provider in ~/.codex/config.toml.
  2. Install the Codex extension from the Extensions view.

The extension reads the same config.toml as the CLI, including model and model_provider. If you keep the key in env_key rather than in the file, the variable must be set in the environment VS Code starts from: launch it from a terminal with code ., or use the generated file's experimental_bearer_token.

Other tools

  • OpenCode and Zed have their own guides.
  • Any other extension that lets you set a custom OpenAI-compatible address works with https://api.opencheese.dev/v1 and your API key; one with an Anthropic mode uses https://api.opencheese.dev.

Usage from every IDE appears in the dashboard under Transactions, grouped as one session per conversation.

The cheese has holes. Your infrastructure should not.