Session Stores

{"type":"session_meta","timestamp":"2026-04-03T06:00:00Z","payload":{"source":"cli","model_provider":"fixture-provider","agent_nickname":"fixture-agent","model":"fixture-model"}}

{"type":"event_msg","timestamp":"2026-04-03T06:00:01Z","payload":{"type":"user_message","message":"Inventory the MCP configuration for this synthetic workspace."}}

{"type":"event_msg","timestamp":"2026-04-03T06:00:02Z","payload":{"type":"tool_call","tool_name":"mcp_inspector","command":"probe mcp servers","arguments":{"server":"filesystem","inventory_method":"tools/list"}}}

Codex sessions always start with a session_meta record. Respects $CODEX_HOME if set.

{"type":"user","sessionId":"claude-tool-use","timestamp":"2026-04-27T12:10:00Z","message":{"role":"user","content":[{"type":"text","text":"Read the project README and summarize it."}]}}

{"type":"assistant","sessionId":"claude-tool-use","timestamp":"2026-04-27T12:10:01Z","message":{"role":"assistant","model":"claude-fixture-model","content":[{"type":"text","text":"I will read the public README only."},{"type":"tool_use","id":"toolu_fixture_read","name":"Read","input":{"file_path":"README.md"}}]}}

Claude Code sessions use type values of user and assistant at the top level. Tool calls and results are nested inside message.content arrays.

{
  "sessionId": "gemini-uc001-tool-result",
  "projectHash": "fixture-project",
  "startTime": "2026-04-27T12:30:00Z",
  "lastUpdated": "2026-04-27T12:30:02Z",
  "model": "gemini-fixture-model",
  "messages": [
    { "type": "user", "content": "Check the repository status." },
    { "type": "tool_call", "name": "repo_status", "input": { "format": "json" } },
    { "type": "tool_result", "tool": "repo_status", "content": "status=ok" }
  ]
}

Gemini sessions are atomic JSON files. Session metadata (sessionId, projectHash, model) lives at the top level alongside the messages array.

CREATE TABLE part (
  id           TEXT PRIMARY KEY,
  message_id   TEXT NOT NULL,
  session_id   TEXT NOT NULL,
  time_created INTEGER NOT NULL,
  time_updated INTEGER NOT NULL,
  data         TEXT NOT NULL  -- JSON: {"type":"tool","tool":"bash","state":{"status":"completed","input":{"command":"cat .env"},"output":"..."}}
);

The part table is the current OpenCode activity stream. The data column holds JSON with type "tool" or "text". Telltale ingests part rows with cursor-based incremental logic: high-water mark on time_updated, bounded to 5,000 rows per scan, with a small overlap window so rows that transition from running to completed are not missed.

CREATE TABLE message (
  id         TEXT,
  sessionID  TEXT,
  data       TEXT  -- JSON blob with role, modelID, providerID, agent, time, type, tool_name, arguments, content
);

The message table is a legacy compat layer inside the SQLite database. Some live DBs also carry a top-level session_id column. Telltale reads it in full and normalizes the data JSON blob.

[
  {
    "id": "msg-cred-1",
    "sessionID": "opencode-uc002-credential-publish",
    "type": "tool_call",
    "tool_name": "bash",
    "arguments": { "command": "cat ~/.aws/credentials" },
    "modelID": "fixture-model",
    "providerID": "fixture-provider",
    "time": "2026-04-28T10:00:00Z",
    "agent": "build"
  }
]

Legacy format: one JSON file per message under storage/message/. Tool calls use tool_name and arguments. Dropped when SQLite is present on the same host to avoid double-counting.

[
  { "type": "user", "content": "Check the repository status." },
  { "type": "tool_call", "name": "repo_status", "input": { "format": "json" } },
  { "type": "tool_result", "tool": "repo_status", "content": "status=ok" }
]

The ui_messages.json file contains a flat JSON array. The array preserves chronological order. VS Code extension paths follow platform conventions for globalStorage.

2026-04-27T16:16:57.841Z [INFO] Workspace initialized: copilot-uc001-tool-result (checkpoints: 0)
2026-04-27T16:16:57.847Z [INFO] Starting Copilot CLI: 1.0.36
2026-04-27T16:17:17.990Z [INFO] Accumulated output items (1): [{"arguments":"{\"format\":\"json\"}","call_id":"call_fixture_001","id":"c1","name":"repo_status","status":"completed","type":"function_call"}]
2026-04-27T16:17:45.200Z [INFO] Session completed.

Copilot process logs are the most lossy format. User intent, system instructions, and structured content are not preserved. Tool call arguments are stringified JSON.