smriti

<p align="center">
  <img src="assets/banner.png" alt="Smriti — Shared memory for AI-powered engineering teams" width="600" />
</p>

<p align="center">
  <em>An exploration of memory in the agentic world</em>
</p>

---

The agentic world is moving fast. Every team is shipping with AI — Claude Code,
Cursor, Codex, Cline. The agents are getting better. The tooling is maturing.

But there's a gap nobody has fully closed:

> **Agents don't remember.**

Not from yesterday. Not from each other. Not from your teammates. Every session
starts from zero, no matter how much your team has already figured out.

This isn't just a developer experience problem. It's a foundational gap in how
agents work. As they get more capable and longer-running, memory becomes a
prerequisite — not a feature. Without it, knowledge stays buried in chat
histories. Teams re-discover what they've already figured out. Decisions get
made twice.

The answer, I think, mirrors how our own memory works:

> **Ingest → Categorize → Recall → Search**

That's the brain. That's what **Smriti** (Sanskrit: _memory_) is building
toward.

---

## The Problem, Up Close

Here's what the gap looks like in practice:

| Monday                                                        | Tuesday                                             |
| ------------------------------------------------------------- | --------------------------------------------------- |
| Your teammate spends 3 hours with Cursor on an auth migration | You open a fresh session and ask the same questions |
| Cursor figures out the right approach, makes key decisions    | Your Cursor has no idea any of that happened        |
| Architectural insights, debugging breakthroughs, trade-offs   | All of it — gone                                    |

The result:

- **Duplicated work** — same questions asked across the team, different answers
  every time
- **Lost decisions** — "why did we do it this way?" lives in someone's closed
  chat window
- **Zero continuit