Pasted and risky commands

Opsty names what a command will destroy before you press Enter, and notices when a line came from a paste. It only says so: your Enter always goes through.

Commands that cannot be undone

Type or paste one and a sentence under the line says what will be gone. It knows rm -rf, git reset --hard, git push --force, git clean, deleting Docker volumes or pruning, DROP and TRUNCATE, kubectl delete, terraform destroy, and writing straight to a disk with dd or mkfs.

A downloaded script piped into a shell, curl … | sh, gets one too: Runs a downloaded script before you can read it. Make sure you trust the address. Opsty’s own installer has that shape, and gets the same sentence.

Settings ▸ Helpers ▸ Name what a dangerous command loses turns it off. On a server you marked as production, the sentence is a red ribbon; see Production.

When you pasted it

When the line came from a paste rather than your keyboard, the sentence begins You pasted this ·, because an AI or a web page may have written it, and ends Opsty only says so; it does not stop you.

Pasting several commands

Paste a block from a chat, say a comment, $ brew install pnpm, $ pnpm install and $ pnpm dev, and it lands on zsh’s line as it always does, held there by zsh and not run. Opsty offers to walk it: the $ prompts and the comments come off, and each step is listed and read back.

One at a time
Opsty edits the line down to step 1 by sending keys. You press Enter. When a step finishes cleanly the next is offered, with Place; when one fails, the failure card shows and the walk waits, with Place it again. Stop the walk ends it.
Keep it as pasted
Leaves the paste exactly as zsh holds it.

A block with a here-document or an open quote is only ever offered as it is. Settings ▸ Helpers ▸ Pasted commands, one at a time turns the offer off.