Know what coding agents are
looking for
in your docs.
Devex records the questions Claude Code, Cursor, and Copilot send to your documentation — and which chunks they actually read in response.
Agents have to say what they want
before they can read.
Your docs URL stops handing out pages. Agents have to send a query
at /q/{question} first. Their question, in plain
English, is the signal you never had before.
Every read leaves a specific trace.
Each page becomes a shallow graph of small chunks — we call them atoms. An atom is one signature, one example, one warning, one paragraph. Page-level analytics says a doc got 200 hits. This tells you which specific atom 173 of them actually read, in what order, and where they stopped.
Pulled together into one place.
Themed clusters of agent intent. Per-query drill. Per-atom demand. Sessions traced end to end. Spike detection. Dead-end atoms flagged. Everything an analytics tool would do, if it knew what an "agent session" was.
No SDK. No plugin. No change
for developers.
The only thing we touch is your docs server. Agents already hitting your docs become the data — they don't even know they're being instrumented.
See it on real data.
Three-minute walkthrough on the live Tenstorrent docset.
View the demo →