Launching today

Titen

Launching today

Open-source agent memory with receipts. No API key, no LLM.

1 follower

Open-source agent memory with receipts. No API key, no LLM.

1 follower

Visit website

LLM Memory

Ask your agent "why do you remember that?" Titen answers with receipts: every memory keeps its source, who may read it, and the evidence that contradicts it. • No API key, no LLM, no embedding provider, 0 deps • Drop-in for the MCP reference memory server: same 9 tools, auto-import • titen audit finds duplicates, recall loops, leaked secrets and stale memory in any store • Bun + SQLite or Cloudflare Workers + D1, Apache-2.0

Free

Launch tags:Open Source•Developer Tools•Artificial Intelligence

Launch Team / Built With

Maker

📌

Hey Product Hunt 👋 I'm Rama, maker of Titen. Try this: ask your AI agent "why do you remember that?" Most memory layers can't answer. They hand back a nearby paragraph and a similarity score. That's vibes, not memory. And once a team of agents shares that store, nobody can tell what's current, who was allowed to see it, or which agent quietly overwrote whom. Titen is built on one rule: every memory keeps its receipts. → Where it came from: raw observations with a content hash and a timestamp → Who may read it: org / project / subject scoping runs BEFORE retrieval, not after → What contradicts it: disputes stay disputed, both sides kept, never averaged Three things that make it different: 1. It needs nothing. No API key, no LLM, no embedding provider, zero runtime dependencies. One command (needs Bun 1.2+) and your agent has memory over MCP: npx titen-memory mcp 2. It's a drop-in for @modelcontextprotocol/server-memory. Same 9 tool names, your existing graph is imported on first run. Underneath, search becomes real ranked FTS5 instead of String.includes. 3. The benchmark publishes our losses. On LongMemEval-S (pooled, n=500) the zero-provider lane scored 0.246 recall@1 vs 0.182 for Mem0 OSS (infer=False). Two of our own pre-registered falsifiers also fired against us. They're printed on the chart, not hidden: titen.dev/benchmark 🧾 Launch-day challenge: the Memory Audit Point it at any agent memory store (Titen, the MCP reference server's memory.json, or a Mem0 export): npx titen-memory audit ./memory.json Read-only, offline, nothing uploaded. It counts exact duplicates, near duplicates, recall loops, leaked secret patterns and stale entries, with per-item evidence you can check by hand. We ran it on Titen's own store first: 17.9% duplicates, 96.7% stale. Published in the repo. Your turn. Drop your numbers below 👇 Honest notes: Titen is pre-1.0 (pin an exact version). By default you author the claims; model-assisted extraction ships but stays gated until a model passes 90% on our eval. And on huge unscoped stores, compile latency still crosses our own 250 ms line. Why "Titen"? It comes from the Javanese "niteni": to notice, and to keep what you noticed. The logo is kawung, a four-petal batik motif. Its four petals stand for tenant, subject, agent and run. I'd love to hear: what's the one thing you wish your agent could explain about its own memory? GitHub: github.com/RamaAditya49/titen

Report

9d ago

Forum Threads

p/titen

•

5d ago

How do you find out why your AI agent "remembers" something?

Hi Product Hunt, I'm Rama, maker of Titen. We launch here on October 20.

The problem I keep hitting with agent memory isn't retrieval, it's the write side. Stores quietly fill up with duplicates, copies of the agent's own output, stale facts and the occasional pasted secret. One public audit of a production store found 97.8% of 10,134 entries were junk after 32 days. When I ran the same kind of audit on Titen's own store, it found 17.9% duplicates and 96.7% stale, so I'm not pointing fingers.

Titen is built around receipts: every memory keeps its source, who may read it, and the evidence that contradicts it. It runs with no API key, no LLM and no embedding provider (Bun + SQLite, or Cloudflare Workers + D1), and it's a drop-in for the MCP reference memory server: same nine tools, your existing memory.json imported on first run.

You can audit any store today, even one Titen doesn't own. It's read-only, no network, no upload:

View all