Session Management

Every Drisp run creates a session persisted to SQLite at ~/.config/drisp/sessions/<session-uuid>/session.db.

Browse Sessions

drisp sessions

Opens an interactive picker. Navigate with arrow keys, press Enter to resume.

Also available as a slash command during a session:

/sessions

Resume

Resume the most recent session for the current project:

drisp resume

Resume a specific session by ID:

drisp resume <session-uuid>

Resume works by replaying feed_events from the SQLite store back into the timeline. The event feed populates with historical events, then new events stream in as they arrive.

Resume in Exec Mode

drisp exec "continue previous work" --continue
drisp exec "continue" --continue=<session-uuid>

Session Data

Each session stores:

  • Runtime events — raw hook events from the agent harness with full payloads
  • Feed events — derived display events shown in the UI timeline
  • Adapter sessions — Agent session records with token usage (input, output, cache read/write, context size)
  • Metadata — project directory, timestamps, event count, label

Session Statistics

During an active session, use:

/stats

Shows session-level statistics including event counts and duration.

/context

Shows token breakdown and current context window usage.

Ephemeral Sessions

Skip session persistence entirely:

drisp exec "quick check" --ephemeral

No database file is created. The session cannot be resumed.