Confirmations
A command classified as destructive (see the list in Scope and rules) is never run by a CLI machine without your explicit approval, whatever its scope, even with "Any command", whether it comes from konsolity run, a snippet, Claude Code through konsolity mcp or the Claude connector through konsolity serve.
What the machine shows
$ konsolity run db-01 -- "mysql -e 'DROP TABLE sessions_old'"
Destructive command: confirmation requested in the Konsolity app.
https://app.konsolity.com/cli/confirm/9f3c2a71
Waiting (5 min at most)...
The CLI waits for the answer. Only an approval runs the command, once; running it again creates a new request.
Answer in the app
The request shows in the Konsolity app (computer, phone, tablet): name of the machine, host, exact command and reason for the confirmation. Two buttons:
- Allow once: the command runs. The app first asks for Face ID, Touch ID or the device passcode.
- Refuse: the command does not run.
Answer on the console
Open the https://app.konsolity.com/cli/confirm/<id> link received by email or shown by the machine. If your console session is more than 15 minutes old, it asks for the second factor (TOTP or passkey) before allowing.
Timeout
Without an answer within 5 minutes, the request expires and the command does not run. The CLI says so and returns. A refusal or an expiry is never retried automatically.
Alerts
Each request sends an email, an app notification and, if you linked it in Security › Telegram alerts, a Telegram message, with the link to the confirmation page.
Log
The request, your decision (allowed or refused) and the run that follows are written to the command log. The server also refuses to record the start of a destructive command without an approved confirmation: a modified CLI cannot skip the step.