Overview
Bundles package structured context (files, events, transcript) for clean handoffs between agents. They create a durable reference that can be expanded later, avoiding large copy-paste blocks.Quick Start
List Bundles
Limit to last N bundles
JSON output
Example Output
View Bundle
Bundle ID or prefixAccepts:
- Event ID:
123 - Full bundle ID:
bundle:abc123xyz - Prefix:
abc123(matchesbundle:abc123xyz)
Example Output
Expand Bundle
Files Section
Shows file metadata with size, line count, and modification time:Transcript Section
Respects detail level specified in bundle:Events Section
Full JSON output for each event (supports ranges like100-105):
Bundle Chain
extends field).
Example
Prepare Bundle
Target agent (default: self)
Last N transcript exchanges to suggest
Events per category to scan
Hide how-to section
JSON output with transcript text and template command
Example Output
Create Bundle
Bundle title (positional or
--title flag)Bundle description (required)Should comprehensively explain:
- What happened
- Decisions made
- Current state
- Issues encountered
- Next steps
Comma-separated event IDs or ranges
Comma-separated file paths
Transcript ranges with detail levelsFormat:
<range>:<detail>[,<range>:<detail>...]Detail levels:- normal - Truncated (user: full, action: ~200 chars, tools: names only)
- full - Complete text (no truncation)
- detailed - Complete text + tool I/O, edits, errors
Parent bundle ID (creates chain)
Output bundle ID as JSON
Raw JSON Mode
Raw bundle JSON string
Path to bundle JSON file
Bundle JSON Format
Fields
- title (string, required) - Short bundle name
- description (string, required) - Comprehensive context
- refs (object, required) - References to context items
- events (array) - Event IDs or ranges (e.g.,
"100-105") - files (array) - File paths
- transcript (array) - Ranges with detail (e.g.,
"10-15:normal")
- events (array) - Event IDs or ranges (e.g.,
- extends (string, optional) - Parent bundle ID
Examples
Simple Bundle
Comprehensive Handoff
Chained Context
Send with Bundle
Create bundle inline while sending:Workflow: Prepare → Edit → Create
Script Usage
Notes
- Bundle events stored in database with type
bundle - Bundle IDs:
bundle:<timestamp>_<random>(8 chars) - Event ranges expanded during
cat(e.g.,100-105→ 6 events) - File paths stored as provided (relative or absolute)
- Transcript detail level respected in expansion
- Missing files shown as “(not found)” in
cat - Bundles are immutable after creation
extendscreates parent chain (view withchain)- Prefix matching:
abcmatchesbundle:abc123xyz