handoff

To transfer agent context, you summarize ongoing work into a safe handoff artifact that captures verified goals, current status, dead-end warnings, and next actions. This allows the next code agent or restarted session to continue seamlessly without guesswork.

Recovering from context pollution involves distilling only validated facts and recording dead ends while excluding outdated assumptions. This process creates a clean transfer note that preserves continuity and prevents polluted histories from corrupting the next agent.

You summarize work by generating a handoff artifact with unique file naming that includes verified facts, key files, and next actions. This structure ensures agent continuity is preserved safely without leaking sensitive secrets into the transfer note.

A work summary for a restarted development session must include the verified goal, current status, next step, critical files, and dead ends to avoid. This concise handoff note tells the next agent what was tried and where to look first.

Yes, you can maintain continuity across long-running development workflows by creating a concise transfer note. This artifact captures the verified state, risks, and next actions so another agent can continue the active work safely.

You should avoid using a handoff artifact for session recovery when your conversation history is clean and concise. It is specifically designed for polluted histories, context resets, and long-running threads that need distilled recovery rather than simple continuations.