Claude Code workspace

Use the official Claude Code distribution for your operating system, then check claude --version. This recipe concerns endpoint configuration, not installation or bypassing a client's own access controls.

Per-user settings

Merge the following env entries into ~/.claude/settings.json on Linux/macOS, or %USERPROFILE%\.claude\settings.json on Windows. Keep unrelated existing settings.

{"env":{"ANTHROPIC_BASE_URL":"https://api.b2b-llm.com","ANTHROPIC_AUTH_TOKEN":"mg_live_...","ANTHROPIC_MODEL":"claude-sonnet-4.6","ANTHROPIC_SMALL_FAST_MODEL":"claude-haiku-4.5"}}

The origin has no /v1. The sample names must be replaced if your catalog uses different enabled models or aliases. Use a separate low-cost utility model only when it supports the client's utility tasks.

Check the process environment

Close and reopen the terminal/client after editing configuration. A shell environment can override saved settings, so inspect both when requests still go to an unexpected destination. Do not print the full token into a troubleshooting log.

Start with a small task in an approved working directory. Keep tool approvals appropriate to that environment. Agent activity can produce multiple billable model turns from one instruction; apply project/key budgets before broad team rollout.

A shared project key available in the web Playground is not automatically a reusable secret available to a workstation. Have an authorized administrator issue an application credential for a persistent CLI integration.

Claude Desktop

For the desktop application, use the separate Claude Desktop gateway setup. Claude Code configuration is not its desktop configuration.