session-end

Closing an agent-driven coding session safely involves verifying planned work against actual changes, running typecheck, test, and lint quality gates, then committing validated changes and recording session metrics. This prevents unsafe commits while generating a structured session summary.

Session orchestration close-out for Claude Code, Codex, and Cursor IDE is the process of finalizing agent-driven engineering work by auditing wave histories, extracting learnings, creating carryover or discovery issues, and appending session JSONL entries for analytics and vault mirroring.

Yes, you can use Conventional Commits and VCS integration to finalize engineering session changes. The session close-out stages reviewed artifacts, commits with Conventional Commits formatting, pushes to origin and optional GitHub mirror, and synchronizes VCS issues for partial work.

Yes, you need access to the platform state directory and persistence-enabled state to record session metrics and learnings. Optional Obsidian vault or GitHub mirror configuration can also be integrated for mirroring session JSONL entries and analytics.

To handle carryover issues and emergent work when finalizing a coding session, the close-out process cross-checks planned items against actual changes, creates carryover issues for partial work, and documents emergent work discovered during the session before committing validated changes.

Automated session close-out for agent-driven engineering requires persistence-enabled state and platform state directory access to function. Without optional Obsidian vault or GitHub mirror configuration, vault validation and remote mirroring capabilities are unavailable, limiting metrics synchronization and analytics extraction.