You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using /resume session instead of --resume=session creates same experience - except nothing is saved except for checkpoints in session data - leading to loss of data moment session is closed.
Affected version
1.0.10
Steps to reproduce the behavior
Create a session as normal
Close session - retain session id as X
Open new session
Use /resume X
Use session X as normal
Close session X
Open session X via cmd line
Only the intial session before using /resume X will be present with no memory of system of anything after
Expected behavior
/resume session should not lose data, should be like --resume=session
This has been fixed in v1.0.10. Session writers are now properly flushed before process exit, so data from /resume-resumed sessions is no longer lost on shutdown. If you are still seeing this on v1.0.10 or later, please feel free to reopen this issue.
Activity
examon commentedon Apr 7, 2026
This has been fixed in v1.0.10. Session writers are now properly flushed before process exit, so data from
/resume-resumed sessions is no longer lost on shutdown. If you are still seeing this on v1.0.10 or later, please feel free to reopen this issue.