Updated · 2 episodes · 2 shows · 2 source notes

concept

Agent Tape System

Definition

An agent tape system is an append-only record of messages, tool calls, observations, state changes, and other task events, paired with a movable working view that determines which parts the agent currently sees.

Current Synthesis

The DeepChat and Bub cases treat tape as a context architecture rather than a synonym for chat history. Preserving an ordered event record lets an agent revisit earlier evidence during long work, while a pointer, window, anchor, or handoff controls what enters the active model context. DeepChat combines the record with selective compression and inspection; Bub emphasizes hiding earlier spans without deleting them and searching the original history when needed. Both approaches can reduce information loss relative to replacing the full history with one summary, but neither eliminates retrieval, salience, cost, or privacy problems.

Tape belongs inside the wider Agent Harness: the record only becomes useful when the runtime can decide what to retain, expose, summarize, inspect, or replay. Its inspectability also makes it useful for diagnosing tool calls, reasoning content, multi-turn interaction, and failed loops.

Key Claims

  • Append-only storage preserves task history while allowing the active context to move independently.
  • Agents can revisit earlier records during long tasks instead of relying entirely on lossy context compression.
  • Tape inspection improves debugging because model requests, tool calls, observations, and loops remain traceable.
  • A tape is not automatically good memory; selection, compression, retrieval, and relevance still determine what the model can use.
  • Persistent records require privacy, retention, and access controls when they contain local files, credentials, or enterprise work context.
  • Anchors and handoffs can express task-stage boundaries without requiring destructive compression of earlier records.
  • Historical search is itself an agent behavior that needs query discipline and selective loading to avoid flooding active context.

Evidence

Long-task context continuity

Inspection and debugging

Anchors, handoffs, and selective retrieval

Counterevidence & Qualifications

  • The source does not provide controlled comparisons showing that Tape outperforms other context-management approaches.
  • An append-only record can grow expensive, surface stale information, or retain sensitive material unless the harness applies retrieval, compaction, and governance.
  • Tape, Persistent Agent Memory, and AI Skills overlap in practice but serve different functions: event history, durable experience, and reusable procedure should not be collapsed into one layer.
  • Bub’s preference for preserving original history does not prove that avoiding compression is always more accurate, economical, private, or operationally reliable.

What Changed

  • Added Bub’s anchor-and-handoff implementation as a second tape architecture.
  • Distinguished nondestructive history retention from active-context visibility.
  • Added selective historical search and context flooding as explicit operational boundaries.

Sources

2 source notes across 2 shows
  1. VOL.002|DeepChat:为什么要做一块开源 AI 试验田? 为 AI 发电
  2. Ep 58. 从零实现龙虾需要什么?Bub 开发者访谈 捕蛇者说