Rich History Storage Investigation

Output

Rich History Storage Investigation

Current Architecture

There are two separate working history data paths:

stream.ts
├── addToWorkingHistory()  → Session map (in-memory)
│   └── Includes: summary, length, details
│
└── builder.addToolResult() → Kontext (persisted)
    └── Only stores: summary, length (no details)

What Rich Data Exists

The buildRichToolResult() function generates rich data including:

Tool Type	Rich Data Available	Currently Stored
Glob (files)	`files[]`, `fileCount`	Only summary
Grep (search)	`matchCount`, first 20 lines	Only summary
Bash (shell)	Full output (up to 10KB)	Only summary
Edit (diff)	`oldString`, `newString`, `filePath`	Stored in input.details
TodoWrite	`todos[]` array	Stored in input.details

Storage Impact Analysis

Current kontext file sizes:
ses_df705a8d-ea1.json   636 KB  (active session, ~50 kontexts)
ses_10e72148-d11.json    21 KB  (older session)

Rich content limit in buildRichToolResult():
MAX_CONTENT_SIZE = 10 KB per tool result

Estimated impact if we stored rich details:
~20 tool calls/turn × 2-5KB avg = 40-100 KB extra per kontext
With 50 kontexts = 2-5 MB per session file

Proposed Implementation Options

Option A: Selective Rich Storage (Recommended)

Only store rich details for high-value tool results:

Short outputs (<20 lines, ~2KB) - store full content
Error messages - store for debugging
File lists (<50 files) - store structured data
Skip large outputs (full file contents, long grep results)

Impact: ~10-20KB extra per kontext

Option B: Full Rich Storage

Store all rich details (up to 10KB per result)

Maximum fidelity - history exactly matches real-time
Larger file sizes (2-5x current)
May need kontext compression/rotation

Impact: ~50-100KB extra per kontext

Option C: Lazy Loading (Deferred)

Store rich data separately, load on demand:

Keep kontext lean, store details in separate file
Load details only when user expands history item
More complex architecture, better performance at scale

Impact: Minimal storage, higher complexity

Implementation Path (Option A)

1. Update kontext.ts addToolResult():
addToolResult(toolUseId, summary, length, mcpExecutionMs, details?)

2. Update stream.ts to pass details:
builder.addToolResult(id, summary, length, mcpMs, richResult.details)

3. Filter details by size/type:
if (richResult.content && richResult.content.length < 2048) {
  details = { content: richResult.content, structured: richResult.structured };
}

4. Update renderToolResult() in console-render-items.ts
to display output.details.content when available

Important Caveat

The real-time console shows streaming events that include error messages and transient state. These are NOT tool_result events and are not captured in workingHistory. Errors would need separate tracking.

Quick Actions

▶ View Turn

Original Request

No layout configured

Details

Type General

Status Completed

Scope vibetools

Tags consolehistoryarchitecture

Created 10 Jan 2026, 9:52 am

Updated 10 Jan 2026, 9:52 am

Timing

⏱️ 140.7s

0 tools

● TTFE 0% ● Thinking 100% ● Tools 0%

Created By claude

📋 Claude's Context

Session ses_df705a8d...

Raw Data

