COVER STORY
Hand it off so someone can take over
Persistence keeps work running. A handoff lets someone accept the result.
An always-on computer is not yet a dependable colleague
This week’s personal agents share a move: taking AI out of a single conversation and giving it a computer that stays online. After you leave, it can organize files, run programs and wake for a scheduled task. Founder Park surveys products living in apps, messages and email, or presented as teams of named bots. Underneath, their foundations increasingly resemble one another: a cloud computer, persistent memory and connections to other tools. 12
That explains the appeal. We used to bring a question to a chat box; now we can leave a piece of work behind. But the standard changes with the arrangement. One reply can be inspected in place. After an overnight assignment, we need to know where the work stands, which results are dependable and who takes over next.
Persistence answers who keeps running. Delivery answers who can accept the result. The second question matters more to me. If eight hours of autonomous activity leave me checking everything from scratch, execution has simply turned into supervision.
Start with a task that can end
Founder Park points to cancelling subscriptions as a concrete entry point: there is an object and an observable outcome. Compared with “manage my life,” it is easier to check whether a subscription was cancelled, a confirmation arrived and the next bill stopped. One completed, bounded task can give a person a reason to delegate again.
The community guide to Dots and Jev proposes another division: a fast decision layer selects, scores and routes, while a stronger model executes. A Grok Bot introduction offers scheduled digests, content reuse and support triage as examples. These make ongoing work tangible. But the cost of a task includes retries, escalation, verification and human time—not just an individual model call. 02 04
For this newsletter, a more useful assignment than “make an issue tonight” is: include every save in the period, group related material, attach sources to claims and deliver a draft readable on a phone. The first asks the agent to guess what good means. The second lets us check coverage, evidence and usability. An explicit finish condition reduces the clarifications needed later.
01 / THE HANDOFF
Turn “done” into a usable handoff
Editorial example: a newsletter-draft handoff, not a run log.
- 01Assignment
- Turn public saves into a readable draft
This assignment ends at a preview; publication is a separate decision.
- 02Progress & evidence
- Prose, source references, page captures
Each result points back to an inspectable artifact.
- 03Unresolved
- Two return claims lack complete ledgers
Keep uncertainty visible rather than marking it verified.
- 04Next step & owner
- Editor reviews and decides what follows
The next person can continue without rereading the whole chat.
Inspect the deliverable. Conversation history provides clues, not a substitute for these artifacts.
Before adding a team, complete one handoff
The saved Grok Bot team template separates a chief of staff, feature owners and verifiers. Its useful principle is that the producer cannot approve work merely by declaring it done. Verification should point to inspectable artifacts: a reproduction, test output, screenshots or a run record. The public image shows one template page, not evidence that an entire organizational system has been validated. 06
Still, the division exposes an important cost: multiple agents create more handoffs. A collector says the links are ready, a writer says the draft is finished, and a designer says the build passes. Those three statements may still fail to produce a good issue. Someone must connect the acceptance conditions and identify the missing evidence.
The Feishu integration tutorial lowers the barrier to putting these roles in a group chat. After connecting them, messages need to reference the same task: who owns it, where the output lives, which decisions belong to the editor. If that information is scattered across conversations, a person soon becomes every agent’s manual router. 19
After a disconnect, “do it again” is not a sufficient recovery policy
The Pi Durable Objects tutorial provides a lower-level example. It persists conversations, tasks and request receipts, checks repeated requests against previous work, and resumes the original retrieval subtask. The retrieval agent excludes previous retrieval outputs, reducing the risk of a summary becoming evidence for another summary. 30
Two kinds of recovery matter here: restarting computation and repeating an external action. An analysis can often run again; an email already sent should not be sent again just because its receipt was lost. The tutorial notes that alarms can fire repeatedly and external calls are not inherently exactly-once. A dependable system needs an “outcome unknown” state, followed by verification before retry.
02 / RECOVERY
On return, identify the state first
An editorial recovery model informed by the Pi tutorial, not a guarantee for every external service.
Confirmed complete
A verifiable result exists
Return the existing output; do not repeat it.Not yet executed
The record shows pending work
Continue from the unfinished step.Outcome unknown
The request left; the receipt did not arrive
Check external state before retrying.Recovery does not mean repeating an email, order or write. [30]
That is what I want from an always-on agent: less reporting that it has been busy, more certainty about where someone can continue. AIGC Weekly #192 brings personal agents, protocols and product updates together as further reading. Its saved newsletter cache may be incomplete, so it is not used here to establish protocol details. 15
AIRING’S DESK / FOUR PANELS
Before heading home
From assigning the work to making it possible to take over.
Read the comic transcript
- At dusk, Airing gives the work to Moflow: “I can leave early this time.”
- At the door, Airing turns back: “Which part is actually finished?”
- They organize progress and evidence. Moflow: “Write down what is blocked too.”
- They finally leave. Airing: “Tomorrow, we can pick up from here.”
AI-generated using the updated character references. Read top-left, top-right, bottom-left, bottom-right. Chinese dialogue translated in the transcript.






