Ora · for Windows · private beta
You decide
You decide
what Ora may do.
The approval rules are one system. No mode, standing permission, or mission card can turn a hard stop into a silent action.
The hard stops.
These ask every time, in every mode — nothing pre-approves them.
- Payments and shell commands.Anything that spends money or runs a command on your PC.
- Uploads.A file leaving your PC — the card names the exact file and where it's going.
- Sending.Messages, posts, and form submits — the card names the exact recipient.
- Installing software.New software always asks.
- Account security.Password changes, two-factor settings, recovery options — every time, with no memory.
- Credential material.Opening a file that holds passwords or keys.
- Deletes that haven't been judged safe.And anything in a protected place is refused outright — not asked, refused.
Three choices — and one that's often missing.
For the two ordinary-but-irreversible kinds of action — sending and uploading — the card shows three buttons, not two.
- Approve for this session is narrow on purpose.It covers only repeats of the same kind of action to the same destination — a send to one person never covers anyone else. It lives in memory only, dies with the run (within the hour at the latest), and sits in the task bar with a Revoke button.
- Sometimes it's never offered.Payments, account security, a generated skill's first run, approvals inside a saved workflow, anything driven by text on a page, in an email, or from another bot — and every other hard stop — always ask in full, whatever was approved before.
- Focus starts on Deny.No single keypress approves anything.
Send "Running late, starting at 9:30" to Priya in Teams?You see the exact message before anything is sent.
DenyFor this sessionApprove once
DenyNothing is sent. Ora tells you it stopped.
Approve onceJust this message. The next one asks in full.
This sessionThe same kind of action to the same destination, until the run ends.
How much a bot does alone.
Each bot has its own mode. A mode only changes how chatty Ora is about ordinary actions — the hard stops ask in all three.
The default
Asks before anything risky or new.
Per bot
Runs the mission on its own — and still asks for every hard stop.
Time-boxed
Asks almost nothing — for a few hours only: 4 by default, 24 at most, per bot, then it steps itself back down. Even here a first action on a new site asks once, and every hard stop still asks.
Undo covers files — not messages.
- One click puts files back.Tidy-ups, reports, rebuilt sites and Build edits restore to exactly where they were — and keep edits you made afterwards.
- What undo cannot reverse.A message already sent, a form already submitted, a click already made. That is exactly why those ask first.
- Your hands always win.Move your mouse or touch the keyboard while a bot is driving the screen and it pauses instantly — no confirmation, no delay.
Protected places.
- Refused, not asked.System folders, source-code repositories including .git, and credential stores — deleting there is denied outright.
- Too big to touch.A drive root, your whole user folder, C:\Users and your application data are refused as tidy targets — pick the subfolder you mean.
- A delete it can't identify.Asks, like everything else it isn't sure about.