Sessions

Every conversation is persisted as JSON under your data directory (~/Library/Application Support/dupli/sessions on macOS, ~/.local/share/dupli/sessions on Linux).

Resuming

dupli -c                # continue the most recent session
dupli --session <id>    # resume a specific one

Or from inside Dupli:

» /sessions
Resume which session? (↑/↓ to move, Enter to pick, Esc to cancel)
  > Fix the auth flow     2026-10-08 12:41 · 18f2a1c9e4b-3f01
    Refactor the router   2026-10-08 09:12 · 1a11a40c8c2-7d9c

Pick with ↑/↓ (or j/k) and Enter; Esc cancels. Resuming replays the session’s previous history in the terminal so you can see where you left off. Resuming also applies to dupli -c and dupli --session <id>.

What’s saved

• All messages (yours, the model’s, and action results)
• The provider and model used
• The session title (taken from your first prompt)

Rewinding with /navigate truncates the saved history too, so a resumed session picks up exactly where you left off.

Files

Sessions are plain JSON — you can open, diff, or copy them. The id is timestamp-based so sessions sort naturally in /sessions.