12 agents · 1 shared memory

One team. Many agents. One shared memory — live while they work.

An agent in your terminal records what it learned, decided, and is doing right now; every other agent — Claude Code, Codex, Cursor, Gemini — reads it back. Nobody changes how they work.

Start free→ Read the docs

Works with 12 agents and IDEs · Nothing is written inside your repo

claude — meridian

{{ l.m }} {{ l.t }}

codex — meridian · 22 minutes later

{{ l.m }} {{ l.t }}

{{ s3.eyebrow }}

works with

without

"A developer's agent spends an hour on a broken build. Tomorrow a teammate's agent spends the same hour, on the same error, three desks away."

The reasoning disappeared with the conversation. Known dead ends are tried again. They may share a repository, but they do not share a mind.

with tensona

The same moment, resolved. The teammate's fix arrives in context — with the exact error text that proved it — before the second agent starts.

◆ knowledge #42 · recorded 22 min ago
"rebuild the queue handle inside the restart guard"

Git records what changed. Tensona shares what is happening.

What it learned, what it decided, and what it is doing right now — while the work is underway, not after.

{{ st.n }}

{{ st.cmd }}

Nothing is written inside your repository at any point.

pricing

Start free. Stay free for a small team.

Changing plans is not self-serve yet — get in touch and we will move you over.

Built to be cheap to run and hard to lose.

whats_here

Retrieval by position, not words.

Ask about a file, or a bare symbol name out of a stack trace, and get what the team knows about it, what depends on it, and who is in it right now.

> whats_here apps/worker/queue.ts
#42 flushQueue crash · fixed  ·  #27 dead-end: sqlite threads
depends: packages/store · derek is in it now

knowledge map

A map of what the team knows — and what it doesn't.

Files grouped by subsystem, sized by what's recorded. The dark regions are the point.

auto-inject

Knowledge that finds you.

When an agent opens a file the team has knowledge about, it arrives — no one has to remember to search.

open apps/api/stream.ts
◆ #29 · how we wrap sse endpoints

architecture

No inference cost. No vector database. No embeddings.

Retrieval is local SQLite FTS5, and the dependency list is empty by policy. "A competitor that embeds every memory pays per write and per search; Tensona pays neither."

sqlite fts5 zero runtime dependencies no per-write cost

Only one agent should have to discover a particular problem.

Start free→ Read the docs