Remote Control

Make your local terminal a bridge so CrabCode Web / mobile apps can run sessions in your local project.

What it is

Remote Control turns your local terminal into a long-running bridge. After it's up, CrabCode Web or the mobile app — signed in to the same acosmi.com account — can launch sessions inside your local project directories. The model runs locally (your CPU, your files, your permissions); the UI lives in the cloud or in your phone.

Good for: continuing this morning's session from your phone, working from another machine while reusing your home setup, or remote-pairing with a teammate watching your live debug.

When you see this doc

After running crabcode remote-control
After typing /remote-control in the TUI
The pairing prompt on Web / mobile linking to "Learn more"

How to enable

Two entry points work:

bash

crabcode remote-control      # subcommand
# Legacy aliases also accepted: crabcode rc / remote / sync / bridge
crabcode remote-control      # subcommand
# Legacy aliases also accepted: crabcode rc / remote / sync / bridge

Or inside the TUI:

shell

/remote-control
/remote-control

The bridge prints pairing info on start. Sign in to the same acosmi.com account on the Web app or mobile app and the machine shows up there.

Ways a remote client can start a session

Once the bridge is running, a remote client can pick:

Start a new session in a chosen directory
Use a worktree — spawn inside an isolated git worktree so it doesn't clash with what you're editing
Attach to an existing session — share view with a session that's already running locally

The actual menu options depend on your environment.

Typical uses

Continue this morning's session from your phone while you're out
Have a teammate attach from Web to watch your live debug
Drive your home Mac's code env from the office PC

Limits and caveats

Requires an acosmi.com subscription — the bridge authenticates with your acosmi.com account (crabcode auth login)
Needs outbound access to acosmi.com — no inbound port required; the relay lives in the cloud
Local permissions = remote permissions — a remote client can do anything your local terminal can; be careful with permission-bypass switches
Network drops can drop sessions — the bridge is not persistent; recovery depends on session state