Close a session
Save the accepted facts and a precise next step before ending the conversation.
Goal and prerequisites
Leave the project ready for a different session or agent. You need the actual work results, validation evidence and a chance to review proposed record changes.
1. Request a handoff draft
Review this session's work against the files we changed.
Propose an updated handoff with completed work, validation performed,
remaining blockers, risks and one exact next action.
Propose memory changes only for durable decisions I explicitly approved.
Keep unresolved proposals separate. Show the diff before saving.
2. Check the evidence
Verify that “complete” refers to finished work and that tests marked passed were actually run. Preserve failures and skipped checks. Keep proposed decisions provisional and avoid storing a whole conversation as memory.
3. Authorize the update
Approve the specific changes you accept, then ask the agent to save them. Refresh the handoff rather than endlessly appending old status. Update a change history when your project uses one.
4. Inspect what was saved
Open the changed files. Confirm the next action names a concrete task, the current blocker is visible and any referenced output exists. Ensure personal data or secrets were not copied into a reusable context note.
Expected result and recovery
The saved handoff should let a new session tell you where work stands without relying on this chat. If the agent says it saved something but no file changed, resolve that before closing. Use resume work to verify continuity.
Versions, sources & verification
Reviewed against: Starter Kit 1.2.0 / Community 1.0.0; KOS Pro 1.1.0 / Core 1.0.0.
Agent runtime behavior has not been tested for this article. Run the verification steps with your selected agent.
- Release source on GitHub ↗
- KOS Pro 1.1.0 supplied release notes, installer reference and scripts
Source review confirms the documented interface. It does not replace testing your vault, tools, or recovery copy.