Agents that ask
about the right things.
Choose how much an agent may do on its own. AigoPilot asks about deleting, reaching outside the project and installing, and stops asking about things that cannot hurt.
The two usual choices are both bad: approve every single command, or switch approvals off and hope for the best. AigoPilot sits between them. It reads each command to see what it would really touch, asks about the ones that matter and remembers your answer.
Fully safe asks about everything. Balanced, the default, asks only about dangerous actions such as deleting outside the project. Full access asks about nothing. Custom gives you a switch for each group of permissions. Any mode other than fully safe shows a notice listing exactly what you granted.
Deleting inside the project and deleting outside it are separate switches. Installing Python packages outside the project's own environment, or global Node packages, gets a question. Checking whether a path exists never does.
Every shell command is read to see where it really reaches: through pipes, scripts, nested shells, .NET calls and redirects. A delete hidden three levels down is still treated as a delete.
A dialog shows the exact plan before anything is written. When you confirm, it adds the hooks (and, if you like, the status line) to Claude Code's settings file, leaves a copy of the original file beside it, and tests them. Your own hooks are left untouched. With the hooks in place, a session waiting for permission in VS Code or a terminal is known for certain.
An optional hook blocks destructive commands in sessions you run in a terminal or an editor, even when those sessions run with approvals switched off. Whether to install it is up to you.
Something you allowed is not asked again in that session, even after a resume or a restart of the engine. Destructive actions are the exception. Those are asked every time.
A question you keep seeing offers “allow similar” and “deny similar”, and spells out exactly what similar covers. The rules go into the project's own settings file, are listed in Settings and come out with one click. Nothing that deletes, reaches outside the project, installs or cannot be undone is ever offered as a standing rule.
Make a folder outside the project part of it, and the agent may work there as it does inside. Deleting that folder itself is always asked.
No part of AigoPilot, on the desktop or on the phone, starts a session in the CLI's own auto-approve or bypass modes. Sessions start in manual or plan mode, and AigoPilot answers the permission requests according to the mode you picked.
AigoPilot runs only the official CLIs, with your own subscriptions. It never reads, stores or reuses a login, token or cookie, and it never calls a private endpoint. Signing in always happens in the CLI's own window, and tests check that no sign-in secret ends up in AigoPilot's data.
Sessions start without the provider's API key variables unless you choose to pay with a key, so a subscription session cannot quietly bill an API account. Every session shows who pays for it, and a change in the middle of a session raises a critical alert.
Paid API keys live in Windows Credential Manager or the macOS Keychain, never in a data file or a log. Anything that looks like a key is masked on screen, and sessions never see AigoPilot's own keys.
Sessions, settings and history sit in a local file, and there is no AigoPilot cloud account. Connections between your own computers and your phone are encrypted: pairing uses SPAKE2, and the line after it uses Noise. A device you have not paired gets no answer at all.
Paths with spaces or non-Latin letters work, .cmd launchers work, and no console window flashes up. When a session ends, every program it started is closed with it.
Before AigoPilot changes the structure of its own database during an update, it makes a copy of it.
Start one session with tighter permissions than the rest, shown in its own colour. Today the mode is set for each computer.
That depends on the mode. In the balanced mode AigoPilot still asks before anything that deletes outside the project, installs globally or cannot be undone, and it reads each command to see what it really touches. The fully safe mode, which asks about everything, is always one click away.
No. Sessions start in manual or plan mode, and AigoPilot answers the permission requests according to the mode you chose.
No. Logins stay with the official CLIs. AigoPilot never reads, stores or reuses them.
Only for devices you paired. An agent on another computer, and the studio once you pair a phone, accept connections from paired devices. Anything else gets no answer.
