Approve Claude's Prompts from Your Phone with Permission Relay
Long Claude Code sessions are great until they hit a permission prompt and sit there blocked while you're away from your desk. Permission relay solves this by pushing those prompts to your phone instead of freezing the terminal.
Start a session with channels enabled:
claude --channels
When Claude hits an action that needs approval, any connected channel server that supports the permission capability can relay the prompt to your mobile device. You approve or deny from your phone, and the session continues without you needing to be at the keyboard.
For a direct browser or phone bridge, use the /remote-control command inside an active Claude Code session. This links your terminal to claude.ai/code and the Claude iOS or Android apps, so you can monitor and respond to prompts wherever you are.
# Inside an active session:
/remote-control
A few practical notes:
- Permission relay is a research preview feature — channel servers need to explicitly declare the permission capability
/remote-controlis available for both the terminal and the VS Code extension- Remote sessions appear in your conversation history with auto-generated titles
- The Claude mobile apps for iOS and Android are the primary way to receive relayed prompts
This pairs especially well with overnight or long-running refactor tasks — kick off the session, go to dinner, and handle the occasional approval from your phone.
Start long sessions with --channels and never come back to a stalled terminal again.
Log in to leave a comment.
When Claude writes error messages, button labels, validation text, or onboarding flows, it defaults to generic developer-speak. Add a "Users" section to your CLAUDE.md describing who your actual users are — their technical level, industry jargon, and what they care about — so Claude writes copy that makes sense to THEM, not to developers.
Use the --agent flag with custom markdown files in .claude/agents/ to launch purpose-built Claude sessions with restricted tools and scoped system prompts.
Every project has traps — the billing module that silently fails if you forget to queue the job, the legacy table with column names that don't match the model, the config value that must be set before tests run. Document these gotchas in your CLAUDE.md so Claude avoids the same mistakes your team spent days debugging.