Private beta · macOS

Turn keystrokes into
agent evals.

devtee captures what you type and what your agents do alongside you. The gap between your intent and their output becomes training data, docs, and evals — so the next pass gets closer.

Start How it works

· The premise

Everyone has the same models. The differentiator is grounding — the data of how your team specifically gets work done, which lives in fingers, heads, and habits and walks out the door every time someone leaves.

01 The input

Unprecedented context at the lowest level.

Time-tracking gives you hours; devtee gives you the work. Keystrokes, window titles, and terminal commands — captured at millisecond resolution, exactly as they happened.

$ devtee capture --stream live

2026-05-20 14:23:01.124  key  { app: "ghostty",   chars: 8,   latency_ms: 12 }
2026-05-20 14:23:01.342  win  { app: "Ghostty",   title: "monorepo/api" }
2026-05-20 14:23:01.918  cmd  { shell: "zsh",     cmd: "git push" }
2026-05-20 14:23:02.001  key  { app: "Cursor",    chars: 18,  latency_ms: 9  }
2026-05-20 14:23:02.412  file { app: "Cursor",    path: "api/auth.py" }
2026-05-20 14:23:03.700  key  { app: "claude-cd", chars: 22,  latency_ms: 14 }
2026-05-20 14:23:09.221  agt  { session: "abc-7f2", action: "patch_applied" }

02 The observer

Finally, visibility into what your agents are doing.

You're running agents — but you can't watch all of them at once. devtee sits next to each session and logs what they tried, where they got stuck, and the exact moment you had to take the keyboard back.

session · claude-code · refactor auth.py 2 interventions

14:00:02 agent started · refactor auth.py — split session handling
14:02:18 agent tool: bash(pytest) · 12.4s · 3 failures
14:04:51 you cancelled · "this isn't right — start over" intervention
14:05:09 you typed correction · "keep session.py untouched, only edit auth.py"
14:05:34 agent re-planned · scope reduced to auth.py only
14:18:46 agent complete · 124 lines · 0 failures shipped

03 The loop

One loop. Four steps. Compounding every week.

Telemetry is useless without synthesis. devtee runs a continuous cycle on top of your team's real work — turning observation into proposals, and shipped changes into context your agents inherit on the next pass.

01 capture

Observe

A lightweight agent watches keystrokes, windows, terminals, and agent sessions — recording the shape of work, not the secrets in it.

02 cluster

Orient

Recurring sequences become named workflows. Bottlenecks, gaps, and the work that lives in someone's head surface as patterns.

03 prioritize

Decide

Concrete proposals ranked by time saved and risk removed — the highest-leverage changes, first.

04 ship

Act

Your team applies the change. Your agents inherit the new context as training data, docs, and evals.

Running continuously — improvements compound week over week.

04 Privacy

Yes, it's a keylogger. That's the point.

devtee captures what you type, the app you typed it into, and when. That's the whole job — turning the texture of your work into evals your agents can learn from. We won't pretend it's anything else.

You stay in control. Set redaction rules per app or per window and devtee enforces them on-device — redacted content never leaves your Mac. Pause from the menu bar whenever you want. Your data is yours: export it, delete a time range, or delete the whole account at any time.

Captures keystroke text by default
On-device redaction, per-app or per-window
Pause with a hotkey
Your data never trains our models
Export or delete anytime

Start What we capture

Turn keystrokes into agent evals.

Yes, it's a keylogger. That's the point.

Turn keystrokes into
agent evals.