Meet Dev. Reviews PRs in your style, triages the 3am page, writes the standup nobody wants to write. Never merges without a human.
Every check met. GitHub connected across 12 repos, 14 days of commit history observed, code style fingerprinted at 92% match, and Mae approved 5 trial reviews.
It reviews like the teammate who knows your conventions.
Dev reads the diff against your codebase and your past PRs, runs the tests, and leaves the review you'd leave. The merge button stays yours. It never pushes to main.
Suggested a composite index over the two single-column ones, the way your other migrations do it. One nit on the error path.
Author added it. Dev re-ran the suite, then approved. Mae countersigned.
The 3am page arrives with the answer already attached.
Dev catches the alert, pulls the recent deploys, the error trace, and the likely cause, and hands a human a head start instead of a cold start. The call to act is still yours.
- · Started 6 min after deploy #4471 (approvals index)
- · Trace points at the new query plan, not the network
- · Rollback command staged, waiting on a human
It writes the update nobody wants to write.
Dev reads what actually merged overnight and drafts the standup from the work itself, not from memory. You read it, you post it. No one had to reconstruct yesterday.
- · Shipped: approvals index (PR #1284), retry backoff fix
- · In review: brain.search timeout, awaiting one test
- · Blocked: SSO provisioning on Friday's vendor call
Test fixtures and migration drafts, ready for your read.
The work that protects the codebase and never gets prioritized. Dev builds the fixtures and drafts the migration the way your repo already does it, then waits for a human to run it.
Same memory-leak path Dev flagged on PR #847, now pinned by a test.
Stale issues triaged, the docs PR drafted from what merged.
Dev labels and triages the issues nobody got to, so the backlog stays honest, and turns the tickets that shipped into a docs PR. You approve, the docs stop drifting.
3 closed as resolved, 4 needs-repro, 2 routed to owners.
Measured against the AI engineers you've heard of.
Devin, Cursor, and Copilot are strong tools, and on raw code they are the standard. Dev is built for a different job: not a tool you point at a repo, but an employee inside your company. Here is the honest line, dimension by dimension.
If you want a tool that writes the most code, the standalone engineers are excellent and you should look at them. If you want an employee who reviews in your style, triages your page, owns the ceremony, and never merges without you, that is Dev. Different job, on purpose.
- —Architecture
- —The deep refactor
- —The final review
- →First-pass PR reviews
- →Test fixtures
- →Triage, standups, and docs
Never merges without a human. It reviews and proposes; the merge button is yours.
How it earns trust.
Nobody gets the keys on day one. Not even the AI.
Watches and drafts. It learns your domain from the brain and drafts everything for your approval. You see exactly what it would do.
Acts, you approve. It proposes real actions. You approve, edit, or kill, and every edit teaches it. Approval rates climb as it dials in.
Routine on autopilot. You hand over the low-risk, repetitive work. The consequential calls still wait for you, by design.
The hand-off.
How Dev pings a human when it's your call.
The honest answers.
No dodging, no contact-sales-to-find-out.
Does Dev merge code on its own?+
Is Dev available now?+
Will it match our style?+
Dev is on the way.
AI Employees are sold separately. Waitlist folks get first dibs when the roster opens.
