Sessions & History
Find saved sessions and continue your work.
A task does not always fit into one sitting. Find a saved conversation, revisit its decisions and continue with your current project state.
Sessions are stored locally by the CLI. Availability depends on retained files and your setup; history is not a permanent backup.
Find. Load. Recheck.
- 01
Find the conversation.
List sessions for the current project or across projects. Use recall to look through saved session history.
- 02
Continue the discussion.
Load a chosen session and its conversation context. Confirm a project switch when one is required.
- 03
Check where the code stands.
Loading chat history does not restore the old working tree. Inspect current files before continuing a previous task.
Start with the saved sessions.
Run these commands inside Lurus Code chat. /resume lists recent project sessions; /sessions all broadens the list.
Read the documentation- List project sessions
/resume - List sessions across projects
/sessions all
A handoff you can read
Save the conversation beyond the chat.
/save exports a Markdown transcript. Use it as a handoff or reference, not as a complete backup of tools, files and generated artifacts. Review it before sharing sensitive project details.
- Export the conversation
/save
Chat history is not a code checkpoint.
/rewind chat concerns the conversation. Code rollback uses the separate checkpoint workflow. Review the proposed rollback scope before changing files.
Local sessions and exported transcripts have their own storage lifecycle. The model-processing guarantees below do not mean these local files are never stored.
Your code stays yours.
Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.
See privacy and processing detailsA few things to know before you start.
Does loading a session restore the code?
Are sessions retained forever?
Does Zero Data Retention mean no local history?
Sessions & History
Make the next session a continuation.
Open your project, find the conversation and verify the current code before taking the next step.
Sessions are stored locally by the CLI. Availability depends on retained files and your setup; history is not a permanent backup.
Want to start with your team? Talk to us.