session-handoff

To preserve session state when approaching context limits, save your dataset details, pipeline progress, and external resource IDs to a single YAML handoff file at working/session_state.yaml. This captures critical execution data so the next session can resume seamlessly without losing work.

The best way to resume a multi-phase pipeline after a session restart is to use a YAML state file containing explicit resume instructions and local file inventory. Loading this handoff document provides the exact restart template needed to pick up the workflow seamlessly.

Session handoff with Google Workspace resources works by tracking external resource IDs and their URLs within the YAML state file. Capturing these identifiers ensures that Google Docs, Slides, and Drive links remain accessible and correctly mapped when the workflow resumes.

Yes, you need to write your workflow progress to the exact file path working/session_state.yaml. Saving to this specific location after major milestones or external resource creation ensures the handoff data is consistently found for the next session.

You should save your session state after creating external resources or completing major pipeline milestones to avoid losing work. Capturing details like auth state and blockers at these critical points ensures no progress is lost when a session nears context limits.

A YAML handoff file should capture dataset details, tasks, pipeline progress, external resource IDs with URLs, local file inventory, auth state, blockers, and explicit resume instructions. This complete state preservation enables seamless resumption of external-resource workflows.