your verification tool.
chekd gives you a second set of eyes: it walks your app, surfaces the broken or ugly parts, and tries to learn your taste with every decision.
npx chekd <url>
Paste into Claude, Codex, Cursor, Antigravity. full setup →
Generic design audits tell everyone the same thing. chekd learns what bugs you.
Every time you correct a finding, chekd cements your taste. The longer you run it, the more irreplaceably yours it becomes — a loop no off-the-shelf audit can copy.
It walks your app
chekd opens the cockpit and walks your shipped app, surfacing dead, broken, and ugly findings as cards.
You correct it
Fix it, snooze it, dismiss it, or move to the next. Each call is you teaching chekd what you actually care about.
It cements your taste
Every correction is remembered. The noise you ignore quiets down; the things you care about get sharper.
The next chekcheck is yours
Run it again and it’s quiet where you said to be quiet — and louder only where you’ve cared before. Sharper every chekcheck.
Every chekcheck, it nags a little more like you.
chekd gets more yours the longer you use it — until skipping it feels like shipping with your eyes closed.
One slider, four stops.
Choose how much is you and how much is chekd — from quietly logging while you drive, to fixing and re-chekingre-checking for you. Land anywhere; every stop hands the calls back to you.
Share live
You drive and talk; chekd rides along in the browser, logging what it sees — every click observed, every error caught, your narration pinned to the moment you said it. It changes nothing. No fix, ever, at this stop.
Scan live
chekd drives; you review. It walks your app and surfaces findings as cards — you snooze or dismiss, and there’s no fix affordance at all. The first hand-off on the trust ramp.
Fix live
chekd drives; you correct and dispatch. Fix it writes a real fix on a qa/ branch in your own repo — main never moves; you review and merge it yourself.
chekd ON chekd Plus
Correct, then unleash: you approve the fixes; chekd applies them, re-walks, and verifies — bounded, never “until perfect.” Anything new it finds comes back to you.
More chekd never means less you.
Every stop up the ramp is something chekd does for you, never instead of you: it only fixes what you corrected, it re-cheksre-checks what it touched, and whatever it finds next lands back in your queue.
Paste one line. ChekCheck your app or PR. Kill the slop you shipped.
chekd is the verification cockpit for apps your AI wrote — it walks the running app, maps changed files into a test plan when a repo or PR is available, and keeps you in the chair for every fix.
Paste one line
Drop npx chekd into your AI setup or your terminal. No chekd account, no upload to a chekd service, no config to wade through.
ChekCheck the surface
chekd opens the cockpit and walks your shipped app. Add a repo, branch diff, or GitHub PR when you want changed-file context too.
Dispatch a disposition
Each finding is a card: fix it, snooze it, dismiss it, or move to next. You stay in the chair the whole time.
You are helping me run chekd on my web app. chekd is a local-first verification tool: it opens a real browser, walks a running web app, and reports the dead, broken, and visually-off spots as reviewable cards. Nothing is uploaded to a chekd server.
Do this:
1. Make sure my app is running (a dev server or a deployed URL), then run:
npx chekd@latest <MY_APP_URL>
Replace <MY_APP_URL> with where my app is served, e.g. http://localhost:5173 or https://myapp.com (type the address bare, no angle brackets).
2. It runs on Windows, macOS, and Linux via Node (Node 18+). Use my normal shell (PowerShell, Terminal, or bash).
3. Expect about two approval prompts: one to let npx download the chekd package, and one the first time it downloads its browser (~100MB, one-time). Approving them is normal.
4. When it finishes it prints a local http://127.0.0.1:<port>/ cockpit URL and keeps running. Open that URL so I can review the findings, then stop it with Ctrl+C when I am done.
If it fails:
- "node" or "npx" not found -> Node is not installed. Install Node 18+ from nodejs.org, reopen the shell, and re-run.
- a browser / Chromium / Playwright launch error -> run: npx playwright install chromium then re-run the chekd command.
Report the findings back to me as a short list (what is dead or broken, and where). Do not fix anything until I say so.
Built to be yours — and to stay yours.
Three commitments shape every part of chekd, from the first run to the thousandth.
Accessible to all
Real value at $0, forever — no required API key, no expertise gate. Plain language, never gatekeeping.
Make it your own
Dark + light and three themes on day one. Choose Claude, ChatGPT, local Ollama, or no model. Set the autonomy yourself — from watch-only to fix-it-for-me.
Compounding
Every use makes it more yours and better. It learns your taste, your corrections compound, and the next chekcheck is already sharper — the flywheel.
Choose the model path. See the boundary.
Nothing cloud-backed is ever selected for you.
Your CLI, your account, your call — chekd never picks a cloud for you.
chekd keeps findings, corrections, screenshots, and history local — never uploaded to a chekd service.
A model-backed action sends only what it needs to your selected provider (Antigravity is text-only). Provider terms apply to every cloud route.
Run a local model and nothing leaves at all. That’s the genuinely airgapped path — zero bytes off your machine.
Free forever. Pay for the model-backed DESIGN pass and bounded fixes.
Everything objective is free. Free remembers and reuses your decisions; Plus adds new DESIGN observations and safely applies and re-checks fixes.
unlimited local chexchecks — no account, no card, no upload
- ✓Unlimited local chexchecks — no quota, $0 every time
- ✓Share & Scan autonomy — you drive, or chekd walks and flags
- ✓FUNCTION · CONTENT · LAYOUT lenses — dead clicks, “undefined” text, broken layout
- ✓PR/diff-aware review planning + baseline runtime security
- ✓Policy profiles & local evidence exports
- ✓Claude, ChatGPT, or local Ollama — cloud provider plan terms apply
- ✓Corrections, priors & taste controls — your decisions stick and reorder future findings
Free is the floor, not a trial.
Founding Member price — get in at launch and you keep this rate when the price rises later
- +Model-backed DESIGN taste pass — visual observations from the provider you choose
- +FULLFIX apply + re-chek — fixes land on a
qa/branch; you review and merge - +Fixed-site preview — inspect the isolated fix before merging
- +chekd-ON — the highest-autonomy loop, bounded
Drop your email — we’ll ping you at launch.
A trusted copilot, never a critic.
Subjective findings are suggestions; only deterministic ones get stated flatly. Honest about limits — and it never judges the work you made.
✓ What it says
- The “Pay now” button doesn’t fire — want me to wire it up?Concrete, names the spot, hands the decision back.
- This label is hard to read on that surface. Bump it one step?Plain language a non-technical builder gets.
- This PR drops a defensive header on checkout. Want the evidence pack?Specific to the changed surface; no scare language.
- You dismissed this kind of thing before — want it quieted for good?Shows it’s learning you, chek over chekcheck over check.
- I might be wrong here — ignore if this is intentional.Honest about limits; never authoritative.
✗ What it never says
- Critical accessibility violation detected. Fix immediately.Alarmist, gatekeeping, treats a finding as a verdict.
- Your design is bad. Here’s what a real designer would do.Judges the creative work. Never do this.
- 17 issues found across 4 severity tiers (see dashboard).Noisy, jargon-heavy, dumps work on the user.
- SOC 2 compliant after one scan.False compliance claim. chekd can produce evidence; it cannot certify you.
- AI-powered QA automatically fixed your app.Overrides the builder; hype, not honesty.