roo-code

Identity

Names: roo-code / com.roocode.
Native format: cline-task: whole task arrays api_conversation_history.json (legacy fallback claude_messages.json), ui_messages.json, and task metadata documents. New Cline SDK persistence is a separate unqualified format.
Session ID: Native task-directory basename, checked against history_item.id when present. Require a stable installation/profile namespace, including for Roo UUIDv7 tasks that share the legacy format. Relocation preserves both values.
Notes: Preserve content block order, reasoning signatures and media. UI-only rows use displayContent with explicit absent model content/role. api_req_started reports a request and supports a derived inference keyed by the UI row; retain recorded tokens and cost without fabricating a model. Approval and follow-up asks record requests, not inferred decisions. lastCheckpointHash supplies a shadow-Git checkpoint ref. history_item.task supplies title; native token totals are cumulative session usage. Context-history and condensation annotations do not establish exact active-context replacement ranges.

Position basis

See Cline task arrays for the shared format. Roo has its own writer evidence; Cline’s qualification does not carry over to Roo.

Entity keys and order: Unique API id and UI ts identify rows. The pinned UI writer looks up and updates by ts, preserving it on partial completion. This is a native key contract, not a timestamp join. Duplicate keys remain distinct capture-scoped rows. Read API array, UI array, then metadata in fixed order. Every current snapshot projection uses snapshot assembly.

Record family	Position basis	Commit boundary
api	array-index	document
ui	array-index	document

Use only positions established by the stated format and mapping evidence. Current-state rows without transcript positions go at the end, as the snapshot tail. A protocol commit boundary takes precedence over physical EOF; uncommitted bytes are not a gap.

Destinations

roo-code: native facts without a standard field

Fact	Native name	Destination
Remaining source facts	The native row or item used for this projection	`native.record` on the record for this source value, or `native.blob` for a blob containing the entire source value. Preserve native JSON text columns as strings. Use a separate vendor record when several source rows feed one projection. ASR-035 applies to unsafe numbers.
Unpaired result identity	The result’s native call-ID field named above	`tool_result.nativeCallId`, verbatim
Unknown UI kind	Complete UI row	vendor record `com.roocode/ui` with `native.record`
Task state	`task_metadata.json`, `history_item.json`, `_index.json`, `context_history.json`	vendor record `com.roocode/task_metadata`; `native.record` holds `{component, value}`, where `component` is the native filename and `value` its contents

Usage

Select one report per native accounting identity only when this entry establishes that identity. Keep unjoinable or overlapping reports as native evidence. Declare incomplete semantic coverage. 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["com.roocode/unassigned"] with the common shape. Selection may retain these facts with any session subset, including an empty subset, but must not imply session ownership. 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 version 3.53.0, commit b867ec9145750d0ae1ff7f02d35406e9bf2a0b16, src/core/task/Task.ts and src/core/task-persistence/apiMessages.ts. Existing task fixtures and authored semantic tests do not qualify a new extension runtime release. Evidence applies only to the named formats and explicit mappings above. A real capture covers only exercised behavior. A no-model writer probe covers persistence, not model or tool execution. Authored tests do not qualify an agent version. Unlisted formats and link mappings remain unqualified.

{
  "name": "com.roocode",
  "aliases": [
    "roo-code"
  ],
  "namespace": {
    "rule": "required"
  },
  "positions": [
    {
      "family": "api",
      "basis": "array-index",
      "boundary": "document"
    },
    {
      "family": "ui",
      "basis": "array-index",
      "boundary": "document"
    }
  ],
  "formats": [
    {
      "id": "cline-task",
      "evidence": [
        0
      ]
    }
  ],
  "evidence": [
    {
      "label": "source",
      "revision": "b867ec9145750d0ae1ff7f02d35406e9bf2a0b16",
      "scope": "format-and-explicit-mappings"
    },
    {
      "label": "authored",
      "scope": "converter-tests-only"
    }
  ],
  "destinations": {
    "task_metadata": {
      "schema": {
        "type": "object"
      },
      "evidence": [
        0
      ]
    }
  }
}

Introduction

Format

Records

Trust

Extending and conforming

Agent registry

roo-code

roo-code

Identity

Position basis

Destinations

roo-code: native facts without a standard field

Links

Usage

Lane and unassigned facts

Losses

Evidence

​roo-code

​Identity

​Position basis

​Destinations

​roo-code: native facts without a standard field

​Links

​Usage

​Lane and unassigned facts

​Losses

​Evidence

roo-code

Identity

Position basis

Destinations

roo-code: native facts without a standard field

Links

Usage

Lane and unassigned facts

Losses

Evidence