Delegated work
The job runner, token budgets counted off the stream, partial returns, overnight parking, and what a job is allowed to do on your behalf.
Otto is one conversation on one thread. Anything slow you ask for is paid for in silence: you ask a question that deserves forty minutes of work, and either you wait forty minutes or Otto gives you a five-minute answer. The job runner is the third option.
What delegate does
A job is a detached headless session with its own scratch directory, tool allowlist, wall-clock cap and token budget. Creating one returns a job id in under a second; the finished result posts back through the loopback webhook as a normal event.
You ask, you get an acknowledgement now, and the answer arrives when it is ready.
Lifecycle
queued, running, parked, done, failed, killed. Terminal states are
terminal; finished jobs are retained for a window and then pruned.
Budgets are counted, not estimated
Token usage is tallied off the job's own output stream as it runs, which means the budget can be enforced mid-run rather than discovered afterwards. A job that hits its budget or its wall clock is killed.
A killed job still returns what it got. Progress is written incrementally, so the answer is "three of five vendors done, here they are" rather than nothing. That is the difference between a budget and a cliff.
Overnight parking
A job tagged overnight sits unstarted until quiet hours, and the scheduler only
launches what fits before your wake time. The Mac's idle window becomes real
capacity, and nothing is half-finished at breakfast because it started at 07:40.
Failures land quietly
A job that broke at 03:00 is never worth a 03:00 notification. Failures are sent at normal priority and are subject to the ordinary holds.