Heidelberg AICurriculum

This Is My Favorite Claude Code Feature...

NeuralNine ·2026-06-05 ·1 min read

Summary written by us from the video's transcript. The video, and everything in it, is NeuralNine's work.

Learn how to use Claude Code’s remote‑control feature to code from a phone or other device while keeping a session active on your computer.

Takeaways

  • Activate remote control with `/remote control` to generate a QR code for phone access.
  • Approve or deny code suggestions directly on your phone, keeping the laptop idle.
  • Use the feature for quick UI tweaks, simple additions, or brainstorming while away from the desk.
  • Start sessions with `Claude --remote control` to keep both desktop and mobile interfaces active.
  • Run remote sessions in isolated environments and terminate them with `/exit` when finished.

Starting a Remote Control Session

Open any project directory and launch a Claude Code session. Use the slash command `/remote control` (or simply `/remote`) to activate remote mode, which generates a link and QR code for connecting another device.

Connecting from Your Phone

Scan the displayed QR code or open the provided link on your phone. The phone shows the active session tied to your computer, allowing you to view prompts, suggestions, and execution results in real time.

Sending Prompts and Approving Changes

From the phone you can type commands such as “create a basic minimal Flask app” or “change the style of the application to blue.” The prompt is sent to the computer session, which returns suggested code changes. You can approve or deny those suggestions directly on the phone with an “allow once” tap, without touching the keyboard on the laptop.

Session Variants and Flags

You can start a remote‑only session with `Claude remote control` (no dashes) – this gives you only a phone interface, not an interactive desktop session. Using `Claude --remote control` or the `/remote control` slash command keeps both interfaces active, letting you switch between laptop and phone as needed.

Practical Use Cases

Remote control works best for lightweight tasks: tweaking UI colors, adding simple features, brainstorming code changes, or querying the code base while away from your desk. Complex engineering work is less suited to phone interaction. Voice input can also be used to issue commands on the go.

Managing Sessions and Security Tips

You can run multiple remote sessions in different project folders and switch between them on your phone. Because the session remains active on the host machine, keep it in an isolated environment (e.g., a sandbox or VM) and avoid granting excessive permissions. Use `/exit` from either device to terminate the session, though the command may not always succeed reliably, so treat it as a convenience rather than a strict security control.