How it works · get info
Ora · how it works · no jargon

One request.
Careful, checkable steps.

Ora uses your computer the way you would: it looks at the screen, picks the next move, plans and checks — and stops at you before anything that can't be undone.

One run, drawn out

From your words to the receipt.

1 · It looks
The screen

Ora reads the screen the way you do — which windows are open, which buttons, boxes and links they hold, and what the text says.

2 · It picks
Compass-1 · on this PC

Our own small model ranks the things it could act on and picks one — in about 0.07 s on a laptop graphics card. When it isn't sure enough, it abstains.

3 · It checks
The bigger model

A bigger model takes the calls Compass-1 passes up, plans the steps toward your words, and re-checks each one against what is actually on screen.

Every risky step stops here
!
Upload essay-final.docx (48 KB) to the class portal?You see the exact file and destination before it goes. Deny has focus — nothing approves by accident.
DenyFor this sessionApprove once
It acts · the receipt is saved

Only after your answer does the step run — and before Ora changes any file it records how to put it back. Sends, uploads and submits leave a receipt that names what went where, and whether the other side confirmed it.

The same run, in words

Five habits, every run.

  • It looks before it touches.The screen is re-read at each step. A page that changed since the last look is planned fresh, not replayed from memory.
  • It picks one thing, or abstains.Compass-1 was right on 96.8% of 1,058 decisions across 59 sites and apps it had never seen — and every call it was sure enough to take alone was right. The unsure ones went up to the bigger model.
  • Nothing risky passes on a guess.Sending, uploading, payments, installs, account security and deletes ask every time, in every mode. Text on a page can never grant a permission.
  • It leaves a trail.History lists what you asked, what changed, and how it ended. A portal chore isn't "done" until the portal confirms it, and the receipt says so.
  • Undo is one click.Files are recorded before they're changed, so the Undo button puts them back. What it can't undo — a sent message, a click — is exactly what asks first.
When it can't, it asks

Stuck means parked, not guessed.

When a run hits something it can't decide — a sign-in, a page it isn't allowed to touch — it stops on "Waiting for you" and asks in its chat.

  • Sign-ins are yours.Ora never types your password. A portal run parks, you sign in inside its browser, and it continues.
  • Some doors stay closed.Admin prompts, "prove you are human" checks, face and fingerprint screens, and protected media are refused rather than worked around.
  • A missed schedule is honest.A run whose time came while Ora was closed is recorded as missed — never replayed silently as if it were on time.
Task · school portal
Waiting for you

Ora is waiting for you to continue in the portal — the sign-in page is up. Sign in, then the run goes on.

ParksA waiting task does nothing until you answer — nothing goes on behind your back.
StopThe square button ends it. Stop everything on the task bar halts all running work at once.
UndoAfterwards, Undo restores every file the task snapshotted before changing.
Keep reading

Where to look next.

The model that picks the next click is on Compass-1, with the honest limits. What always asks — and what never can — is on Safety. What leaves this PC, row by row, is on Privacy.