forward

AI session handoff is automated by generating a structured context file in the vault and entering plan mode. This workflow captures progress and defines next steps to ensure continuity without losing memory between interactions.

Plan mode for workflow handoff is a process that composes a follow-up plan for the next AI session. It uses tooling to capture pending items, align with stakeholders, and prompt for final approval before wrapping up the current work.

You need to create a handoff context file when signaling to wrap up or continue in the next session. Using triggers like 'forward' or 'handoff' instructs the AI assistant to preserve memory and progress before ending the interaction.

You can skip plan approval when wrapping up an AI session by using ASAP or --only modes. These modes bypass the final approval prompt while still generating the required handoff context file in the vault.

The vault handoff workflow requires no external dependencies. It operates independently by writing context files directly to the local vault directory at ~/.oracle/ψ/inbox/handoff and using built-in plan mode tooling.

The best way to ensure traceability across AI sessions is to generate a structured handoff document. This preserves memory and progress in the vault while entering plan mode to define and approve next steps for the upcoming interaction.