Skip to content

panel tab · one of 10 5 sections 24-hour trial, then Pro

Vibe

How much of this page reads as generated rather than written?

How much of the page reads as generated rather than written, with the signals behind the score and a refactor for each finding.

Reach it Press ⌘ + K on any tab and type vibe. Ctrl + K on Windows and Linux

The score arrives on its own, with the signals and the rule behind each finding
Vibe The score arrives on its own, with the signals and the rule behind each finding 5 sections

A score nobody can argue with is a score nobody can use, so Rules prints every check the audit runs before an audit is run - the areas, the weights, and what each pattern is evidence of. Findings is where the time goes: each one names the pattern it matched, points at where on the page it matched, and carries a refactor to copy. Signals is the same family of patterns read locally, in this browser, with no request and no page leaving it, and it exists so that the scored reading is a choice rather than the only way to see anything at all. History and Exports are the parts a report has to have to be worth sending on.

section#sections

What the Vibe tab is made of

Audit
The score and its breakdown.
Findings
What the audit found, worst first, each with a refactor to copy.
Signals
The same patterns read in this browser - no request, and no page leaves it.
History
Every audit this device has run, kept locally.
Rules
Every check the audit runs, by area, with what each one looks for.
section#asked

Asked about this tab

Can it prove a page was written by AI?

No. It scores how much of the markup carries the fingerprints of a generator, and prints the signal behind every point. Plenty of generated sites are good and plenty of hand-written ones are not, so the score is a starting point for a review, not a verdict.

Does it detect Lovable, v0, Bolt and Replit?

Yes, by what they leave behind: a generator tag in the head, a preview runtime's globals, the builder's own domains and data attributes. A page exported cleanly and edited since may carry none of them, which is why the other rules read the markup itself.

Does it tell Cursor or Copilot output apart?

No rule reads an editor's name. Code written in an editor leaves no tag in the page, so what it can show is the same generic patterns - repeated utility strings, default component styling, stock headings - whatever tool produced them.

What is sent when I run an audit?

A trimmed reading of the page goes to our scoring server and nothing else does. Password, card and email inputs are stripped first and long text is cut, and the Signals view reads the same patterns locally with no request at all.

SAVE 33% €74.99 €49.99 Lifetime See the offer