STOP, consent and revocation: staying in control of an AI that acts
On-device consent, the STOP button, revoking an AI or a computer: what each SteerLatch control blocks, and what it does not.
An AI that acts on a computer must be easy to stop. SteerLatch offers several complementary controls. Here is what each one actually does.
1. Consent, on the computer itself
The first time an AI wants to act, a window opens on the computer concerned, not only in the browser. You choose what you allow: files, terminal, screen, mouse and keyboard. The choice stays valid until you withdraw it.
2. STOP: block everything at once
STOP, from your account or from the SteerLatch menu bar icon on a Mac, refuses every new AI action on that computer, including reads and screenshots, and interrupts actions in progress, including terminal commands SteerLatch started. It never lifts itself.
3. Revoking an AI or a computer
Revoking an AI refuses its next calls. Revoking a computer stops it from receiving any request.
Limits to keep in mind
- Revocation blocks next calls; STOP also interrupts what is in progress. An operation already under way may still complete, and a program a command started separately may keep running.
- Nothing automatically undoes changes already made.
- The terminal runs commands with your rights: it is not a sandbox. Start with a test folder.
- SteerLatch has no dedicated file-deletion tool, but once you allow the terminal, a command can delete or change files within your account's rights.
MCP lets each tool declare whether it is read-only or can modify data. Your assistant may use this to ask for confirmation, according to its own rules.