Design System
COHERENT_E005

Session schema version mismatch

Sessions are ephemeral by design — they hold in-progress phase artifacts, not long-term state. Across CLI upgrades the session schema may change. Rather than auto-migrating (complex and risky), the CLI rejects the mismatched session and asks you to start a new one.

When you see it

A session directory exists (e.g. from an older CLI version) whose `session.json.schemaVersion` is incompatible with the installed CLI.

Why

Session schemas are tied to the CLI version that created them. A newer CLI that auto-migrated older sessions could hide real bugs; it's safer to discard.

Fix options

  1. 1

    Discard the old session and start fresh

    Nothing is lost that wasn't already lost — sessions only hold in-progress state of a not-yet-completed run.

    $ rm -rf .coherent/session/<uuid>/ && coherent session start --intent "..."

Related