troubleshooting
Fix daemon/client version mismatch
A version mismatch appears when the CLI, daemon, or resident worker were installed or updated separately. The safe fix is to stop resident sessions, update all components to the same channel and version, restart the daemon, and reattach. Back up important sessions first because protocol changes can break resume.
First-party announcement, documentation, release, or installer.
Symptom
Symptom
The CLI connects but the daemon rejects requests or resumes fail right after an update.
Diagnosis
The client, daemon, or worker likely ran different versions or channels.
Safe fix
Stop everything, align versions, restart the daemon, then reattach to the session.
Verification
Check version banners on the CLI and daemon before you resume work.
Rollback
Roll back to the last matching version if the new release is incompatible.
Diagnosis
Symptom
The CLI connects but the daemon rejects requests or resumes fail right after an update.
Diagnosis
The client, daemon, or worker likely ran different versions or channels.
Safe fix
Stop everything, align versions, restart the daemon, then reattach to the session.
Verification
Check version banners on the CLI and daemon before you resume work.
Rollback
Roll back to the last matching version if the new release is incompatible.
Safe fix
Symptom
The CLI connects but the daemon rejects requests or resumes fail right after an update.
Diagnosis
The client, daemon, or worker likely ran different versions or channels.
Safe fix
Stop everything, align versions, restart the daemon, then reattach to the session.
Verification
Check version banners on the CLI and daemon before you resume work.
Rollback
Roll back to the last matching version if the new release is incompatible.
Verification
Symptom
The CLI connects but the daemon rejects requests or resumes fail right after an update.
Diagnosis
The client, daemon, or worker likely ran different versions or channels.
Safe fix
Stop everything, align versions, restart the daemon, then reattach to the session.
Verification
Check version banners on the CLI and daemon before you resume work.
Rollback
Roll back to the last matching version if the new release is incompatible.
Rollback
Symptom
The CLI connects but the daemon rejects requests or resumes fail right after an update.
Diagnosis
The client, daemon, or worker likely ran different versions or channels.
Safe fix
Stop everything, align versions, restart the daemon, then reattach to the session.
Verification
Check version banners on the CLI and daemon before you resume work.
Rollback
Roll back to the last matching version if the new release is incompatible.