Workflows · Documents

Invoices and contracts in,checked fields out.

Drop the week’s scans on a Reference card. An agent in its own isolated worktree reads each one, writes the fields into intake.csv and tracks every document on a task board. “Add a reviewer” puts a different model on the same files with one rule — don’t edit anything — and the author fixes what it finds. Filing waits for your Allow, and a budget card caps the whole run.

An invoice, a contract and a receipt. The reviewer finds one wrong date. Allow the filing when asked.

The agent extracts fields from an invoice, a contract and a receipt; a reviewer on another model finds one wrong date; filing waits for your Allow.

Scans stay on the canvas

The Reference card holds the PDFs; the agent reads them with reference_get — nothing is pasted into a chat.

A second model checks

“Add a reviewer” starts an agent on another harness in the same worktree, told to report and not to edit.

Every document on the board

One task per document, assigned to the agent, moving from To do to Done as the work happens.

A ceiling on spending

The workspace budget stops programmatic prompts when the limit is reached; you raise it if you want more.

Workflows · Documents

From a scan to a filed record

Two agents on two models, a board and a budget.

01
Drop
Scans on the Reference card.
02
Extract
Fields into intake.csv, one task each.
03
Review
A different model compares with the scans.
04
File
Moved into the archive after your OK.
Related scenarios

More in Workflows

Other live scenarios from the same shelf — and a few close relatives.

Browse all 40 scenarios

Let two models read the paperwork

One extracts, one checks, you decide what gets filed.

Download for WindowsWindows 10 / 11 · 64-bit

macOS and Linux are coming later.

The first-run wizard installs an agent CLI, Git and the dictation model for you — or skips each step.