DEV Community

Cover image for Claude Code Channels Can't Approve Permissions from Your Phone. Here's What Can.
Yurukusa
Yurukusa

Posted on • Edited on

Claude Code Channels Can't Approve Permissions from Your Phone. Here's What Can.

Claude Code Channels launched this week. You can send messages from Telegram or Discord into a running session. Your AI has full filesystem, git, and MCP access. You can code from your phone.

One problem: permission prompts still pause the session. You can't approve them from your phone.

The Gap

You're on a train. Your Claude Code session hits a git push command. It needs approval. The session pauses silently. You don't know until you get home and check the terminal.

Channels gives you input. It doesn't give you approval authority.

Why This Matters for Autonomous Sessions

If you run Claude Code unattended (overnight, during meetings, while you sleep), permission prompts are the #1 cause of silent stalls. Channels doesn't fix this — it was designed for interactive use, not autonomous operation.

The Fix: PreToolUse Hooks

PreToolUse hooks run before the permission system. They can auto-approve safe commands and hard-block dangerous ones — without any human interaction.

{
  "permissions": { "allow": ["Bash(*)"] },
  "hooks": {
    "PreToolUse": [{
      "matcher": "Bash",
      "hooks": [{ "type": "command", "command": "~/.claude/hooks/destructive-guard.sh" }]
    }]
  }
}
Enter fullscreen mode Exit fullscreen mode

With this pattern:

  • Safe commands: auto-approved, no prompt
  • Dangerous commands (rm -rf, force push, git add .env): hard-blocked, exit code 2
  • Everything in between: your call

One Command Setup

npx cc-safe-setup
Enter fullscreen mode Exit fullscreen mode

667 hooks. 10 seconds. Covers destructive commands, force push, .env leaks, syntax errors, context window monitoring, and more. 2,9,200+ tests.

GitHub

Channels + Hooks = Best of Both

The ideal setup:

  1. Hooks handle permission decisions automatically (safe = allow, dangerous = block)
  2. Channels let you send new instructions from your phone
  3. No permission prompts = no silent stalls

Channels is great for input. Hooks are great for judgment. Use both.


Top comments (2)

Collapse
 
armorer_labs profile image
Armorer Labs

This is the gap we're solving with Armorer Gauntlet — a mobile command deck specifically built for local coding agents like Claude Code.

Gauntlet gives you: QR-first pairing to connect your phone to the local daemon quickly, push notifications when a session needs input or approval, and the ability to approve requests directly from your phone without reopening the laptop.

The key difference: it's not a tiny terminal. It's just the controls that matter — status, approvals, next instructions — on your phone. And the relay is self-hosted, so your laptop credentials never leave the machine.

If you're running Claude Code and want to step away without stalling the agent, this is the layer you're missing.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.