CloudCodeTree LogoCloudCodeTree
AI NewsTutorialsAbout
CloudCodeTree Logo
CloudCodeTree
  • AI News
  • Tutorials
  • About
← Back to AI News
Remote Control Requires User-Scope Enable Now — and How --teleport Pulls a Cloud Session Into Your Terminal

Remote Control Requires User-Scope Enable Now — and How --teleport Pulls a Cloud Session Into Your Terminal

Chris Harper

2 min read

Aug 5, 2026 · 12:05 UTC

AI
Workflow
Claude Code
Best Practices

August 4 change: repo-local .claude/settings.json can no longer enable Remote Control — fix it with /config in Claude Code. Bonus: claude --teleport pulls any cloud session to your local terminal.

Two changes in one: a Claude Code scope fix you need to make, and a workflow that makes web → local context hand-off seamless.

Breaking change: Remote Control must be enabled at user scope

Before August 4, you could add "remoteControlEnabled": true to your project's .claude/settings.json or .claude/settings.local.json and Remote Control would auto-start. As of the August 4 release, repo-local settings can no longer enable it — they can still disable it, but enabling requires user-scoped config.

Fix it in 30 seconds:

# Inside a Claude Code session:
/config remoteControlEnabled true

This writes to ~/.claude/settings.json at user scope, persists across all your projects, and allows repo-level settings to disable it where needed (e.g., sensitive repos). You only need to do this once per machine.

The security rationale: a repository's settings file should not escalate your device's Remote Control exposure — that decision belongs to the machine owner, not the project.

Bonus: --teleport pulls a cloud session to your local terminal

Remote Control is also what powers claude --teleport. If you kick off a task at claude.ai/code (or on mobile), --teleport pulls the full conversation history and working branch into your local terminal:

claude --teleport
# → interactive picker of your active cloud sessions
# → switches your local shell to the cloud session's git branch
# → continue with all context intact

This is one-way (cloud → local). For the reverse — start locally, monitor from your phone — /remote-control starts a session you can observe and redirect from any browser. Enable it first with /config remoteControlEnabled true at user scope.

Sources: Remote Control docs — Claude Code · Claude Code on the web docs · Session teleportation guide — proflead.dev