Hook-based session capture
wrud attaches to an agent’s lifecycle hooks and streams prompts, tool calls, file edits, and replies as they happen, so sessions are captured without manual logging.
wrud
wrud is a local-first, open-source recorder for AI-agent sessions. Review activity, track model and token use, and turn repeated mistakes into shared lessons.
What wrud is
wrud, short for What R U Doing, is a local-first, open-source recorder for AI-agent sessions. It is designed to help individuals and teams see what their agents actually did, how models and tokens were used, and where repeated mistakes can be turned into reusable lessons.
The product runs on a local Node server and one SQLite file, with no account and no egress described on the site. Claude Code and Cursor are supported directly, and other agents can send data through the local API.
Core features
Plain-language recaps
A background process reads the run data and writes a plain-language recap of what actually happened, rather than only showing raw counts or transcript fragments.
Model and token visibility
The site highlights per-model spend and token totals, helping you spot when a costly model was used for simple work and where context usage is concentrated.
Session history
Recorded sessions include agent, model, events, and token spend, giving a queryable history that can be reviewed after the session ends.
Local-first storage
wrud runs locally with a Node server and one SQLite file, with no account and no egress according to the site copy.
Out-of-the-box and API-based integrations
Claude Code and Cursor are supported out of the box, and other agents can connect through the local API.
Where wrud fits
Individual session review
Use wrud to review an agent session after the fact, including the models used, token spend, and the recap of what the session actually did.
Team learning and policy
For engineering teams, wrud can roll up sessions across people and projects so repeated errors become shared lessons and model policy instead of isolated incidents.
Cost and model review
When a large model is used for a trivial task, wrud’s per-model cost view can help a team right-size its next run and reduce unnecessary spend.
Non-desktop agent runs
If you are running agents in CI, on a remote box, or in a cloud environment, wrud’s hooks and local API are meant to capture those runs outside a single desktop app.
Onboarding with captured lessons
For onboarding, wrud can preserve lessons from previous sessions so a junior teammate can inherit proven guidance instead of relearning the same mistakes.
Pros and Cons
Pros
- Local-first design with data stored on your machine.
- Open-source and MIT licensed.
- Captures prompts, tool calls, file edits, and replies through lifecycle hooks.
- Provides a plain-language recap and a way to surface recurring mistakes as lessons.
- Supports both individual sessions and whole-team rollups when self-hosted.
Cons
- The public pages provide limited detail about deeper workflow features, security controls, and supported integrations beyond Claude Code, Cursor, and the local API.
- Cursor is described as having model and action capture, with cost capture marked as coming soon on the site.
FAQ
How do I set it up?
You can start the app with `npx @wrud/cli`, then connect in the browser and run hook installation for your agent. The site also offers a paste-in prompt that lets Claude Code or Cursor wire wrud up for you.
Is wrud useful for teams?
wrud is positioned for individual use and team rollups. It can show sessions, model calls, tokens, spend, and lessons across a whole team when self-hosted on your own box.
Which agents does it support?
The source pages show support for Claude Code and Cursor out of the box. For other agents, wrud exposes a local API and says anything else can stream in that way.
What does it record?
wrud captures prompts, tool calls, file edits, replies, model usage, token spend, and a plain-language recap of the session. It turns repeated mistakes into lessons you can feed back to the agent.
Does data leave my machine?
The product pages say capture is local-first, runs on a local Node server and one SQLite file, and that no account or egress is required. The site also says it is MIT licensed.
Quick Facts
- Category
- Developer Tool
- Product type
- Local AI-agent session recorder
- Primary users
- Individuals, team leads, and platform leads
- Platforms / runtime
- Local Node server with SQLite storage
- Integrations
- Claude Code, Cursor, and any agent via local API
- License / access
- Open-source, MIT licensed
wrud Alternatives
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads in Firecracker micro-VMs with private networking and SDK, CLI, or MCP control.
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repos and verifies changes with compilers, debuggers, sanitizers, and tests.
hob
hob is an independent workspace for coding agents, with local control over sessions, terminals, history, routing, and follow-up work.
Manta AI
Manta AI is an autonomous web app testing tool that maps app behavior, catches regressions, and generates tests from a URL, no scripts or selectors needed.
Redline
Redline is a budgeting tool for Claude Code that paces sessions by time, tokens, cost, or plan percentage, helping them end with a usable result.
SonOf
SonOf connects to your repo and PM tool, audits your codebase, and turns approved work into shipped tickets with senior engineering review.