@adeildo/pi-ask-permission

Out of the box, pi runs every command the model writes. With this package, pi asks you first. You answer yes, always yes or no, and you can leave a note on any answer. The model reads the note, so a no can tell it what to do instead. In judge mode, a small model answers the routine calls for you.

Answering

The dialog opens before the command runs.

• yes runs it once.
• always yes runs it, and stops asking for the same command in this session, this project or everywhere.
• no blocks it. Press Tab first to add a note, like "use pnpm instead", and the model reads it.

Reads never ask, and for an edit you see the diff before you answer.

Modes

Alt+M switches between modes, and the status bar shows the current one.

Mode	What runs without asking
manual	Reads, and what you marked always yes. The default
edits	The same, plus file edits and writes
judge	The same as edits, and a model answers the rest
full	Everything

A call outside your project asks you in every mode, full included. Alt+W lets those through for the rest of the session.

Let a model decide

In judge mode, a small model reads each call and lets through the ones it is sure about. You only see the calls it doubts.

1. Run /login typesafe to use Jev, the default judge.
2. Switch to judge with Alt+M, and turn on Dry run in Alt+S. The judge writes its verdict on each call, but you still decide.
3. Pick a policy, such as Standard development.
4. Once you agree with the judge for a few sessions, turn Dry run off.

Every call shows who let it run and why, like judge approved 97% sure, risk 0.12.

Learn more

• How it works: always yes in detail, folders outside the project, MCP servers, how the judge decides, and the limits.
• Reference: every setting, the exact order in which a call is decided, and the events other extensions can listen to.