Checkpoint a session

Automatic synchronization

Agent hooks and plugins can update Handshake after a completed turn. The daemon also imports supported native sessions when it starts.

Run a pull when you want to import native sessions immediately:

handshake pull

Automatic synchronization can store the conversation and session metadata. A manual checkpoint can also supply a clear summary and settled decisions.

Create a manual checkpoint

Describe the current state

Record completed work, test results, active problems, and the next actions.

Record settled decisions

List decisions that the receiving agent must not change without new evidence.

Request the checkpoint

Enter:

checkpoint this session

You can include the title, summary, and decisions in the request.

Check the result

Make sure that the agent reports the stored title and message count.

MCP parameters

The agent calls checkpoint_session.

Parameter	Requirement	Function
`session_id`	Required	Identifies the native agent session.
`agent`	Required	Identifies Claude Code, Codex, Hermes, or OpenCode.
`title`	Optional	Replaces the native session title.
`summary`	Recommended	Gives the current state and ordered next actions.
`decisions`	Optional	Gives one settled decision per line.

Cursor uses its installed hook to send completed session data. The checkpoint_session tool does not accept cursor as its agent value.

Automatic synchronization