Web, remote control, and mobile
Hosted Code, Remote Control, teleport, cloud setup, PR autofix, scheduling, mobile, and gateway limits.
Claude Code has several remote workflows. See Platforms and integrations for a broad comparison and Desktop/Web/IDE workflows for entry-point details.
| Form | Execution location | Use |
|---|---|---|
| Remote Control | Your local machine; browser/mobile provides input | Follow a local task while away |
| Code on the web | Anthropic-hosted sandbox | Dispatch GitHub work from a browser/phone |
| Teleport | Bring a web session into a local terminal | Continue cloud work locally |
#Remote Control
| Aspect | Detail |
|---|---|
| Code and commands | Still run locally |
| Remote client | Sends prompts, shows status, receives notifications |
| Start | /remote-control or claude remote-control |
| Suitable | Complex local environment while you are away |
Current session:
/remote-controlServer mode:
claude remote-control --name "my-project"#Passion8 limitations
Remote Control depends on claude.ai identity and supported first-party routing.
| Configuration | Effect |
|---|---|
| API/token/helper credentials | Can disable Remote Control and voice features |
| Non-first-party Base URL | Remote Control disabled in applicable current versions |
| Subscription login | Normally needed for device pairing |
Treat this as an official-account feature, not Passion8's primary connection method. Use local CLI/IDE for gateway model requests.
#Code on the web
Hosted execution suits:
- Dispatching GitHub issues/PR fixes from browser or mobile.
- Creating branches, running tests, and proposing PRs.
- Fixing CI failures and review comments.
- Parallel work without occupying your computer.
Common entry points:
/web-setup
/autofix-pr
/ultraplan
/ultrareview
/scheduleCloud sessions have separate sandboxes, network rules, setup scripts, GitHub connections, and caches. Local settings and Passion8 tokens are not automatically copied there.
#Cloud setup scripts
| Component | Detail |
|---|---|
| System tools | Common languages/package managers in the sandbox |
| GitHub | Official connection for repositories/issues/PRs |
| Network | Security proxy and allowed-domain rules |
| Environment cache | Reuses setup results for faster starts |
| SessionStart hook | Small project actions required on each start |
Private registries, internal APIs, and custom gateways require appropriate cloud network access and secret injection. Local shell credentials do not automatically transfer.
#Teleport
| Scenario | Why useful |
|---|---|
| Cloud already created branch/plan | Continue debugging locally |
| Local databases/devices/LAN required | Unreachable from hosted sandbox |
| Continue with Passion8 locally | Local provider configuration applies |
/teleportOr:
claude --teleportHistory can continue, but the actual provider becomes the local configuration. Changes to model, effort, system prompt, tools, or provider can make the next turn cold.
#PR autofix
Autofix dispatches a hosted session to watch the current branch's PR and address CI failures or review comments.
/autofix-pr only fix lint and type errors| Aspect | Detail |
|---|---|
| PR discovery | Usually gh pr view and current branch |
| Runtime | Code on the web |
| Cache | Separate cloud cache, not the local Passion8 cache |
| Boundary | Suitable for CI/PR work, not local-only secrets |
#Schedule and loop
| Mechanism | Runtime | Cache considerations |
|---|---|---|
| /loop | Repeated turns in the current session | Shorter-than-TTL intervals favor hits |
| /schedule | May require hosted/GitHub support | Each scheduled run follows its own interval |
| Desktop scheduled tasks | Supported Desktop/hosted surface | Depends on location/account |
| Routines | Hosted automation | Independent cloud runs |
Intervals over five minutes may leave an API/provider cache cold. Longer supported TTL can suit periodic checks. See Routines and loop scheduling.
#Choose a workflow
| Need | Recommendation |
|---|---|
| Passion8 model calls | Local CLI/IDE or supported local Desktop configuration |
| Follow local work on a phone | Remote Control with compatible account/routing |
| Cloud PR repair | Web and autofix-pr |
| Cloud plan, local execution | Ultraplan/web, then teleport |
| Periodic checks | Short loops locally; routines/scheduled tasks for durable automation |
| Local database/LAN | Keep execution local |
#Official references
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.

