DEV Community

Cover image for Claude Code Remote: Your AI, Anywhere You Go
Rajesh Royal
Rajesh Royal

Posted on

Claude Code Remote: Your AI, Anywhere You Go

#tutorial #claudecode #productivity #beginners

Start a task at the office. Finish it at home. Claude doesn't mind the commute.

From: x.com/adocomplete

Introduction

We've all been there. You're deep into a complex refactoring session with Claude Code, making great progress, and then—life happens. You need to leave for a meeting, catch a train, or simply call it a day. Your Claude session? Stuck on that machine, in that terminal, waiting for a return that might not come for hours.

What if your AI assistant could follow you? What if you could fire off a task, let it run in the background, and resume exactly where you left off—on a completely different machine?

Welcome to Day 9 of our 31 Days of Claude Code Features series. Today, we're exploring Claude Code Remote—the feature that untethers your AI workflow from any single device.

The Problem

Modern development is inherently multi-device. You might:

  • Start work on a desktop, then switch to a laptop for a meeting
  • Begin a task at the office and want to check on it from home
  • Kick off a long-running AI task and close your laptop to commute
  • Work across multiple machines depending on context

Traditional terminal sessions don't travel well. SSH and tmux help for server-side work, but local Claude Code sessions? They're bound to the terminal that spawned them.

This creates several frustrations:

Lost context: Closing a session means losing the conversation history, the accumulated understanding, and the partial progress.

Blocked workflows: You can't start something intensive and walk away. The session needs babysitting.

Device lock-in: Your Claude relationship is tied to a physical machine instead of being truly portable.

In a world where work follows us everywhere, our AI tools should too.

The Solution

Claude Code Remote introduces two powerful features: background tasks and session teleportation.

Sending Tasks to the Cloud with &

Want Claude to work on something while you do other things (or nothing at all)? Prefix your prompt with &:

& Refactor the authentication module to use JWT tokens instead of sessions
Enter fullscreen mode Exit fullscreen mode

This sends your task to Claude Code's cloud infrastructure. The work continues in the background, even if you:

  • Close your terminal
  • Shut down your computer
  • Go completely offline

Resuming Sessions with --teleport

Every background task gets a session ID. To pull that session back into your local terminal:

claude --teleport session_abc123
Enter fullscreen mode Exit fullscreen mode

This "teleports" the session—including all history, context, and results—to your current machine. You pick up exactly where Claude left off.

The Complete Workflow

Step 1: Start a background task

& Analyze the entire codebase and create a comprehensive README with architecture diagrams
Enter fullscreen mode Exit fullscreen mode

Output:

🚀 Task sent to background
Session ID: session_7f3a9b2c
Status: Running

Track progress: claude --status session_7f3a9b2c
Resume locally: claude --teleport session_7f3a9b2c
Enter fullscreen mode Exit fullscreen mode

Step 2: Check status from anywhere

claude --status session_7f3a9b2c
Enter fullscreen mode Exit fullscreen mode

Output:

Session: session_7f3a9b2c
Status: Completed ✓
Duration: 4m 32s
Result: README.md created, 3 diagram files generated
Enter fullscreen mode Exit fullscreen mode

Step 3: Teleport and continue

claude --teleport session_7f3a9b2c
Enter fullscreen mode Exit fullscreen mode

You're now in the session, with full history, ready to review results or continue the conversation.

Pro Tips

1. Use meaningful prompts for background tasks

Since you won't be there to clarify, make your initial prompt comprehensive:

& Audit all API endpoints in src/routes/ for security vulnerabilities.
  Focus on: input validation, authentication checks, SQL injection, and XSS.
  Create a report.md with findings and recommended fixes.
Enter fullscreen mode Exit fullscreen mode

2. Queue multiple background tasks

You can run several background tasks simultaneously:

& Generate unit tests for src/utils/
& Update all dependencies and fix breaking changes
& Create API documentation in OpenAPI format
Enter fullscreen mode Exit fullscreen mode

Each gets its own session ID for independent tracking.

3. List all your sessions

claude --sessions
Enter fullscreen mode Exit fullscreen mode

Output:

Active Sessions:
├─ session_7f3a9b2c  [Completed]  "Analyze codebase..."     4m ago
├─ session_2d8e1f4a  [Running]    "Generate unit tests..."  2m ago
└─ session_9c5b3a7e  [Completed]  "Update dependencies..."  8m ago
Enter fullscreen mode Exit fullscreen mode

4. Cancel runaway tasks

Started something you shouldn't have? Cancel it:

claude --cancel session_2d8e1f4a
Enter fullscreen mode Exit fullscreen mode

5. Set up notifications

Configure webhooks or email notifications for task completion:

& [notify:email] Run full integration test suite and report failures
Enter fullscreen mode Exit fullscreen mode

Real-World Use Case

It's 5:45 PM on Friday. You've been working on a legacy codebase that desperately needs modernization. You have a good understanding of what needs to happen, but the actual work will take Claude some time.

Instead of staying late or leaving the task incomplete, you:

& Modernize the user-service module:
  - Convert all callbacks to async/await
  - Add TypeScript types
  - Update deprecated API calls
  - Add error handling with custom error classes
  - Write migration guide in MIGRATION.md

  Take your time. Be thorough.
Enter fullscreen mode Exit fullscreen mode

Output:

🚀 Task sent to background
Session ID: session_fri_evening
Enter fullscreen mode Exit fullscreen mode

You close your laptop and head home. Saturday morning, coffee in hand, you open your personal laptop:

claude --status session_fri_evening
Enter fullscreen mode Exit fullscreen mode 
Status: Completed ✓
Duration: 23m 47s
Files modified: 12
New files: MIGRATION.md, types/user-service.d.ts
Enter fullscreen mode Exit fullscreen mode 
claude --teleport session_fri_evening
Enter fullscreen mode Exit fullscreen mode

You're in the session. Claude walks you through everything it did. You review changes, ask clarifying questions, and request a few adjustments—all from your couch.

Work that would have kept you at the office became a Saturday morning side activity. That's the power of session mobility.

Conclusion

Claude Code Remote dissolves the artificial boundary between you and your AI assistant. Work starts when you have an idea, not when you're at a specific computer. Tasks complete whether you're watching or not. Sessions travel with you, not with your hardware.

The & prefix and --teleport flag are simple in syntax but transformative in practice. They represent a fundamental shift: AI as a persistent collaborator rather than a momentary tool.

Start a task. Walk away. Come back anywhere. That's not just convenience—it's a new way of working.

Coming up tomorrow: You've been using Claude Code for a while now, but how much have you really used it? Day 10 introduces /stats—your personal Claude Code usage dashboard. In 2025, orange is the new green.

This is Day 9 of the "31 Days of Claude Code Features" series. Follow along to discover a new powerful feature every day.

Top comments (0)