Skip to content

PrunableConversation

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:133

A conversation gth history prune would remove the stored state of.

bytes: number

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:141


checkpointCount: number

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:140


optional command?: string

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:136


conversationId: number

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:134


lastActivityTs: string

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:138

Last recorded activity: the newest turn’s timestamp, or the conversation’s start.


recentlyActive: boolean

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:153

True when the last recorded turn is newer than RECLAIM_GRACE_MS — so this conversation may be open in another window right now, and pruning it would take a live session’s memory rather than an old one’s.

A flag and not an exclusion, deliberately. gth history prune is given an explicit bound by the person typing it, and silently keeping back rows inside that bound would make the bound a lie; liveness across processes is also not knowable from here, so a refusal would be a guess wearing a guarantee. The automatic pass can be conservative because nobody asked for it. This one says what it is about to do and lets the person answer.


threadId: string

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:135


turnCount: number

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/history/checkpointRetention.ts:139