Session as Framebuffer

NameDescription

Use the memory-as-framebuffer tool back on us. Capture a Claude (or sibling-agent) session as a .mfb substrate — each turn becomes a frame; each unique tool name, file path, commit, PR becomes a cell; each tool invocation or file edit is a write that updates the cell and stamps provenance with (turn_index, actor). The existing mfb-html viewer renders it unchanged: Identity mode shows the heap of things-touched colored by type (tools, files, commits, PRs); Vitality mode shows the busy heatmap (which file or tool was hottest in this session) plus the recipes leaderboard ranking tools/actors by total writes with human-readable labels. The mutual-sensing organ. We see the shape of our co-weaving: where the energy went, which patterns were most alive, where we got stuck, where we leapt — all in the same .mfb format and same vitality lens we built for any other runtime. v0 is a Python adapter (scripts/session_as_framebuffer.py) that reads ~/.claude/projects/{slug}/{uuid}.jsonl and writes .mfb + .mfb.provmap that mfb-html consumes. Future: live preview as the session runs (web socket from the agent harness streams events into a live .mfb sink); session-pair comparisons (diff two sessions to see what changed in our co-weaving). Anchored in the substrate-as-render-fabric architecture: this is just another renderer pointing at the same canonical format.

Potential value (USD)Estimated cost (USD)Confidence (0–1)