{
  "id": "14c64627-7545-4a98-9991-217e4f4010a9",
  "type": "general",
  "status": "completed",
  "title": "Rich History Storage Investigation",
  "description": "Analysis of storing more tool data in workingHistory for richer playback",
  "context": {
    "output": "<div style=\"background:#1e1e1e;color:#e0e0e0;padding:20px;border-radius:8px;font-family:'Consolas','Monaco',monospace;\">\n<h2 style=\"font-family:sans-serif;color:#fff;margin:0 0 16px 0;\">Rich History Storage Investigation</h2>\n\n<h3 style=\"color:#98c379;margin:16px 0 8px 0;\">Current Architecture</h3>\n<p style=\"color:#abb2bf;line-height:1.6;\">There are <strong>two separate working history data paths</strong>:</p>\n\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;color:#e0e0e0;margin:8px 0;\">\n<span style=\"color:#56b6c2;font-weight:bold;\">stream.ts</span>\n├── <span style=\"color:#e5c07b;\">addToWorkingHistory()</span>  → Session map (in-memory)\n│   └── Includes: <span style=\"color:#98c379;\">summary, length, <strong>details</strong></span>\n│\n└── <span style=\"color:#e5c07b;\">builder.addToolResult()</span> → Kontext (persisted)\n    └── Only stores: <span style=\"color:#f87171;\">summary, length</span> (no details)\n</pre>\n\n<h3 style=\"color:#98c379;margin:16px 0 8px 0;\">What Rich Data Exists</h3>\n<p style=\"color:#abb2bf;\">The <code style=\"background:#2d2d2d;padding:2px 6px;border-radius:3px;color:#e5c07b;\">buildRichToolResult()</code> function generates rich data including:</p>\n\n<table style=\"width:100%;border-collapse:collapse;margin:12px 0;\">\n<tr style=\"background:#2d2d2d;\">\n<th style=\"padding:10px;text-align:left;border-bottom:1px solid #444;color:#61afef;\">Tool Type</th>\n<th style=\"padding:10px;text-align:left;border-bottom:1px solid #444;color:#61afef;\">Rich Data Available</th>\n<th style=\"padding:10px;text-align:left;border-bottom:1px solid #444;color:#61afef;\">Currently Stored</th>\n</tr>\n<tr>\n<td style=\"padding:8px;border-bottom:1px solid #333;\">Glob (files)</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;\"><code>files[]</code>, <code>fileCount</code></td>\n<td style=\"padding:8px;border-bottom:1px solid #333;color:#f87171;\">Only summary</td>\n</tr>\n<tr>\n<td style=\"padding:8px;border-bottom:1px solid #333;\">Grep (search)</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;\"><code>matchCount</code>, first 20 lines</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;color:#f87171;\">Only summary</td>\n</tr>\n<tr>\n<td style=\"padding:8px;border-bottom:1px solid #333;\">Bash (shell)</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;\">Full output (up to 10KB)</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;color:#f87171;\">Only summary</td>\n</tr>\n<tr>\n<td style=\"padding:8px;border-bottom:1px solid #333;\">Edit (diff)</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;\"><code>oldString</code>, <code>newString</code>, <code>filePath</code></td>\n<td style=\"padding:8px;border-bottom:1px solid #333;color:#98c379;\"><strong>Stored in input.details</strong></td>\n</tr>\n<tr>\n<td style=\"padding:8px;border-bottom:1px solid #333;\">TodoWrite</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;\"><code>todos[]</code> array</td>\n<td style=\"padding:8px;border-bottom:1px solid #333;color:#98c379;\"><strong>Stored in input.details</strong></td>\n</tr>\n</table>\n\n<h3 style=\"color:#98c379;margin:16px 0 8px 0;\">Storage Impact Analysis</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;color:#e0e0e0;margin:8px 0;\">\n<span style=\"color:#7f848e;\">Current kontext file sizes:</span>\nses_df705a8d-ea1.json   <span style=\"color:#e5c07b;\">636 KB</span>  (active session, ~50 kontexts)\nses_10e72148-d11.json   <span style=\"color:#e5c07b;\"> 21 KB</span>  (older session)\n\n<span style=\"color:#7f848e;\">Rich content limit in buildRichToolResult():</span>\nMAX_CONTENT_SIZE = <span style=\"color:#d19a66;\">10 KB</span> per tool result\n\n<span style=\"color:#7f848e;\">Estimated impact if we stored rich details:</span>\n~20 tool calls/turn × 2-5KB avg = <span style=\"color:#f87171;\">40-100 KB extra per kontext</span>\nWith 50 kontexts = <span style=\"color:#f87171;\">2-5 MB per session file</span>\n</pre>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">Proposed Implementation Options</h3>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin:12px 0;border-left:4px solid #98c379;\">\n<h4 style=\"color:#98c379;margin:0 0 8px 0;\">Option A: Selective Rich Storage (Recommended)</h4>\n<p style=\"color:#abb2bf;margin:0;line-height:1.6;\">Only store rich details for high-value tool results:</p>\n<ul style=\"color:#abb2bf;margin:8px 0;padding-left:20px;\">\n<li>Short outputs (&lt;20 lines, ~2KB) - store full content</li>\n<li>Error messages - store for debugging</li>\n<li>File lists (&lt;50 files) - store structured data</li>\n<li>Skip large outputs (full file contents, long grep results)</li>\n</ul>\n<p style=\"color:#7f848e;margin:8px 0 0 0;\">Impact: ~10-20KB extra per kontext</p>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin:12px 0;border-left:4px solid #61afef;\">\n<h4 style=\"color:#61afef;margin:0 0 8px 0;\">Option B: Full Rich Storage</h4>\n<p style=\"color:#abb2bf;margin:0;line-height:1.6;\">Store all rich details (up to 10KB per result)</p>\n<ul style=\"color:#abb2bf;margin:8px 0;padding-left:20px;\">\n<li>Maximum fidelity - history exactly matches real-time</li>\n<li>Larger file sizes (2-5x current)</li>\n<li>May need kontext compression/rotation</li>\n</ul>\n<p style=\"color:#7f848e;margin:8px 0 0 0;\">Impact: ~50-100KB extra per kontext</p>\n</div>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin:12px 0;border-left:4px solid #c678dd;\">\n<h4 style=\"color:#c678dd;margin:0 0 8px 0;\">Option C: Lazy Loading (Deferred)</h4>\n<p style=\"color:#abb2bf;margin:0;line-height:1.6;\">Store rich data separately, load on demand:</p>\n<ul style=\"color:#abb2bf;margin:8px 0;padding-left:20px;\">\n<li>Keep kontext lean, store details in separate file</li>\n<li>Load details only when user expands history item</li>\n<li>More complex architecture, better performance at scale</li>\n</ul>\n<p style=\"color:#7f848e;margin:8px 0 0 0;\">Impact: Minimal storage, higher complexity</p>\n</div>\n\n<h3 style=\"color:#98c379;margin:16px 0 8px 0;\">Implementation Path (Option A)</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;color:#e0e0e0;margin:8px 0;\">\n<span style=\"color:#7f848e;\">1. Update kontext.ts addToolResult():</span>\naddToolResult(toolUseId, summary, length, mcpExecutionMs, <span style=\"color:#98c379;\">details?</span>)\n\n<span style=\"color:#7f848e;\">2. Update stream.ts to pass details:</span>\nbuilder.addToolResult(id, summary, length, mcpMs, <span style=\"color:#98c379;\">richResult.details</span>)\n\n<span style=\"color:#7f848e;\">3. Filter details by size/type:</span>\n<span style=\"color:#c678dd;\">if</span> (richResult.content && richResult.content.length < 2048) {\n  details = { content: richResult.content, structured: richResult.structured };\n}\n\n<span style=\"color:#7f848e;\">4. Update renderToolResult() in console-render-items.ts</span>\nto display output.details.content when available\n</pre>\n\n<h3 style=\"color:#f87171;margin:16px 0 8px 0;\">Important Caveat</h3>\n<p style=\"color:#abb2bf;line-height:1.6;\">The real-time console shows <strong>streaming events</strong> that include error messages and transient state. These are NOT tool_result events and are not captured in workingHistory. Errors would need separate tracking.</p>\n\n</div>",
    "requestedAt": "2025-01-10T15:45:00Z",
    "requestId": "04c69fbc-0a9a-4a2b-8e16-2cae242671d0",
    "choices": [
      {
        "label": "Implement Option A",
        "value": "Implement selective rich storage (Option A) - store short outputs, errors, and file lists in workingHistory",
        "primary": true
      },
      {
        "label": "Implement Option B",
        "value": "Implement full rich storage (Option B) - store all rich details up to 10KB per result"
      },
      {
        "label": "More analysis needed",
        "value": "I need more analysis before deciding - what are the typical tool result sizes?"
      }
    ],
    "turnTiming": {
      "totalMs": 140675,
      "ttfeMs": 59,
      "thinkingMs": 140616,
      "toolExecutionMs": 0,
      "toolCallCount": 0,
      "thinkingPct": 100,
      "toolsPct": 0,
      "ttfePct": 0
    }
  },
  "createdBy": "claude",
  "createdAt": "2026-01-09T23:52:03.358Z",
  "updatedAt": "2026-01-09T23:52:09.547Z",
  "requestId": "04c69fbc-0a9a-4a2b-8e16-2cae242671d0",
  "scope": "vibetools",
  "tags": [
    "console",
    "history",
    "architecture"
  ],
  "sessionId": "ses_df705a8d-ea1",
  "flowId": "flow_01KEHQ5A7ZX7YDB8KG1NP2GE68",
  "flowLinks": [
    {
      "flowId": "flow_01KEHQ5A7ZX7YDB8KG1NP2GE68",
      "edgeType": "evidence",
      "createdAt": "2026-01-09T23:52:03.358Z"
    }
  ]
}