Evidence capture and runs

Capture connects observations from supported agent sessions to the change a person will review. Nothing in capture adds model (AI) calls.

Where it appears

Capture is turned on per company. Where it is on, the app shows an Agent work area for your unlinked runs and for sharing setup, and tasks show their linked agent work in an Agent work section. Where it is not, no capture entry appears; contact us to have it enabled.

On a task, the newest run is listed first with the time Orneos first received it (not when the agent started), and it opens with the agent’s captured reply for that turn, shown as the agent’s own unchecked statement, before the detailed activity. A captured reply may describe progress, a blocker or a result; it does not mean the task is complete. Missing capture stays visible rather than being treated as proof that nothing went wrong.

Setting up a computer

Setting up a computer requires an admin to allow sharing in the company policy, a setup created for one team, and a capture-only personal token. New setups also include check results from the Orneos runner for checks the owner configures, plus counts of shell calls; the setup screen lists exactly what is covered before you confirm. These results are local process evidence from the owner’s computer, not confirmation by Orneos. Setups created earlier keep their original consent, and their runs never gain check details. Secrets are pasted when the installer asks for them, never typed on the command line, and the installer uses a saved token only with the one server it was set up for.

The sharing area starts with a Connect Claude guide that lists each part of readiness separately: Claude reading the task, the company policy, a setup used on a computer, what only that computer can show, captures received, task linking and check results. It confirms only what Orneos’s server has reported and gives no overall “ready” verdict. Capture still needs a one-time installation in each project folder on each computer.

Owners can attach runs from their tray. In the founder workflow, an eligible run can also be associated automatically with the task identified for that session after setup. Ambiguous runs remain in the owner’s tray; this is not a claim of wider rollout.

Reviewing captured evidence against agreed requirements is still work in progress. The assisted pilot prepares selected material manually with you.