Desktop and IDE extensions
Configuration boundaries between Claude Desktop, Code surfaces, Passion8 gateway routing, and MCP tool bridging.
“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. For detailed workflows, see Desktop, Web, and 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.
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:
{
"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:
{
"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:
echo $ANTHROPIC_BASE_URL
claude doctorThe 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:
claude mcp serveAdd it to Desktop MCP configuration:
{
"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
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
#Continue reading
Support
Need help?
For setup, billing, or model issues, email us. Check the status page for uptime.
WeChat / QQ support is available at the bottom right.

