Delegate a task
- Hand off a bounded taskA human gives one clear slice of work.
- Subagent works and reportsThe result returns to the parent conversation.
- Choose the next handoffAnother focused task can go to a subagent.
An agent that keeps a notebook. It writes every step down before it moves on, so crashes, restarts and long waits never make it forget.
Scroll to follow Pi| In the story | In Pi Durable |
|---|---|
| The golden notebook | SQLite storage, with checkpoints throughout each task |
| Slip stamped #job-42 | requestId: retries find the original submission instead of admitting it again |
| Storm, then the ghost | Process crash, then Harness.open on the same file |
| "Not safe to repeat" | A tool without replay: "safe" |
| Little mint helpers | Subagents: conversations owned by a task |
| Sleeping through day and night | A task with status: "waiting", answer kept with api.memo |
| Hammer vanishes | Live config or extension swap, such as readOnly |
| Two Pis | fork(entryId) |
| The parrot | A cheap judge model screening events (Jev) |
Give Pi a responsibility: keep incoming work moving, and bring you the decisions it cannot own.
Like a reliable teammate on your side of the court: follows the agreed play, moves work forward, and passes the ball back when it is your call.
A durable, proactive role can still use subagents for scoped jobs; the two patterns work together.
Choose an example to trace the work.
Drop repeats and irrelevant updates.
Recover context and unfinished work.
Run checks and independent reviews.
Fix, ask or suggest.
Make a bounded change, then verify.
Share the outcome. Wait for new information.
Signals are checked before work begins; saved cases continue with fresh evidence, bounded actions or a human decision.
Possible extensions: support inbox · incident queue · review queue. Each needs configured inputs, tools and permissions.
Illustrative workflow inspired by an in-progress PR role agent; broader queues are potential extensions.
Get my Pi Durable agents skill ↗