Session export & import
Move supported recorded session state through the session bundle contract. Check project identity and source availability in the receiving environment.
Explore this capabilityMemory & Continuity
Keep the knowledge.Continue the work.
Give the next session a useful starting point. Retain selected decisions, findings and working state, with the references needed to check what still holds.
The approach
Keep the finding. Keep its source.
Save the decision and its reasoning. Recall what the next task needs, then verify it against the current source.
Retain
Save what matters next.
Store selected facts and decisions as project knowledge. Use session state to preserve progress and recent work.
- Decision
- What was chosen, with the reasoning behind it.
- Finding
- What was discovered and where to verify it.
- Progress
- What is complete and what remains unresolved.
First task
Investigate the formatter.
Retained decision
Keep currency formatting in fmtUsd.
src/lib/roi.ts:83–89Next task
Recall. Check. Continue.
Confirm the decision against the current source.
Retrieve & review
Recall. Check. Update.
Find saved knowledge by query or category. Check the source, update changed findings and remove obsolete entries.
- Relevant recall
- Choose knowledge for the current question.
- Source check
- A stored fact does not make the source immutable.
- Maintenance
- Review confidence, conflicting findings and obsolete entries.
Continue & hand off
Make the next starting point clear.
Restore the recorded task, decisions and source references, or prepare them for the next person or agent. A useful handoff distinguishes completed work from open questions and keeps access permissions intact.
- Session
- Recover recorded working context within the runtime’s retention scope.
- Progress
- Keep completed work and outstanding steps distinguishable.
- Files
- Return to the files associated with the recorded work.
Different kinds of state
Different state. Different purpose.
Cache reuses results. Memory keeps knowledge. Versioned checkpoints preserve working state for export, restoration and migration. Every resumed read still follows current source permissions.
- Cache
- Reuse eligible results under freshness, invalidation and current-access checks.
- Memory
- Retain selected facts and decisions across work.
- Checkpoint
- Restore supported recorded state through a compatible runtime and interface.
In your workflow
Continue here. Carry it elsewhere.
Keep selected context portable without treating every stored format as interchangeable. Choose the right carrier for knowledge, a session or a checkpoint.
Portable knowledge
Export selected facts and relationships as knowledge data or an inspectable open format. Review stale or conflicting findings before relying on them.
Explore this capabilityContext packages
Inspect, export and import supported knowledge, graph or session layers. A package digest proves integrity, not whether its contents are current or authorized for the recipient.
Explore this capabilityCheckpoint continuity
Restore the state represented by a compatible checkpoint. File recovery, session bundles and SDK checkpoint packages have distinct versions and coverage.
Explore this capabilityQuestions & answers
Memory questions.
Does LeanCTX remember every conversation?
Continuity uses the knowledge and session state recorded through the active integration. It is not a promise to capture every conversation, source or model thought. Retention depends on the configured runtime.
Can I treat recalled knowledge as current truth?
Check it against current sources. Decisions can be superseded and code can change. Retained knowledge is a starting point for verification.
Start with LeanCTX
Start the next task informed.
Record one useful decision today. Bring it back when the next task needs the reasoning behind it.
Local-first. Model-agnostic. Your context.