tenequm/pond

> "I know we discussed that before. Why can't I find that damn conversation?"
Pond makes every AI agent session you've ever run - Claude Code, Codex, any tool, any machine - searchable in one place.
Your agent history is already on your disk: thousands of sessions full of decisions, fixes, and dead ends - scattered across tools that can't search them. Pond ingests them all automatically and losslessly into storage you own (a local dir or your own S3 bucket), makes the whole corpus searchable and SQL-queryable, and hands that recall back to your agents over MCP - so "how did we fix this before?" is a query, not an archaeology dig. Sessions stop being locked to the tool that created them: any session can be restored into any supported client and continued there.
Or prompt your agent: *"Please install and set up pond (see github.com/tenequm/pond)"* - the full, failure-proofed version of that prompt is in Connect your agents.
A live 12k-session corpus, then a three-month-old fix found and verified against the current code ( crisper MP4 )
Five real recall questions, one corpus, one machine - method, raw numbers, and a rerunnable script in docs/benchmarks
Status: pre-v1. Schemas, wire shapes, and config keys are subject to breaking change until v1. Full documentation lives at pond.locker; the contract is docs/spec.md.
Quickstart
Install, run guided setup, and ingest your local sessions:
pond init registers pond as an MCP server for Claude Code and installs the bundled pond skill; for Codex it prints the command to run instead - restart the client afterwards so the tools load. By hand: claude mcp add -s user pond -- pond mcp, codex mcp add pond -- pond mcp; skill: mkdir -p ~/.claude/skills/pond && pond skill > ~/.claude/skills/pond/SKILL.md (that whole line is POSIX-only - mkdir -p, &&, and > all break or corrupt in Windows PowerShell 5.1; use the PowerShell block in Connect your agents). Then ask your agent - real prompts from daily use:
Sessions are picked up automatically from **Claude Code**, the **Claude desktop app** (local agent mode), **Codex CLI**, **opencode**, **pi-coding-agent**, **oh-my-pi**, **OpenClaw**, **NanoClaw**, **Hermes Agent**, **letta-code**, **grok-build**, **Antigravity CLI** (agy, including its ACP server), and **Devin CLI** (devin). A Claude.ai data export imports with pond sync claude-ai-export --path (manual download, so not auto-discovered).
Isn't this another memory tool?
No - it's the layer underneath one. Memory tools store what they decided you'd need - facts, summaries, filed chunks; the sessions themselves are gone. Pond keeps the sessions: every message, tool call, and result, value-complete, cross-client, in storage you own, never pruned - searchable over MCP and restorable into any client. Memory is a derived view you can always rebuild from an archive; an archive can never be rebuilt from memories.
Three kinds of tool get called "memory". Side by side:
| | **pond** | **Session search** (ctx, deja-vu, cass) | **Memory layers** (Mem0, Letta) |
|---|---|---|---|
| History from before install | yes | yes | no |
| What is kept | the whole session | a search index ¹ | extracted facts |
| Where it lives | local dir or S3 bucket | local index | the tool's database |
| After the harness deletes the file | still there | gone at next refresh ¹ | only the extract |
| Several machines | one shared bucket | pulled into one machine ² | shared server or cloud |
| Agent access | CLI, MCP, HTTP, SQL | CLI, MCP ³ | HTTP, SDK, MCP |
¹ cass also mirrors the raw files, so they outlive the source. ² deja-vu copies records between machines over ssh; cass pulls other hosts' session files over ssh/rsync into its local index; ctx is single-machine. ³ cass has no MCP server.
Pick session search for fast local recall. Pick a memory layer when the agent should carry distilled facts, not the record. Pick pond when you want the sessions themselves, in storage you own, from every machine you run.
Full comparison, with receipts per tool: pond.locker/compare. Every cell is a claim about a specific version of someone else's project. If one has gone stale, open an issue and it gets fixed the same day.
Background
Every agentic CLI ships its own session format and its own search surface. Switching tools means losing history. Replaying a Claude Code session in another provider's tooling means re-translating the wire shape by hand. Hosted multi-tenant deployments rebuild the same storage layer from scratch.