[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Feature Request: iOS/iPadOS session as a remote window into macOS Claude Code session

Summary
When a user has Claude Code running on macOS with MCPs configured, an iOS/iPadOS session logged into the same account should be able to attach to that desktop session as a remote window — rather than spinning up a fresh, empty cloud container.
How it would work

Proposed Solution

iOS Claude Code
↕
Anthropic (relay)
↕
macOS Claude Code

1. Mac user enables “allow remote session” — generates a shared key

1. User enters key once in iOS app to link the devices

1. Anthropic routes the iOS session to the Mac session — already has both authenticated connections

1. iOS becomes input/output only — all compute, MCPs, and env vars stay on the Mac

Why
Right now iOS Claude Code gets a blank cloud container with no MCPs, no credentials, no access to local tools. The desktop session already has all of that configured. There’s no way to carry that context to mobile.

Security
• Anthropic authenticates both ends via existing account login
• Shared key confirms both devices consent to linking
• Anthropic routes but never needs to hold the key
• Standard session encryption applies

Prior art
VS Code Remote, JetBrains Gateway, SSH + tmux all solve the reachability problem. This is the same idea native to Claude Code.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

Use Case: Coding from the couch without losing your dev environment

1. I’m at my desk. Claude Code is running on my Mac with MCPs connected to GitHub, Cloudflare R2, Modal, and Linq. My environment variables are loaded. Everything works end-to-end.

1. I move to the couch with my iPad.

1. I open Claude Code on iPadOS. Because my Mac session is still running and my devices are linked, the iPad attaches to the Mac session instead of spinning up a fresh cloud container.

1. I ask Claude to check why an SMS delivery to Linq failed. Claude can actually call the Linq MCP, inspect the R2 bucket, and trace the error — because it’s running on my Mac where those connections exist.

1. I make a fix, Claude tests it end-to-end, pushes to GitHub. Railway auto-deploys.

1. I never touched my Mac. The iPad was just the screen and keyboard.Without this feature: Step 4 fails. The iPad session has no MCPs, no credentials, no access to R2/Modal/Linq. Claude can read the code but can’t run or test anything. The iPad is a read-only view at best.

Additional Context

_No response_