Non-blocking notifications for auto-accepted tool calls

Resolved 💬 2 comments Opened Mar 3, 2026 by RaihnForge Closed Mar 31, 2026

Problem

There's a gap between the three current visibility modes for tool calls:

  • Normal mode — prompts for approval (blocking, high friction)
  • Verbose mode (Ctrl+O / --verbose) — full firehose of every detail (too noisy for regular use)

When you configure permissions.allow in settings.json to auto-accept tools, they execute silently. There's no middle ground where you can see what's happening without being blocked.

Proposal

A lightweight, non-blocking notification when a tool call is auto-accepted — something like a brief toast or inline status message:

✓ auto: Edit public/css/tracker.css
✓ auto: Bash(node server.js)
✓ auto: Read data/annotations.json

This would appear in the output stream (or a status area) without pausing execution, similar to how build tools show steps as they run.

Why this matters

  • Learning — helps users build intuition for which tools Claude reaches for and when, especially users still learning the tool ecosystem
  • Trust calibration — you can watch the flow in real time and Ctrl+C if something looks off, without the cost of approving every action
  • Awareness without friction — the whole point of allowlists is speed, but total silence means you lose situational awareness

Current workarounds

  • Toggle verbose mode (Ctrl+O) — works but shows far more detail than needed
  • Don't use allowlists and approve everything manually — defeats the purpose

Suggested behavior

  • Off by default (opt-in via settings or flag, e.g. --show-auto or a notifications.showAutoAccepted setting)
  • Single-line, dimmed/muted styling so it doesn't compete with Claude's actual output
  • Shows tool name + brief context (filename, command) — not full args

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