Batches

One task, many inputs, one ceiling over the whole thing.

opsen batch invoice-extract inputs.txt --cap 5.00 --width 5
ls *.pdf | opsen batch invoice-extract -

How it runs

One run per line, --width at a time. Each run receives its line as OPSEN_INPUT, so the agent does not need to know it is part of a batch.

The cap is on the batch

--cap bounds the whole thing, not each run. A hundred inputs at the task's own per-run cap is a multiplication nobody does in their head while typing, and it is where the expensive surprises in this category come from. The task's own cap still applies to each individual run.

Failures

One failing input does not stop the batch. The batch page shows which succeeded, which failed, and what the whole thing cost — so a re-run can cover only what needs it.