session-end

You can generate a session handoff by running the wrap-up command for your project, which extracts landed work, open tasks, and git commit state from the conversation and writes them to a fixed markdown file.

A cowork session handoff is a durable markdown file capturing what work landed, what remains open, and the repo commit state. You need one when wrapping up a project session to ensure continuity for the next session.

Yes, the session handoff generation optionally refreshes affected writable GitHub repo README.md files to match a canonical documentation structure when substantive changes occurred during the session.

Yes, you can pass a session handoff to a specific teammate by capturing an optional handoff target and author in the handoff file's frontmatter, or skip prompts entirely by using command flags.

Starting a new project session after a previous handoff is supported by a companion workflow that reads the canonical handoff file, which is overwritten at a fixed project path each session to ensure reliable retrieval.

Automated session wrap-up writes to a fixed project path and overwrites the previous handoff each session, meaning it does not maintain a running history of past handoffs and relies solely on the current conversation for extraction.