# Claude Code Desktop and IDE extensions

> Configuration boundaries between Claude Desktop, Code surfaces, Passion8 gateway routing, and MCP tool bridging.

URL: https://docs.passion8.cc/en/docs/claude-code/desktop
Language: en
Publisher: Passion8

“Claude Desktop” can refer to different surfaces. Identify the application before configuring it.

For CLI, IDE, Desktop, Web, Slack, CI, and review comparisons, see [Platforms and integrations](https://docs.passion8.cc/en/docs/claude-code/platforms-integrations). For detailed workflows, see [Desktop, Web, and IDE](https://docs.passion8.cc/en/docs/claude-code/desktop-web-ide).




Do not configure consumer Claude Desktop as though it were the CLI. ANTHROPIC_BASE_URL and ~/.claude/settings.json configure Claude Code; they do not automatically route ordinary Desktop chat through Passion8.




## Choose the correct surface

| Surface | Passion8 suitability | Use |
| --- | --- | --- |
| Claude Code CLI | Recommended | Terminal development, scripts, long repository tasks |
| Claude Code IDE/VS Code | Recommended | Editor-based development |
| Code in Desktop | Depends on organization configuration | Graphical session management |
| Desktop MCP bridge | Optional tool bridge, not gateway routing | Call local Code tools from Desktop |
| Consumer Desktop chat | Not the default Passion8 connection method | General chat |

## Recommended: Claude Code CLI

The CLI has the clearest gateway configuration and diagnostics.

```bash
export ANTHROPIC_BASE_URL="https://passion8.cc"
export ANTHROPIC_AUTH_TOKEN="sk-YOUR_PASSION8_API_KEY"
claude -p "Describe the current directory in one sentence"
```

For persistent use:

```json title="~/.claude/settings.json"
{
  "env": {
    "ANTHROPIC_BASE_URL": "https://passion8.cc",
    "ANTHROPIC_AUTH_TOKEN": "sk-YOUR_PASSION8_API_KEY"
  }
}
```




Share team rules in project settings, but keep personal keys in user settings or local environment variables.




## VS Code and IDE extensions

An IDE may not inherit your shell environment. Configure the extension in its user settings:

```json title="VS Code settings.json"
{
  "claudeCode.environmentVariables": [
    { "name": "ANTHROPIC_BASE_URL", "value": "https://passion8.cc" },
    { "name": "ANTHROPIC_AUTH_TOKEN", "value": "sk-YOUR_PASSION8_API_KEY" }
  ]
}
```

If the IDE exposes a Claude Code terminal, check:

```bash
echo $ANTHROPIC_BASE_URL
claude doctor
```

The endpoint should be https://passion8.cc. Do not print the token.

## Code in Desktop

The official Desktop gateway route is configured through supported organization/administrator distribution, not merely by exporting a terminal variable.

- For personal Passion8 access, start with CLI or IDE.
- For team-managed Desktop, follow the administrator's gateway setup.
- If uncertain about Desktop routing, first establish a working CLI request.




A functioning official Desktop account does not prove Passion8 routing. Verify the configured gateway and the corresponding Passion8 usage records.




## Consumer Claude Desktop

Consumer Desktop is an account client, not a generic third-party Anthropic-compatible client. Connecting MCP tools does not replace its model backend.

For Passion8 model requests, use CLI/IDE or a separately supported Desktop gateway configuration. For local tool access from Desktop chat, use the bridge below.

## Desktop MCP bridge

This exposes local Claude Code tools to Desktop; it does not reroute Desktop's own model requests.

Confirm the stdio server starts:

```bash
claude mcp serve
```

Add it to Desktop MCP configuration:

```json title="claude_desktop_config.json"
{
  "mcpServers": {
    "claude-code": {
      "command": "claude",
      "args": ["mcp", "serve"],
      "env": {
        "ANTHROPIC_BASE_URL": "https://passion8.cc",
        "ANTHROPIC_AUTH_TOKEN": "sk-YOUR_PASSION8_API_KEY"
      }
    }
  }
}
```

Restart Desktop and confirm claude-code is connected in its tool list.




These environment values affect only the spawned MCP process. Desktop's own generation route depends on its separate gateway configuration.




## Troubleshooting order







### Test the CLI first

```bash
claude -p "ping"
```

If it fails, see [Installation](https://docs.passion8.cc/en/docs/claude-code/install) and [Troubleshooting](https://docs.passion8.cc/en/docs/claude-code/troubleshooting).





### Then test the IDE

Check claudeCode.environmentVariables and restart the editor if needed.





### Finally test Desktop

Confirm actual gateway configuration and Passion8 usage rather than inferring routing from a successful chat.






## Official references

- [Desktop application](https://code.claude.com/en/docs/en/desktop.md)
- [Desktop quickstart](https://code.claude.com/en/docs/en/desktop-quickstart.md)
- [VS Code](https://code.claude.com/en/docs/en/vs-code.md)

## Continue reading



- [Installation and configuration](https://docs.passion8.cc/en/docs/claude-code/install): Standard CLI setup for Passion8.
- [Platforms and integrations](https://docs.passion8.cc/en/docs/claude-code/platforms-integrations): Compare runtime locations and provider boundaries.
- [Cost and caching](https://docs.passion8.cc/en/docs/claude-code/cost-saving): Reduce repeated tokens and keep workflows stable.