Claude Code

Platforms and integrations

CLI, IDE, desktop, web, mobile, Chrome, Slack, CI, review, Ultraplan and Ultrareview boundaries with Passion8.

Determine where requests originate and where code/tools execute before choosing an integration. This is more reliable than the UI's name.

See desktop, web and IDE workflows for desktop setup, Linux beta, scheduling, web, remote access, IDEs and Slack.

Passion8 primarily supports local CLI/IDE and automation that explicitly sets the endpoint. Hosted web, Slack, review and Ultrareview rely on official accounts/cloud environments and do not inherit your local token.

#Execution surfaces

Surface	Execution location	Request configuration	Passion8 guidance
CLI	Local shell	Environment/settings	Preferred
VS Code	IDE Code process	Extension environment/settings	Verify inherited environment
JetBrains	IDE Code process	Client/plugin settings	Test remote/WSL separately
Desktop Code	Desktop-managed local/organizational environment	Desktop/policy dependent	Prefer CLI for personal gateway setup
Web	Hosted sandbox	Cloud connectors/secrets	No local-variable inheritance
Remote Control	Local session controlled remotely	Local configuration	Custom URL can affect pairing
Slack	Hosted session	Official Slack/GitHub	Usually not a gateway entry point
CI	Runner	Job secrets/configuration	Explicitly inject gateway variables
Review/Ultrareview	Official cloud	Account, GitHub app and cap	Official billing/limits

#VS Code and JetBrains

IDE entry points directly reference files, diffs, terminal output and editor state.

Feature	VS Code	JetBrains
File/directory references	@ mentions	Plugin context and IDE selection
Multiple sessions	Conversations/tabs	IDE or external terminal launches
Git	Commit/PR/worktree assistance	IDE integration and CLI
Chrome automation	Dedicated documented entry	Usually CLI/browser tools
Remote development	Check extension location in container/SSH/WSL	Check binary location remotely

A reliable VS Code setup uses extension environment variables:

VS Code settings.json

{
  "claudeCode.environmentVariables": [
    { "name": "ANTHROPIC_BASE_URL", "value": "https://passion8.cc" },
    { "name": "ANTHROPIC_AUTH_TOKEN", "value": "sk-YOUR_PASSION8_API_KEY" }
  ]
}

In JetBrains, verify that the IDE can locate claude:

which claude
claude doctor

Remote/WSL IDE environments may have different PATH, Node, certificates and variables. See installation troubleshooting and configuration debugging.

#GitHub Actions and GitLab CI

CI can create PRs, fix tests, handle issues and review. Store endpoint and key in CI secrets rather than relying on developer-machine settings.

.github/workflows/claude.yml

env:
  ANTHROPIC_BASE_URL: https://passion8.cc
  ANTHROPIC_AUTH_TOKEN: ${{ secrets.PASSION8_API_KEY }}

.gitlab-ci.yml

variables:
  ANTHROPIC_BASE_URL: "https://passion8.cc"
  ANTHROPIC_AUTH_TOKEN: "$PASSION8_API_KEY"

Recommendations:

Area	Recommendation
Permissions	Minimal tokens and repository/branch access
Context	Issue, diff and failure logs rather than entire repository prompts
Cache	Stable model/effort within the job
Concurrency	Avoid simultaneous duplicate huge contexts
Logs	No keys, customer data or complete production logs

Official mention-triggered integrations have their own app permissions and security. Start with explicit headless workflows for predictable gateway configuration.

#Slack, mobile and cloud work

These surfaces suit remote delegation and progress tracking, generally through official accounts and hosted sessions.

Scenario	Surface	Gateway boundary
Continue local work on phone	Remote Control	Local requests; official pairing may be required
Delegate GitHub issues in browser	Web Code	No local environment inheritance
Start from Slack	Slack integration	Official connector requirements
Cloud plan, local execution	Ultraplan then terminal	Gateway can apply when execution returns locally
Deep cloud review	Ultra review commands	Separate official feature and billing

Configure secrets, setup scripts and allowlists inside the cloud environment for private services. Local shell/user settings and Passion8 tokens do not synchronize automatically.

#Review, Ultraplan and Ultrareview

Capability	Entry	Use	Consideration
/code-review	Local/PR review	Routine diffs	Local mode can retain gateway configuration
Official Code Review	GitHub app/check	Automated PR review	Official integration, caps and permissions
Ultraplan	CLI to cloud	Deep planning	Execute on web or return locally
Ultrareview	Cloud multi-agent	Deep premerge bugs	Independent context/cache

For Passion8 costs/providers, prefer local review or headless diff analysis. Treat official deep cloud review as a separate execution path and cache.

See review and CI for complete setup.

#Agent Teams and Channels

Advanced collaboration/event entry points:

Feature	Purpose	Recommendation
Teams	Multiple collaborating sessions	Large reviews, cross-checks and parallel hypotheses
Channels	MCP pushes CI/chat/alert events into sessions	Respond to external events
Channel reference	Notifications, replies and permission relay	For custom MCP/channel plugins

These increase parallel usage and permission complexity. Verify forwarding of tools, MCP, caching and channel fields; see gateway guidance.

See Teams and Channels for teammates, MCP, relay and enterprise policy.

#Caching and cost

Action	Effect
Continuous local session	Stable prefixes refresh either TTL
IDE to CLI	Some reuse if directory/model/effort/prompt match
Local to cloud/Slack	Usually different session/provider/cache
New CI job	Short-term project reuse possible; runner/environment may change keys
Teams/Ultrareview	Separate subtask caches increase total tokens

See command effects and TTL fundamentals.

#Official references

PreviousDesktop, Web, and IDE workflows NextChrome and computer use

Support

Need help?

For setup, billing, or model issues, email us. Check the status page for uptime.

Support Email[email protected]Service Statusstatus.passion8.cc

WeChat / QQ support is available at the bottom right.