When running Claude Code on a schedule or as part of some automation, how do you handle permissions for truly dangerous or high-stakes tool calls? I’m assuming you don’t have access to the CLI interface, especially if Claude Code is being called programmatically. A few things I’m genuinely curious about: How do you get notified that Claude is waiting for your input? How do you communicate your decision back? I’ve seen people use messaging services like Slack or Discord for this, but how do you ensure the permissions are handled exactly as you intended from a free-text reply? Is this even a problem people here actually have, or is everyone just running with --dangerously-skip-permissions and scoping things down with --allowedTools? I’m trying to gather feedback for a took I’m building, justack.dev, a typesafe human-in-the-loop API for autonomous agents. As part of it I made a Claude Code hook that lets you configure which tools are dangerous, and when running headless, sends you a notification at your inbox where you can view the full details and approve/deny with optional instructions or modified tool parameters. It has generous free tier limits, so would appreciate anyone giving it a try and sharing their thoughts. submitted by /u/kms_dev
Originally posted by u/kms_dev on r/ClaudeCode