Auditable timeline of what happened and why
Append-only timeline of steps, prompts, and outputs. Supports replay and provenance for debugging and compliance.
What Episodic Memory does
Episodic Memory maintains an append-only timeline of every step the assistant takes. It records prompts, tool calls, outputs, and approval decisions. Perfect for debugging, compliance, and understanding "what did it do yesterday?"
Core capabilities
- Append events per step
- List events by time range or task
- Retrieve full event details
- Replay pointers for debugging
Use cases
- "What did it do yesterday?"
- Reviewable runs and status histories
- Run replay for debugging
- Compliance and audit trails
Who benefits from Episodic Memory
Individuals
"What did it do yesterday?" answered instantly
Teams & Managers
Reviewable runs and status histories
Developers & IT
Run replay for debugging
Security & Compliance
Immutable logs with planned signing
How it works
Append event per step
Use episodic.append to record each step: prompt, tool call, output, approval decision.
Link artifacts
Each event links to artifacts (files, diffs, outputs) for full provenance.
List and retrieve events
Call episodic.list to query by time range or task. Use episodic.get for full details.
Replay for debugging
Use replay pointers to step through a run and identify issues.
Example workflows
Review yesterday's plan and outputs
Runs entirely offline"Show me yesterday's plan, approvals, and outputs"
- episodic.list (filter: yesterday)
- episodic.get (retrieve full event details)
Timeline of steps, approvals, and artifacts—full transparency
Audit team workflows
Runs entirely offline"Who approved the database migration last week?"
- episodic.list (filter: last week, task: migration)
- episodic.get (retrieve approval events)
Approval log with timestamps and user IDs—compliance-ready
Replay a failed run
Runs entirely offline"Replay the failed run from this morning"
- episodic.list (filter: this morning, status: failed)
- episodic.get (retrieve each step)
- Replay step-by-step to identify the issue
Root cause identified—fix and re-run with confidence
Technical details
Configuration
RETENTION— log retention period (default: 90 days)STORAGE_PATH— local log directorySIGNING— tamper-evident signatures (planned)
Performance notes
- Append: 5-10ms per event
- List: 10-50ms for 1K events
- Replay: depends on run complexity
Observability
- Log growth and event count
- Replay counts and latency
- Retention policy enforcement
Security posture
Write-once logs
Events are append-only. No edits or deletions (except retention policy).
Tamper-evident signing (planned)
Hash-chain signatures to detect tampering. Planned for compliance use cases.
Local storage
All logs stored on disk. No network calls for append or retrieval.
Export for compliance
Export logs in standard formats (JSON, CSV) for external audit systems.
Roadmap & status
Current features
- Append, list, and get events
- Replay pointers for debugging
- Artifact linking and provenance
Coming soon
- Hash-chain signatures for tamper-evidence
- Export to standard audit formats
- Timeline visualization UI
Frequently asked questions
Ready to audit your assistant's work?
Get started with Episodic Memory in minutes. Full transparency and provenance.