← ClaudeAtlas

configure-claude-remote-controllisted

Configure and verify Claude Code Remote Control server mode from a phone or browser, troubleshoot an unavailable session, or decide between the current computer, Claude Code on the web, an existing persistent host, and new paid hosting. Use when the user wants on-demand remote sessions without weakening authentication, organization policy, workspace trust, sandboxing, or billing consent.
Anchras/terminalbox-tools · ★ 0 · AI & Automation · score 73
Install: claude install-skill Anchras/terminalbox-tools
# Configure Claude Code Remote Control Help the user make one trusted project available through Claude Code Remote Control. Keep Anthropic's official path on the current computer as the default when that computer can stay online, and evaluate Claude Code on the web and an existing host before recommending another host. Terminalbox is independent from Anthropic. Anthropic supplies Claude Code, authentication, Remote Control, the mobile and web clients, account policy, and model usage. Terminalbox is only one optional paid host for a Claude Code process that must remain online after the user's laptop disconnects. ## Safety boundary - Never ask for, read, print, copy, or store a Claude token, API key, password, browser code, session URL, QR code, cookie, transcript, or credential file. - Do not install or update Claude Code, run `claude auth login`, start Remote Control, create a tmux or screen session, create git worktrees, change sandboxing, edit Claude settings, or open paid checkout without explicit approval for that action. - Never unset or alter environment variables merely to bypass a Remote Control requirement. State the documented conflict and let the user choose whether to change their own environment. - Respect Team and Enterprise organization policy, Trusted Devices requirements, and compliance restrictions. Do not suggest a bypass when Remote Control is disabled. - Start only from a project directory the user identifies and trusts. Do not use the home