Skip to content

IDE extensions

You don’t have to launch Claude Code from the terminal to get routing. The official Claude Code IDE extensions can route through the proxy too - they respect the same ANTHROPIC_BASE_URL setting the CLI uses. Point the extension at your running proxy and every request from the editor is routed and counted on the dashboard.

EditorExtensionNotes
VS Code (and forks: Cursor, Windsurf, Kiro)Claude Code (anthropic.claude-code)First-party. Bundles its own copy of the CLI.
JetBrains - IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, GoLand, Android Studio (and most JetBrains IDEs)Claude Code [Beta]First-party. Requires the notdiamond / claude CLI installed separately.

Any other tool that speaks the Anthropic API and honours ANTHROPIC_BASE_URL will work the same way.

IDE extensions launch Claude Code themselves, so notdiamond claude cannot be used directly. Instead, run the proxy as a background daemon:

Terminal window
notdiamond start # starts the proxy on http://127.0.0.1:8082
notdiamond status # confirm it's up

Run notdiamond init first if you haven’t set up your credentials yet.

Add an env block to the Claude Code settings file at ~/.claude/settings.json (create it if it doesn’t exist). Use the form that matches your proxy credential mode.

For Anthropic API key or Bedrock credentials, set a sentinel auth token:

{
"env": {
"ANTHROPIC_BASE_URL": "http://127.0.0.1:8082",
"ANTHROPIC_AUTH_TOKEN": "notdiamond-proxy"
}
}
  • ANTHROPIC_BASE_URL points the editor at the local proxy. Match the port to your server.port if you changed it in Configuration.
  • ANTHROPIC_AUTH_TOKEN is a sentinel value for API-key-backed proxy modes. Claude Code only routes to a custom base URL when an auth token is present; without it the extension falls back to the Anthropic login screen. The proxy ignores the value - notdiamond-proxy is just a placeholder.

For forwarded credential mode, do not set the sentinel token. Your real credential (from claude /login or an apiKeyHelper) already satisfies the auth-token requirement, and it is intentionally passed to the proxy and forwarded upstream - a sentinel would replace it. The env block should only point at the proxy:

{
"env": {
"ANTHROPIC_BASE_URL": "http://127.0.0.1:8082"
}
}

If your organization manages Claude Code with an apiKeyHelper, leave that configuration in place; Claude Code stamps the refreshed bearer token on requests and the proxy forwards it upstream.

There is no top-level baseUrl key - the base URL always lives inside the env object.

Open the Claude Code panel in your editor and start a session. Requests now flow through the proxy; check notdiamond logs -f or the dashboard to confirm they’re being routed.

  • JetBrains runs your installed CLI directly, so once ~/.claude/settings.json is set it routes reliably. Point the plugin at the binary under Settings → Tools → Claude Code [Beta] → Claude command if it isn’t auto-detected.
  • VS Code bundles its own CLI build. Keep the extension up to date - some 2.0.x releases shipped a regression that ignored ANTHROPIC_BASE_URL. If the editor shows the Anthropic login screen instead of routing, see Troubleshooting below.

The editor shows the Anthropic login screen instead of routing.

  1. Confirm the env block is in ~/.claude/settings.json (not VS Code’s own settings.json). API-key-backed proxy modes need both ANTHROPIC_BASE_URL and the sentinel ANTHROPIC_AUTH_TOKEN; forwarded credential mode should only set ANTHROPIC_BASE_URL and must not use the notdiamond-proxy placeholder.
  2. Update the Claude Code extension to the latest version.
  3. Launch the editor from a terminal (code .) rather than the Dock/Finder - GUI launches don’t always inherit the right environment.
  4. Confirm the proxy is up with notdiamond status.