Documentation

Everything you need to connect your Claude Code sessions to Remo Code.

Quick Start

1. Create an account

2. Create a session

In the Remo Code dashboard, click "New Session" and give it a name (e.g., your project directory name). You'll receive a registration token.

  # Via API
 curl -X POST https://app.remo-code.com/api/sessions \
   -H "Cookie: session=YOUR_SESSION_COOKIE" \
   -d '{"name": "my-project"}'  

3. Install the channel plugin

In your Claude Code terminal, run the configure skill:

  # In Claude Code
 /hub:configure rmc_your_token_here  

This saves the hub URL and token to ~/.claude/channels/hub/.env and activates the channel plugin.

4. Start chatting

Open app.remo-code.com in any browser. Your session should appear as "online" in the sidebar. Select it and start chatting.

How It Works

Remo Code has three components:

Hub Server

The central relay that connects browsers to Claude Code sessions. Handles auth, message routing, and chat history storage. Deployed on our infrastructure.

Channel Plugin

A lightweight MCP plugin that runs inside each Claude Code session. It connects to the hub via WebSocket and relays messages. Runs locally on your machine.

Web UI

The browser app at app.remo-code.com. Shows your connected sessions, lets you send messages, and displays responses in real time.

  Browser (any device)
     ↕ WebSocket + REST
 Hub Server (cloud)
     ↕ WebSocket
 Channel Plugin (your machine)
     ↕ MCP / stdio
 Claude Code (your machine)  

Security Model

Your code stays local. The channel plugin only sends text messages (what you type and what Claude responds). Your source code, files, and filesystem are never transmitted to the hub.

Your API key stays local. Claude Code uses your Anthropic subscription directly. Remo Code never sees or stores your API credentials.

Token-based session auth. Each Claude Code session gets a unique registration token. The token is hashed before storage — even if the database were compromised, tokens cannot be recovered.

Encrypted in transit. All connections use TLS (HTTPS/WSS). Messages between your browser, the hub, and the channel plugin are encrypted in transit.

Troubleshooting

Session shows "offline"

Make sure Claude Code is running with the channel plugin active. Check that the token in ~/.claude/channels/hub/.env matches the one in your dashboard. The plugin auto-reconnects, but if it's stuck, restart Claude Code.

Messages not delivering

Verify the session is showing "online" in the sidebar. If the session is "offline", the channel plugin is not connected. Check your internet connection and ensure no firewall is blocking outbound WebSocket connections.

Plugin installation fails

Ensure you're running a recent version of Claude Code that supports channels/plugins. The /hub:configure skill requires the experimental channel API. Update Claude Code if needed.