← ClaudeAtlas

cloud-local-bridgelisted

Hand work between the user's cloud sessions (Claude Code on the web, claude.ai/code) and local sessions (Claude Desktop, `claude remote-control`) and get the result back without the user naming sessions. Use when a cloud session needs something only the user's machine can do (browser, OAuth sign-in, desktop apps, local files, local MCP servers) — "delegate to a local agent", "hand this to my local session", "run this on my computer" — and when a local session receives a cross-session-message tag from another session or is told to "send it back".
ShiJianXi/molt · ★ 1 · AI & Automation · score 67
Install: claude install-skill ShiJianXi/molt
# Cloud-local bridge Two roles. Find yours: a cloud session handing work down is the **sender**; a local session that received a `<cross-session-message from-session="session_…">` is the **receiver**. ## Facts that cause the failures (observed October 2026, Claude Code 2.1.28x) - `SendMessage` with the **name a `ListAgents` row prints** is the only route that worked in both directions. Local sessions see a cloud session by its **title** (e.g. `Fix login redirect`), never by its `session_…` id or its own cloud-side name (`user-e8`, `user-fb`). - The cloud wrapper says to reply through "the send_message tool of the Claude Code Remote MCP server" with the `session_…` id. A Desktop session has no such tool. `SendMessage` with the `session_…` id fails ("No agent named … is reachable"), and `mcp__ccd_session_mgmt__send_message` fails ("session … not found"): that one only reaches local Desktop sessions. - A local session is visible from the cloud only while it is open, unarchived and on Remote Control. Desktop: a session joins when the app's "Connect new sessions to Remote Control" setting is on or the user turns it on for that session; with auto-archive on PR close, it disappears when its PR closes. Terminal: only `claude remote-control` (or `/remote-control` inside a session). - A computer running `claude remote-control --spawn worktree` shows up in the cloud's `list_environments` as `kind: "bridge"`, named `<host>:<folder>:<id>`. `create_session` with that