> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genesiscomputing.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Remote Connections to Claude Code

> Operator notes for Claude Code Remote Control and cross-session messaging alongside a Genesis deployment.

Companion to [Installing Genesis on GKE with Helm](/docs/deployments/GCP/Genesis-On-GCP-GKE-Install).
How to set up remote / team-up connections to a Claude Code session, and how someone
connects to it. Two distinct features.

<Warning>
  **Read first — the caveat that bites this deployment.** Remote Control does **not**
  work with a custom `ANTHROPIC_BASE_URL` or a non-Anthropic backend (Bedrock,
  Databricks, etc.). The Claude Code running **inside the Genesis pod** routes its LLM
  through Genesis's proxy (pointed at Databricks), so **that** in-pod `claude`
  **cannot use Remote Control.** Enable Remote Control only on a Claude Code session
  logged directly into **claude.ai** (e.g. the session managing the cluster), with
  outbound HTTPS to `api.anthropic.com`.
</Warning>

## A) Remote Control — connect from another device / browser ("team-up")

Use when someone **off the cluster** wants to watch or drive the session from
claude.ai or the mobile app.

**Prerequisites (all required, or it won't turn on):**

* Session logged into **claude.ai** — `claude` → `/login`, a Pro / Max / Team /
  Enterprise account. **Not** an API key, **not** Bedrock/Databricks, **not** a custom
  `ANTHROPIC_BASE_URL`.
* Outbound HTTPS to `api.anthropic.com:443` (Remote Control polls Anthropic). A
  locked-down pod that blocks this cannot use it from inside.
* None of `DISABLE_TELEMETRY` / `DO_NOT_TRACK` /
  `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` set.

**Enable:**

```bash theme={null}
claude remote-control --name "Databricks cluster"
# or, inside an existing session:  /remote-control
```

It prints a **session URL** and a **QR code** (press space to show the QR).

**Verify it's live:**

* Footer shows an `/rc active` indicator.
* `/remote-control` reopens the panel with the URL / QR / disconnect.
* On claude.ai/code the session appears with a **green dot**.

**How the other person connects:**

* Open the **session URL** (or scan the QR in the Claude app).
* It runs under **your** claude.ai account — the other person must be signed into that
  same account (or you share it). There is no cross-*account* join; it's your account
  on multiple devices.

## B) Cross-session messaging — two sessions in the same pod ("remote thread"-style)

Use when a second agent/worker **in the same pod** should coordinate with the primary.
Local Unix sockets — no Internet, works in a locked-down pod.

**Enable** — start the worker as a headless session that accepts messages:

```bash theme={null}
claude -p --settings '{"crossSessionInbound":"accept"}' --name "pod-worker"
# primary session:
claude --name "pod-operator"
```

**Verify:**

* `/list-agents` — the worker shows up (`active` / `idle`).
* `/status` — a `Peer address` row shows a `uds:` socket.

**Send:** just tell Claude, e.g. `Tell @pod-worker to run the scan`.

**Constraint:** only works **between sessions inside the same container** — a pod
session and a laptop session cannot reach each other (separate filesystems).

## Which one to connect *from outside the cluster*

Option **A (Remote Control)**, on a claude.ai-logged-in session with
`api.anthropic.com` egress. **If the pod blocks `api.anthropic.com`, neither remote
option bridges pod ↔ laptop** — connect to the in-pod agent through the **Genesis
sandbox terminal** instead (the browser console or the `genesis` CLI over the Genesis
backend), which is the path the
[deploy runbook](/docs/deployments/GCP/Genesis-On-GCP-GKE-Install) sets up.