Supercharge

Supercharge Studio

Desktop, Android, and the headless server that phones connect to

Supercharge Studio

Supercharge Studio is the window and the phone app for the same agent as the CLI. It does not have its own model account. You still install the CLI, run /setup, and pay the provider you connected. Studio reads ~/.supercharge/ on the computer where the agent runs, so a chat you start in the terminal and a chat you start on the phone are the same session store.

Three pieces ship together:

PieceWhere it runsWhat it is
Desktop appLinux, macOS, Windows with a screenA native window. It starts the agent for you.
Android appA phoneThe remote control. It never runs the model itself.
ServerA terminal-only Linux, macOS, or Windows machineA small gateway. The phone pairs with it. It starts supercharge agent serve.

Download the newest files from the Studio release. Names do not include a version, so the same link stays current.

https://github.com/supercharge-cli/supercharge-studio/releases/latest/download/<file>

Check a running server with supercharge-studio-server --version. The desktop About line and the Android app version are the same release.

What the phone can do

After a phone is paired it can:

  • list projects and open sessions that already exist on that computer
  • send prompts and watch the turn stream
  • answer permission requests (shell, file edits) from the phone
  • attach files. The gateway saves them on the computer and the agent reads those paths
  • export a chat or copy a share link. Pasting that link into another Studio message box opens the same conversation

The phone does not store your provider key. The key stays in ~/.supercharge/config.toml on the computer.

How a phone finds the computer

Pairing prints one link:

scstudio://pair?u=ws://<ip>:2420/gw&i=<id>&k=<key>&n=<name>&r=wss://relay.superchargeai.in/v1/connect/<host>
PartMeaning
uDirect gateway, usually ws://<lan-or-public-ip>:2420/gw.
i and kOne-time pairing id and key. The link expires in 120 seconds and works once.
nName shown on the phone. Defaults to the hostname.
rPublic relay. Present when the computer is in Public mode.

On the same Wi-Fi the phone uses u. From mobile data, or from another network, it uses r. The relay only forwards encrypted frames. It does not see prompts.

The built-in relay is wss://relay.superchargeai.in. A desktop in Public mode and a server started with --relay or SCS_RELAY both use it unless you pass another URL.

Ports

PortWho listensWho connects
2420Studio gatewayThe phone, when it is on a network that can reach this host. The gateway moves to the next free port up to 2430 if 2420 is taken, and remembers the choice.
127.0.0.1:2422Control socketsupercharge-studio-server pair on that same machine. Not exposed.
127.0.0.1:2419supercharge agent serveOnly the gateway. This is the ACP WebSocket.

A firewall can block 2420 and the phone can still work through the relay. Nothing on the public internet needs 2419 or 2422.

Which page to read

  • Desktop for Linux, macOS, and Windows with a screen.
  • Android for the APK, pairing, and what the phone stores.
  • Server for a VPS or any machine with only a terminal, including systemd.
Ctrl+I
Assistant

How can I help?

Ask me about configuration, installation, or specific features.