Skip to main content
Use Connect your coding tools in Planck to choose an available, qualified Claude model, obtain an authorized gateway credential, and generate configuration. A registry entry alone does not establish client compatibility.

​
Terminal

Merge the generated env block into ~/.claude/settings.json (Windows: %USERPROFILE%\.claude\settings.json). It contains ANTHROPIC_BASE_URL, ANTHROPIC_AUTH_TOKEN, approved model mappings, and ANTHROPIC_CUSTOM_HEADERS with the temporary setup identifier. Replace the credential placeholder locally. Do not put the credential in a repository’s .claude/settings.json. The base URL is the gateway origin, without /v1/messages. Planck’s bearer credential uses ANTHROPIC_AUTH_TOKEN. Start Claude Code and use /status to confirm the gateway, credential source, and selected model.

​
VS Code extension

Open Preferences: Open User Settings (JSON). Merge the generated claudeCode.environmentVariables entries, preserving existing settings and unrelated custom headers. Configure the host actually running the extension. Keep credentials out of Settings Sync and repositories. Restart the extension. Terminal exports alone do not configure an editor launched from the Dock or Start menu. For SSH, WSL, and containers, configure the remote execution host.

​
Verify

Start a new conversation and send the prompt shown in Planck. Wait for the matching completed request, then open its request link. A browser gateway test is separate from tool verification. Remove the temporary setup header after success; preserve the gateway, approved models, and credential settings. See official Claude gateway setup.