You can now choose which interactive shell commands launch automatically, which need confirmation, and which are blocked. Quiet sessions can alert Pi even if they have printed nothing, and each alert includes a short redacted excerpt showing what needs attention. Timer and token-counter updates no longer repeat the same alert; after you answer, the next question can still notify Pi. File-watch requests also reject conflicting commands, preventing an unintended launch.
Highlights
- Choose whether interactive shell launches run, ask for confirmation, or are blocked.
- Get alerted when a quiet terminal needs attention, even without new output.
- Understand alerts from a redacted screen excerpt without repeated notifications from changing counters.
Full changelog
Highlights
- Decide which interactive shell commands can launch automatically, which need confirmation, and which are blocked.
- Get notified when a quiet terminal needs attention, even if it has not printed anything.
- See a short redacted excerpt with each notification and avoid repeated alerts from changing timers or counters.
Added
- Add an optional global
launchPolicyfor exact commands launched throughinteractive_shelland/spawn. Rules can allow, deny, or ask for confirmation; unmatched commands ask. The policy is off unless configured and does not affect existing sessions (#71). - Check a quiet session once after an inactivity period, including sessions with no output. The check can notify Pi but cannot type into the terminal. Configure the delay with
quietIntervalMs(default 2 seconds) (#75). - Include a short redacted screen excerpt in semantic notifications, so Pi can see what needs attention without querying the session (#75).
Changed
- Stop repeating attention notifications when only timers or token counters change. After input is sent, a follow-up question can notify Pi again even if it asks for the same kind of response.
Fixed
- Keep configured semantic actions available when only elapsed time changes on an otherwise unchanged screen.
- Reject file-watch requests that also specify a command or spawn. File watches use only their generated watcher command, and rejected requests cannot create a worktree (#71).