Expand description
Session lifecycle and local Session History.
In-progress transcript entries live in kcode-session-log. Session
lifecycle and command records live in a separate Session History control
journal.
Successfully committed sessions leave only one local line containing their
immutable Kweb object ID; their details are loaded from Kweb on demand.
Re-exports§
pub use chatend::Session;
Modules§
- chatend
- Kennedy’s reconstructed, provider-independent durable session context.
Structs§
- Checkpoint
- Command
Outcome - Completion
Receipt - Config
- Created
- Error
- Expected
Version - Ingress
Failure - NewCommand
- NewObject
- NewSession
- Record
Completion - Register
Session - Retry
Ingress - Session
Command - Session
History - Session
Record - Start
Ingress - Start
Session - Stored
Object