Skip to main content

Common Scenarios

Step-by-step guides for typical Remi usage patterns.

Monitor From Phone on Same WiFi​

You are working on a project and want to check Claude's progress from your phone while moving around the house.

# On your computer (binds to all interfaces by default)
remi my-project

On your phone, open the Remi web app and enter the direct WebSocket URL:

ws://192.168.1.100:18765/ws

Replace 192.168.1.100 with your computer's local IP address.

Monitor Remotely via Relay Code​

You started Claude working on a task and left the house. Connect from your phone over cellular:

# Already running on the server
remi my-project

# View your connection code
remi code

On your phone, open the Remi web app and enter the connection code (e.g., AXBY-1234).

Secure a Permanent Relay Endpoint​

You want your phone to always be able to connect to your dev machine using the same code.

One-time setup​

# Generate server identity
remi keygen

# Generate a permanent code
remi code --refresh

# Export client key from the web app and authorize it
remi authorize client-key.json --label "My Phone"

Daily use​

# Start with permanent code
remi --permanent-code my-project

The connection code stays the same across restarts. Your phone connects with the code and authenticates with its Ed25519 key.

Multiple Authorized Devices​

Authorize your phone and laptop to both connect:

# Authorize phone
remi authorize phone-key.json --label "Phone"

# Authorize laptop
remi authorize laptop-key.json --label "Laptop"

# Check both are registered
remi keys

Each device can connect independently. Over direct WebSocket, multiple clients can connect simultaneously (up to 100). Over relay, only one remote client connects at a time.

Resume a Session From Another Terminal​

You closed your terminal but Claude was mid-task.

# See what sessions exist
remi --sessions

# Resume the most recent one
remi --resume

# Or resume a specific session
remi --resume abc12345

Remi looks up the Claude session ID and passes --resume to Claude Code automatically.

Attach to a Running Session​

Remi is running in one terminal (or as a service) and you want to interact with it from another terminal:

# List live sessions
remi ls

# Attach (auto-selects most recent)
remi attach

# Detach: Ctrl+B d

Run as a Background Service​

Set up Remi to start automatically on login:

remi keygen
remi code --refresh
remi --install

Remi runs in daemon mode and creates sessions on demand when clients connect.

To stop:

remi --uninstall