Claude Code

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.

FormExecution locationUse
Remote ControlYour local machine; browser/mobile provides inputFollow a local task while away
Code on the webAnthropic-hosted sandboxDispatch GitHub work from a browser/phone
TeleportBring a web session into a local terminalContinue cloud work locally

#Remote Control

AspectDetail
Code and commandsStill run locally
Remote clientSends prompts, shows status, receives notifications
Start/remote-control or claude remote-control
SuitableComplex local environment while you are away

Current session:

/remote-control

Server mode:

claude remote-control --name "my-project"

#Passion8 limitations

Remote Control depends on claude.ai identity and supported first-party routing.

ConfigurationEffect
API/token/helper credentialsCan disable Remote Control and voice features
Non-first-party Base URLRemote Control disabled in applicable current versions
Subscription loginNormally 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
/schedule

Cloud 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

ComponentDetail
System toolsCommon languages/package managers in the sandbox
GitHubOfficial connection for repositories/issues/PRs
NetworkSecurity proxy and allowed-domain rules
Environment cacheReuses setup results for faster starts
SessionStart hookSmall 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

ScenarioWhy useful
Cloud already created branch/planContinue debugging locally
Local databases/devices/LAN requiredUnreachable from hosted sandbox
Continue with Passion8 locallyLocal provider configuration applies
/teleport

Or:

claude --teleport

History 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
AspectDetail
PR discoveryUsually gh pr view and current branch
RuntimeCode on the web
CacheSeparate cloud cache, not the local Passion8 cache
BoundarySuitable for CI/PR work, not local-only secrets

#Schedule and loop

MechanismRuntimeCache considerations
/loopRepeated turns in the current sessionShorter-than-TTL intervals favor hits
/scheduleMay require hosted/GitHub supportEach scheduled run follows its own interval
Desktop scheduled tasksSupported Desktop/hosted surfaceDepends on location/account
RoutinesHosted automationIndependent 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

NeedRecommendation
Passion8 model callsLocal CLI/IDE or supported local Desktop configuration
Follow local work on a phoneRemote Control with compatible account/routing
Cloud PR repairWeb and autofix-pr
Cloud plan, local executionUltraplan/web, then teleport
Periodic checksShort loops locally; routines/scheduled tasks for durable automation
Local database/LANKeep 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.