Nothing your operator does is a black box
Every task, whether it ran in front of you or overnight, produces a step-by-step account: what was asked, what your operator did, which model did it, what it cost, and every decision you made along the way. Like a receipt from a purchase, it’s produced automatically and it’s specific, and you only open it when you want to check something.
If you need to answer “why did this email go out” or “where did this number come from,” the task’s receipt has the answer.
What a receipt shows
Open a task’s receipt and you’ll see it laid out in order, for example:
Task: “Compare our shipping cost against 3 competitors.” 09:14: Checked competitor sites A, B and C for current shipping rates. 09:19: Compared against our published rates, found we’re 12% higher on orders under $50. 09:20: Drafted a one-paragraph summary. Model: your connected key. Cost: usage for 4 calls. 09:21: Delivered to you in Slack.
For tasks that involved an approval, like sending an email or booking something, the receipt also shows what was proposed, what you decided, and exactly what ran immediately after; see approvals for how that step works.
The model and the cost, in plain view
A receipt always names the model that did the work and what that usage cost, whether it ran on a key you brought or on OperatorNest’s own access. See model choice and bring your own key. You can see whether a recurring brief was expensive to produce, and which model has handled a particular kind of task well before.
Receipts for recurring and background work
A recurring task keeps a separate receipt for every run, so a weekly competitor brief has a full history you can scroll back through. A background task that ran for two hours while you were away leaves the same level of detail as one that finished in thirty seconds in front of you. You can check what happened while you weren’t looking.
Receipts need no setup
Every task generates a receipt automatically, one click from the task itself. You don’t choose what gets recorded, because a record with gaps would defeat the purpose.
You can export a receipt as a plain record to keep a copy outside OperatorNest, document a decision for a colleague, or check a task’s cost against a budget. Exporting doesn’t change the original, and it gives no one access to your operator or its memory, only the record of that one task.
Receipts across a whole week of work
Looking back over a week, you can see every recurring brief that ran, every approval you made, which model handled most of the work and what it cost in total, and any task that stalled or needed your input. You’re reading the record itself, not a summary someone hands you at the end of the week.