It hits around week three.
You delegated the boring stuff to the agent. Then you delegated some of the interesting stuff. Then a bug shows up in a corner of the system you don't remember writing — because you didn't — and the agent has tried five fixes and none of them stuck.
You open the file. It feels foreign. You ask the agent what it does. It tells you. You half-believe it. You start re-deriving the structure from the source because the only documentation that exists is the commit messages, and you stopped reading those around PR #80.
Clew is for that moment. It's the how it works page someone should have been writing while the agent was shipping — except no one was, so we are.
Progressive disclosure of your codebase's how it works.
A living visual map of your system — modules, edges, what calls what — with
the why behind every change on main tucked into a hover.
Top-level shows the architecture. Drill down for detail. Hover any module for
its changelog: what changed, why, which agent did it.
A real diagram
The thing you'd sketch on a whiteboard if you still had the headspace to. Auto-maintained as PRs land — no hand-curating, no 48-file AGENTS.md pile.
The why, not the diff
Every commit on main contributes a sentence on what changed and why. Hover a module to see its decision history. Skip the PR archaeology.
Scrub the architecture
Drag the playhead to any point in your repo's history. See what the system looked like then. Useful when "it used to work" is the only clue you have.
There's a working one. Go poke it.
The diagram lives at app.useclew.dev. It's pre-seeded with an
auth subsystem so you can see the shape of the thing — graph,
hover-changelog, time slider, all wired up. Yes, the page is obviously
AI-styled. That's the joke. We're building the product, not the lander.
What you'll see: a 9-module graph with a glowing recently-touched node, a slide-in changelog panel, and a draggable time slider snapped to commits. It's the bones; the full thing auto-builds from your actual repo.
open prototype →Probably you, if any of this lands.
Clew is built for one specific person: a founder or CTO at a 2-15 person startup whose codebase is now mostly written by Claude, Cursor, or Codex. We're not trying to be a developer-tool-for-everyone. We're trying to nail this one slot.
You're the target if
- You ship with Claude Code, Cursor, or Codex most days.
- 30-70% of your codebase is AI-generated and accelerating.
- You've shipped for 2-12 months and the codebase is bigger than your mental model of it.
- You've felt that "wait, what does
orders/actually do anymore" moment. - You're hands-on technical but delegating more than you used to.
This isn't for you if
- You hand-write most of your code and want to keep it that way.
- You already maintain 40+
AGENTS.mdfiles and have a tooling pipeline for them. Respect — you've solved this another way. - You want a code-review bot. There are good ones; this isn't one.
- You want a documentation generator. We're capturing the why, not autogenerating prose.
Get on the list.
We're inviting waitlist signups into a private beta as the build catches up to the prototype. If you've felt any of the above, you're a useful person to have in the first cohort.