continue
Identity
-
Names:
dev.continue; short aliascontinue. -
Native format:
continue-session-json,sessions/<sessionId>.json; the separate catalog is discovery only. -
Session ID: Persisted
sessionId, no namespace. -
Compaction: At the pin,
conversationSummarysummarizes the history prefix up to and including its containing item. Mapreplaces.throughIdto that item’s last context projection. The summary is not an extra assistant message. -
Notes: Each persisted
promptLogs[]item identifies an inference with a derived key.modelProvideris a provider;modelTitleandchatModelTitleare labels, not model IDs. Prompt logs do not prove exact request context. ContextItem arrays in tool state remain raw unless explicit tool-message content records rendering. Current mode, tools and totals are tail snapshots; totals are cumulative session usage.
Position basis
Use only positions established by the stated format and mapping evidence. Current-state rows without transcript positions form the snapshot tail. A protocol commit boundary takes precedence over physical EOF; uncommitted bytes are not a gap.
Destinations
continue: native facts without a standard field
Links
-
Entity keys and links: GUI
ChatHistoryItemWithMessageId.message.idis native. Core ChatMessage can lack it and uses capture-scoped position.toolCallStates[].toolCalltakes precedence overmessage.toolCalls;toolCall.idjoins explicit tool-messagetoolCallId. Duplicate IDs do not join by order. - Lineage: No native inter-session parent, child, copy or root contract is qualified. Generic fields that look like parent pointers remain source evidence.
Usage
Select one report per native accounting identity only when this entry establishes that identity. Keep unjoinable or overlapping reports as native evidence. Declare when semantic coverage is incomplete. Schema defaults and placeholder zeros are not reported usage. Backend inclusion rules require evidence; do not infer them from a model name.Lane and unassigned facts
Facts without established session ownership use manifest_meta["dev.continue/unassigned"] with the common shape. A selection may keep these facts with any subset of sessions, including an empty subset, but must not imply that a session owns them. State the selection policy in the export report.
Losses
Declare every applicable loss under ASR-157. Missing model rendering, accounting joins, lineage or exact context boundaries remain losses when this entry does not qualify them. Unknown ownership is not itself lost data. Omitted unassigned facts use a documented vendor loss or report, not a new core category.Evidence
Basis: source-verified at Continue commit5522c6f44ca0ac3528b37244818fbfa39b5af470 (core/util/history.ts, sessionSlice and conversationCompaction), with authored tests. No package version or end-to-end runtime capture is established.
Evidence applies only to the named formats and explicit mappings above. A real capture covers only the behavior that was exercised. A writer probe run without a model covers persistence only, not model or tool execution. Authored tests do not qualify an agent version. Unlisted formats and link mappings remain unqualified.
Observations from 2026-10-27
observed, version 1.5.47: CLI 1.5.47 retained history items, toolCallStates and result content in three runs. The public fixture covers one read/edit/shell-test session with four tool call/result pairs. It supplies no fork or compaction evidence. Preserve each whole history item in native.record or native.blob.
The ctx conversion produced 3 streams and 54 records, with 0 errors, 3 notices, 0 gaps and 0 unidentified inputs under validator-v0.1.2. These counts describe the selected output; an empty bundle qualifies no source format. The separately retained sanitized native fixture has capture@1.5.47 evidence for one read/edit/shell-test session only. The other runs remain observed evidence.
Whole native records use native.record or native.blob, with JSON text columns preserved as strings. The exporter’s own bookkeeping for serialization, partitioning and message keys belongs in the exporter namespace (rs.ctx for ctx), not in a provider metadata destination. These runs add no evidence for unexercised approvals, lineage links, compaction boundaries or exact request context.