Uncaught exception after “Inspect connection”
Error: Connection inspector crashed at HTMLButtonElement.onclick (http://127.0.0.1:65299/dashboard:22:330)
An unhandled page exception was observed, not inferred from appearance.
SMALL APP. HEALTHY SKEPTICISM.
Your AI says it’s done.
Heckle it.
A second opinion for your localhost.
Find the broken clicks, failed requests, and screens your agent missed.
Windows 10/11 x64 · macOS coming soon · checking current price · no subscription
Actual desktop capture. A recorded run against our intentionally broken benchmark app.
2pages
4UI states
7interactions
3viewports
2findings
THE HANDOFFDone coding.
Done coding.
Not done checking.
Looks right isn’t the same as works right.
That’s where a little skepticism helps.
YOUR CODING AGENT
Implementation complete.
All requested changes done.
01
Paste localhost.
No test scripts. No configuration.
Just the app you’re building.
02
Let it poke around.
Pages, clicks, requests, small screens.
The parts worth a second look.
03
Fix. Heckle. Repeat.
Give the evidence to your agent.
Run it again after the fix.
EVIDENCE, NOT VIBESA bug report.
A bug report.
With the receipts.
Not “something went wrong.” The exact click, the screen, and the request that failed. Everything your agent needs to try again.
2 findings from a real run.RECORDED BENCHMARK RUN
“Delete workspace” was skipped.
Safe Mode stayed on.
↑ SELECT AN ISSUE. INSPECT THE EVIDENCE.Real benchmark findings. This page does not scan your app.
A SECOND PAIR OF EYESThe obvious stuff.
The obvious stuff.
Until you miss it.
Built around the failures that hide behind “looks good on my machine.”
IMPLEMENTED IN V1The things you click
Buttons, forms, navigation, dead links.
The things you don’t see
Console errors, failed requests, broken assets.
The screens you forgot
Responsive overflow and clipped controls.
A focused second pass. Not a guarantee that every bug is caught.
YOUR MACHINE
HECKLE
localhost
LOCAL BY DESIGNYour app.
Your app.
Your machine.
Browser checks run on your machine. Your unreleased app doesn’t need to be hosted on a remote QA service. No account or AI API key.
Desktop first. Local execution. Fewer moving parts.OWN YOUR SECOND OPINIONOne app.
One app.
One-time price.
Yours to keep.
No subscription for local HECKLE.
One less thing on your monthly statement.
HECKLETHE DESKTOP UTILITY
HECKLE 1.xLAUNCH STOCK CHECKING
—USD / one time
The complete local utility. Nothing held back.
First 100 at $7 · next 200 at $9 · then $19 standard
- Unlimited local runs
- Screenshot, console and network evidence
- Reports to hand back to your coding agent
- Windows 10/11 x64 · all 1.x updates
THE PRACTICAL QUESTIONSWhy an app?
Why an app?
Because localhost is local.
The website is where you buy HECKLE. The desktop app is what can reach your localhost, launch a controlled browser, use your prepared session, and keep the evidence on your machine.
How many computers does one key cover?
One at a time. Deactivate the old computer in Settings, then use the same key on the new one.
Does HECKLE need to stay online?
Only for activation and occasional validation. After a successful check, scans keep working offline for fourteen days.
What platforms are supported?
HECKLE launches first on Windows 10 and 11 x64. Native Apple Silicon and Intel Mac builds are planned after the Windows release is verified in production.
What leaves my computer?
License checks and update requests. Scan targets, screenshots, browser sessions, reports, and application data stay local. Diagnostic evidence is attached only when you explicitly include it.
What is the refund policy?
Ask within fourteen days of purchase. We will refund the payment and deactivate the associated key.
Your agent finished coding.
HECKLE starts there.
Install from the Microsoft Store. Activate before your first scan.
Install from the Microsoft Store when the Windows release is live, then activate before your first scan. macOS is coming soon.