[Feature Request] Add inverse of `/teleport`: push local CLI session to Cloud

Feature Description

A "send to cloud" command - the inverse of /teleport.

/teleport moves a Claude Code Cloud (claude.ai/code) session down to the local CLI. There's no command that goes the other direction: taking the current CLI conversation and continuing it in the web app or mobile.

What already exists, and why it doesn't cover this

• claude --remote "..." / /remote spins up a brand new cloud session. It doesn't migrate conversation history, active todos, or working-directory state — and it requires you to push commits first because the cloud VM clones fresh from GitHub. That's a "start a new task in the cloud" flow, not a handoff.
• The Desktop app already has a "Continue in" menu that hands a local session over to the web (per the official docs — "Move tasks between web and terminal"). So the pattern is already established in one surface — it just doesn't exist on the CLI, which is the primary coding surface for most Claude Code users. The docs explicitly call this out:

> "From the CLI, session handoff is one-way: you can pull cloud sessions into your terminal with --teleport, but you can't push an existing terminal session to the web."

So the asymmetry is intentional today, but it's surprising — once you've used /teleport and the Desktop "Continue in" menu, discovering the CLI can't do the reverse feels like a gap rather than a design choice.

Use case

I sometimes start work in the terminal where I have full filesystem and shell access, then want to continue from a browser or phone later (or on another machine) without re-explaining context to a fresh session. Today the workaround is manual: summarise, commit current state, restart on the other client — which loses the conversational scaffolding, any uncommitted changes, and the active todo list.

Even a partial-fidelity handoff would help: transcript + active todos + a snapshot of working-directory state (or just the diff), without trying to replicate local shell or MCP connections. The cloud session inherits a degraded toolset — that's fine and expected; what matters is keeping the conversational context alive.

Concrete scenarios where this matters:

• Stepping away mid-session and continuing on my phone
• Knowing I need to leave halfway through a coding session and wanting it to keep going in the cloud
• Developing on aircraft Wi-Fi that's about to cut out on descent
• Switching machines without losing where I was

The Desktop app proves the pattern works. The CLI just needs parity.

Suggested names

• /teleport-up — reads as the obvious inverse and matches existing vocabulary
• /share-to-cloud

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 2.1.129
• Feedback ID: bb259173-9384-46b3-8015-6e19b9bacd70

Thanks team - appreciate you all!
Ben