Tucaen claims the released Toucan tool writes zero-token Markdown records from Claude Code and Codex transcripts that new sessions grep before starting, giving coding agents cross-session memory of what earlier sessions tried without spending model tokens.
state: corroboratedheat: lowuncertainty: mediumconvergesscott: highagent-memory session-continuity coding-agent-harnessesTucaen
What is this?
Toucan is an open-source Windows desktop workspace by Tucaen (repo created 2026-09-23, announced on Reddit) that gives Claude Code and Codex cross-session, cross-harness memory by deterministically writing, after every agent turn, a Markdown record (goal, files touched, outcome, failures) built from the session transcript alone at zero model-token cost; new sessions grep those records at boot. None of the search results mention Toucan itself — no adoption signals or independent evaluations surfaced — so its efficacy and uptake remain unverified as before. What the snippets do establish is the field it landed in: a crowded, active zone of tools mining the same default transcript stores (~/.claude/projects, ~/.codex/sessions), split between raw-capture approaches (Toucan-style append + grep/search; Darc's index-over-rollouts that proposes raw `rg` as a baseline arm; agentfdr's flight-recorder observability) and compile/compress approaches (Fabio Akita's ai-memory session-end markdown compilation stored in git; ctx-memory's three-layer compression to ≤500-token digests; Ninadnj's MCP engine with token-budgeted semantic recall claiming 93% recall at 78% fewer context tokens; agentmemory's AI-compressed injection). The compile camp explicitly argues raw record piles accumulate into token floods and stale notes 'recalled with full confidence', and several tools (Ninadnj's scaffold→engine, Conare's file-based→MCP framing) show a visible maturity gradient from Markdown convention to structured retrieval — independent corroboration of the accumulation cap the case already flags, and a preview of where a compilation layer would appear if Toucan matures.
Why it matters to Scott
Two independent builders have now shipped dated artifacts implementing Scott's zero-AI-capture + grep-what-churns doctrine over the exact Claude Code/Codex pair his search-conversations archive covers — a dated-receipts opportunity, not a repetition, since Tucaen and ad3mar arrived at his capture write-path from outside. The grounding's raw-capture-vs-compile field split, with the compile camp's 'stale notes recalled with full confidence' critique, is his capture-vs-compilation / Knowledge Graveyard framework playing out live; Toucan's missing compilation layer makes it the concrete foil for benchmarking capture-only grep against his transcript-distillation pipeline.
ip:source.code-what-transcript-why-ebookip:concept.capture-vs-compilationip:concept.search-what-churnsip:concept.knowledge-graveyardip:concept.transcript-distillationdev:project.search-conversationsdev:project.dev-wikiradar:activity-frames-agent-memory-compilerradar:docs-first-agent-continuity-protocolradar:hindcast-claude-code-session-recoveryradar:opencode-memory-persistenceradar:futureos-context-compaction-recall
queries asked of Scott's wikis
- zero-AI capture transcript-to-markdown doctrine
- grep what churns raw records vs compiled summaries
- Knowledge Graveyard Integration-Not-Retention memory accumulation cap
- capture-vs-compilation agent memory pipeline
- search-conversations project Claude Code transcript mining
- agent wiki curation layer distilling session logs
Measured heat
now 0 pts/hpeak 0 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 458h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p50 vs 1032 stories at the 336h mark (now 458h old) — ahead of agentgit-accountless-agent-handoffs (1.1x), behind anthropic-pentagon-blacklist-ruling (0.9x)
Evidence (3) — ⭐ canonical anchor
Interpretation history
2026-09-28T14:05:41Z
grounded: converges/high — Two independent builders have now shipped dated artifacts implementing Scott's zero-AI-capture + grep-what-churns doctrine over the exact Claude Code/Codex pair
2026-09-28T13:57:21Z
ad3mar's Rejected Futures independently ships the same transcript→Markdown, zero-token, hook-injected memory pattern, upgrading this from a single-builder artifact to a two-builder trend — Toucan is now the leading instance of an emerging pattern rather than a one-off, though it remains untested, unadopted, and attention-cold, and skeptical reception ('confusing context for Claude') voices exactly the append-only-capping failure mode Scott's own framework predicts.
2026-09-28T13:35:16Z
evidence attached: reddit.post.1wse83q — Rejected Futures is a parallel transcript-to-Markdown-claims memory tool with hook injection, evidence the zero-token transcript-memory pattern is a trend rather than a one-off.
2026-09-24T17:28:22Z
origin walked (opencode/cheap-glm, conf 0.88): anchor reddit.post.1wp270z -> echo.github.ee4c0051ca by Tucaen
2026-09-24T16:47:59Z
grounded: converges/high — Tucaen independently arrives at the capture half of Scott's own pipeline — deterministic, zero-AI transcript→Markdown writes grepped at session boot, cross-harn
2026-09-24T16:40:57Z
case created — Released cross-harness zero-token transcript-memory artifact posted by its builder in the hot agent-memory zone — a concrete claimable mechanism, not chatter.
Decision trace
- 10-10 20:06review_dormantscheduled targets exhausted or 28 quiet days
- 10-10 20:06drop_targetsquiet through full ladder or over cap 8
- 09-29 00:05repricead3mar's Rejected Futures independently ships the same transcript→Markdown, zero-token, hook-injected memory pattern, upgrading this from a single-builder artifact to a two-builder trend — Toucan
- 09-29 00:05groundTwo independent builders have now shipped dated artifacts implementing Scott's zero-AI-capture + grep-what-churns doctrine over the exact Claude Code/Codex pair his search-conversations archive c
- 09-28 23:35attachRejected Futures is a parallel transcript-to-Markdown-claims memory tool with hook injection, evidence the zero-token transcript-memory pattern is a trend rather than a one-off.
- 09-28 23:27propose_attachRejected Futures is a parallel transcript-to-Markdown-claims memory tool with hook injection, evidence the zero-token transcript-memory pattern is a trend rather than a one-off.
- 09-26 08:54review_screenjev screen: no material development (noul=0.17)
- 09-25 04:21sensor_dirtycomment_update
- 09-25 03:28promote_anchororigin walk conf 0.88
- 09-25 02:47groundTucaen independently arrives at the capture half of Scott's own pipeline — deterministic, zero-AI transcript→Markdown writes grepped at session boot, cross-harness over the exact Claude Code/Code
- 09-25 02:40createReleased cross-harness zero-token transcript-memory artifact posted by its builder in the hot agent-memory zone — a concrete claimable mechanism, not chatter.