Agent handoffs

Use Worktable when an agent needs to leave work in a form someone else can pick up like another agent, another session, or you in two weeks.

What a good handoff contains

• The objective.
• Current status.
• Decisions made, and why.
• Open questions.
• Next actions.
• Links to the relevant docs, records, HTML docs, and conversations in the Space.

One living doc

Ask agents to update the same handoff doc rather than leaving a new note each session. A trail of “status update” docs is where continuity goes to die. Updating in place is what docs are built for: patch the sections that changed, and version history keeps every previous state reachable.

Handing off across agents

Nothing about a handoff is agent-specific. A second agent or a later session orients the same way: workspace state, search, the Space’s content, and open annotations. If the handoff doc is honest, the next session starts where the last one stopped instead of re-deriving it.

Leave your own instructions as annotations on the handoff doc. “Prioritize the migration question first” lands better anchored to the open-questions section than repeated in every new chat.

Use a Space thread when the handoff needs a durable conversation with a connected participant. Keep the decisions and current state in the living doc: threads preserve discussion, while the doc remains the artifact another person or agent can scan and continue.