Taru is shared team memory for Claude Code and Cursor. It captures what agents learn while you work, curates it into sourced memories, and hands that knowledge to every teammate’s agent at session start.
The problem
01
Agents forget everything they learned when the session ends.
02
What does survive is scattered across CLAUDE.md files, laptops and transcripts.
03
So teammates and their agents rediscover the same gotchas, one session at a time.
Taru gives those lessons one home: a curated, sourced memory that every teammate’s agent reads before it starts work.
How it works
01 · Capture
Hooks in Claude Code and Cursor note the decisions, fixes and gotchas your agent works out. You keep working the way you already do.
02 · Redact
Before a note leaves your machine, keys, tokens and passwords become [REDACTED]. The server checks every note again when it arrives.
03 · Curate
Notes from many sessions are merged into memories with a kind, a confidence score and links to their sources. Disagreements are flagged, never overwritten.
04 · Recall
When a teammate opens a session, their agent gets a short briefing of the memories that matter for that repo, each with where it came from.
What a memory looks like
A memory says what it is, how sure Taru is, and which sessions it came from. When teammates’ notes disagree, both are kept and the memory is marked disputed.
Trust and control
Capture is off until you and your project both turn it on, and you can stop it at any time.
On-device redaction
Keys, tokens and passwords are replaced with [REDACTED] on your machine, before anything is uploaded.
Two-sided opt-in
A project opts in, and so does each person. Nothing is captured until both have said yes.
taru pause
One command stops capture on your machine until you turn it back on.
.taruignore
Files, folders and patterns listed here are never read or captured.
Server re-scan and quarantine
Every note is scanned again on arrival. Anything that still looks like a secret is quarantined instead of becoming memory.
Append-only audit log
Every capture, edit and removal is recorded in a log that can be added to but not rewritten.
Harnesses
Memory is shared across harnesses, so a teammate on a different tool gets the same briefing.
Supported today
Claude Codecapture + recall
Cursorcapture + recallComing soon
Codexcoming soon
Antigravitycoming soon
OpenCodecoming soon
Zedcoming soonWe’re working with a small group of teams who use Claude Code or Cursor every day.
FAQ
Taru is shared team memory for AI coding agents. It captures what Claude Code and Cursor learn while your team works, curates it into sourced memories, and hands them to every teammate’s agent at the start of a session.
Claude Code and Cursor today. Memory is shared between them, so a teammate on Cursor gets what a teammate learned in Claude Code. Codex, Antigravity, OpenCode and Zed are planned but not supported yet. The Taru command-line tool also includes an MCP server, so an agent can search team memory on demand.
The decisions, fixes and gotchas your agent works out during a session, along with the files they relate to. Capture runs only in projects that have opted in, for people who have opted in, and skips anything in .taruignore.
Notes are redacted on your laptop, then sent to Taru’s hosted service, where your team’s memories are stored and served to each teammate’s agent.
Only redacted notes leave your machine, and only from projects and people that have opted in. Keys, tokens and passwords are replaced with [REDACTED] on your machine before upload, and the server scans every note again on arrival and quarantines anything that still looks like a secret. The queries agents use to search memory are stored only as keyed hashes.
Taru compares notes across sessions and teammates. A memory’s confidence rises as more sources agree, and every memory links to the sessions behind it, so anyone can check where it came from.
The memory is marked disputed. Both notes are kept with their sources, nothing is silently overwritten, and agents see the disagreement instead of a single confident answer.
Taru is working with a small group of design partners. Use the form on this page or email join@devtraverse.com.
Run taru pause to stop capture on your machine. You can also withdraw your own opt-in, or a project can opt out for everyone. Each of these is recorded in the audit log.
