Session Management

To resume a long-running session after an interruption, you replay its history from the event store using the prior session_id. This reconstructs the full session state, ensuring durable continuity and an auditable history across runs.

Event-store replay for durable session persistence is the process of reconstructing a session's state by replaying its historical events. It ensures long-running workflows remain durable and auditable, allowing full state recovery across disruptions.

Configurable compaction thresholds allow you to balance context size and performance during session replay. By adjusting these settings, you control how much historical event data is retained versus compacted to optimize the durable store's efficiency.

Yes, session management supports a durable realm-backed session store that materializes projected state under .rkat/sessions. This projection is explicitly not the canonical state, but rather a durable view for managing long-running, interactive workflows.

You need durable session persistence and replay for long-running, interactive sessions where interruptions occur. It is essential when your workflows require resume capabilities from a prior session_id and full historical reconstruction via an event store.

Your session state needs projection under .rkat/sessions instead of storing canonical state directly to maintain an auditable history. The realm-backed durable store projects state for recovery, while the event store retains the canonical event sequence for full replay.