context-handoff

To preserve context for a different AI agent, generate a compact handoff document from the current conversation. This document references existing PRDs, plans, ADRs, issues, and commits by file path instead of duplicating content, ensuring seamless continuity.

Redacting secrets and PII before transferring context is handled mandatorily during handoff document generation. The process automatically strips sensitive information to prevent leakage, ensuring the compact context file is safe to pass to the next model.

Yes, you can generate a portable handoff document that prescribes the next steps for the successor agent. It explicitly tells the next AI which skills to invoke, which specific files to read, and which decisions are already settled.

The handoff document saves directly to the OS temporary directory, not the workspace. This prevents workspace clutter while providing a reliable file path for the next session or model to retrieve the compact context.

The best way to transfer conversation context between models is using a prescriptive handoff document. It compacts the current session, references existing plans by path, redacts sensitive data, and suggests which skills the successor model should invoke next.

You need a handoff document when a session ends and the next agent or model should continue the work. It compacts the conversation into a portable reference that guides the successor on settled decisions, required files, and next steps.