About This Ora

Ora

For Windows · private beta

An assistant that uses your computer the way you would — and asks before anything that can't be undone.

What's new, dated below. Ora began as an assistant that answers; this is what it can do now that it couldn't before.

Release notes · private beta

2026-10-05

For the private beta

A chat can now be a worker. A bot is a chat with its own settings and its own memory of what you've allowed it. Its mission card states the job in plain words: the goal, what counts as done, the places it may touch, the schedule and the budget.
Work keeps going when you look away. A mission runs on your schedule while Ora is open; the task bar shows what's running and what's waiting on you. A bot that gets stuck stops and asks instead of guessing.
Hand it a plan and a photo. Give a bot a requirements document and photos of a whiteboard or sketch and it proposes a milestone plan for your approval first. Your documents and photos are material to review, never instructions.
A big job can get a team. A bot can share its work with sub-bots it creates — you see the whole team, can open any member's chat, and no sub-bot ever has more power than its lead.
Coding agents are bots too. A bot's chat can be backed by a command-line coding agent on your PC. From your side it's just another bot: it works in its own folder, and every file change and command appears as a question for you.

Portal chores, with a paper trail. A bot can run a school or work portal chore: each download is checked and recorded, it asks once before uploading and submitting, and the job only counts as done when the portal confirms it. Every attempt leaves a receipt beside the files.
Research with citations that check out. Every claim in a research report carries a citation verified against a page Ora actually opened; conflicting numbers are listed rather than quietly resolved. The whole task can be undone.
Turn a website into an editable project. Point Ora at a site it captured — or a public web address — and it rebuilds the page as a small local project you can open and edit. Nothing from the page is run, nothing is published for you, and the task can be undone.

A digest of your inbox. After you connect your mailbox, Ora posts a short digest: what's urgent, what needs a reply, what's informational. Card numbers, passwords and one-time codes are masked before anything is summarised, and mail that tries to give Ora instructions is flagged, never drafted.
Replies start as drafts, not sends. A newly connected mailbox is draft-only — a person presses send. Even with sending turned on, Ora asks before every message and names the exact recipient.

Ora can drive Blender. After a one-click add-on install, Ora can build a scene, add materials, render and export — inside the project folder you choose. Custom commands ask every time, and every change can be undone.

Some things always ask, whatever the mode. Spending money, running commands, uploading files, installing software, sending messages or submitting forms, changing account-security settings, reading files that hold passwords, and unsafe deletes. Deleting in a protected place — system folders, code repositories, password stores — is refused outright.
Every ask has three choices. Deny, Approve once, or Approve for this session. A session approval only repeats the same kind of action to the same destination, lives only in memory, ends with the run — and every active one is listed in the task bar with a Revoke button.
Some asks can never be pre-approved. Payments, installs, deletes, anything touching passwords or account security, the first run of a generated skill, approvals inside a saved workflow, and anything that looks like it was asked for by text on the screen rather than by you.
Mistakes can be undone. Undo puts files back the way they were — tidy-ups, research and site-rebuild outputs, and coding-agent edits. It doesn't reverse clicks or messages that already left, which is why those ask first.