Expand description
Session lifecycle and local Session History.
In-progress transcript entries live in kcode-session-log. Typed lifecycle,
command, and stop records live in a separate .session-control journal.
Successfully committed sessions leave a synchronized local receipt for
their immutable Kweb object.
Modules§
Structs§
- Checkpoint
- Command
Outcome - Completion
Receipt - The durable, camel-case completion receipt stored in the catalog.
- Config
- Created
- Error
- Expected
Version - Ingress
Failure - Launch
Session - NewCommand
- NewCurrent
Work Stop - NewIngress
Session - NewObject
- NewSession
- NewStop
Request - Provider
Cost Compatibility - Optional compatibility callbacks for legacy provider-cost projection.
- Record
Completion - Input used to persist one completed session receipt.
- Register
Session - Retry
Ingress - Session
- Session
Command - Session
History - Session
Launch - Session
Record - Session
Stop Request - Start
Ingress - Start
Session - Stop
Listener - Stop
Outcome - Stored
Object