Claude Code: /remote-control Comes to VSCode, Bridging Sessions to Browser and Phone
Claude CodeClaude Code v2.1.79 brings the /remote-control command to the VSCode extension, allowing developers to bridge their in-editor coding session to claude.ai/code and continue working from a browser or phone without interrupting execution. Previously available only in the terminal CLI, Remote Control's addition to VSCode closes a significant gap for the large segment of Claude Code users who work primarily through the editor extension. The release also adds AI-generated session titles to VSCode tabs, improving session navigation at a glance.
Sources & Mentions
5 external resources covering this update
/remote-control Arrives in the VSCode Extension
Claude Code v2.1.79 extends the /remote-control command — previously exclusive to the terminal CLI — to the VSCode extension. This brings one of Claude Code's most compelling workflow features to the majority of developers who interact with the tool through their IDE rather than a standalone terminal.
What Remote Control Does
The /remote-control command creates a live bridge between a running Claude Code session and the claude.ai/code web interface. Once activated, the session becomes accessible from any browser or mobile device at claude.ai/code, allowing developers to monitor progress, review outputs, and continue directing the agent from outside the IDE environment.
This is particularly valuable for long-running agentic tasks. A developer can kick off a complex refactor or multi-file feature implementation in VSCode, activate /remote-control, and then step away from their desk — checking in on the task via phone or a secondary device without needing to interrupt execution or open their laptop.
AI-Generated Session Titles in VSCode Tabs
Alongside the Remote Control expansion, v2.1.79 introduces AI-generated session titles for VSCode tabs. Previously, Claude Code sessions in VSCode appeared with generic or sequential tab labels that offered no context about the session's content or purpose. With this update, each session tab receives a title automatically generated by the AI based on the work underway — making it far easier to navigate between multiple concurrent sessions.
For developers who routinely run multiple Claude Code sessions in parallel across different features or branches, this is a meaningful quality-of-life improvement that reduces the cognitive overhead of context-switching.
Why VSCode Parity Matters
The VSCode extension is likely the most common entry point for Claude Code users, given VS Code's dominance in the developer tooling landscape. Features that ship exclusively in the terminal CLI create a two-tiered experience where extension users miss out on capabilities that power users access via the command line.
The v2.1.79 release continues Anthropic's push toward feature parity between the CLI and the VSCode extension, ensuring that the most impactful Claude Code capabilities are available regardless of how a developer chooses to interact with the tool.