Koder keeps conversation state and local memory so you can resume work without rebuilding context by hand.

Default storage paths:

Koder does not require a hosted session service for these features.

Use named sessions when you want durable work streams:

koder -s api-migration
koder -s api-migration "continue the serializer cleanup"
koder --resume
koder --continue

Inside the TUI:

/session
/rename api-migration
/tag backend
/resume api-migration
/clear

/clear switches to a fresh workflow state. The previous named session remains resumable unless you explicitly remove local state outside Koder.

Use these commands to understand what the active session contains:

/status
/summary
/stats
/insights
/usage
/cost
/files
/context
/ctx_viz

/summary is a compact local status report. /insights focuses on transcript roles, tool activity, context files, and usage counters.

Long sessions can be compacted to keep the useful parts while reducing context size:

/compact

Use rewind when a recent turn sent the session down the wrong path:

/rewind

/rewind lists recent prompt targets, restores the selected prompt into input, and trims later session history.

Use local export commands when you want a durable artifact from a session:

/export
/copy
/share

/share prints share metadata for the active session. It does not upload transcript content.

Memory files are local markdown files. User memory is shared across projects; project memory stays in the workspace.

/memory
/remember prefers focused tests before full suites
/thinkback
/thinkback-play

/thinkback summarizes recent local session context and prompt counts without running a model request. /thinkback-play replays recent turns from the active session.

AutoDream is a best-effort cleanup-time memory consolidation task. When its local cadence threshold is met, it asks the configured provider to extract durable memory notes, writes them to ~/.koder/memory/auto-dream-*.md, and records task metadata under ~/.koder/tasks/auto-dream/.

Inspect recent runtime tasks with:

/tasks

Use settings bundles to move configuration and local notes between machines:

koder config export ~/koder-settings.json
koder config import ~/koder-settings.json --dry-run
koder config import ~/koder-settings.json

Bundles include known Koder config, settings, keybindings, user memories, project memories, and project session notes. They exclude token stores, model caches, transcripts, task records, and plugin caches.