Pre-launch · Free for first 500 users

Be quality.

Your AI copilot for Windows apps.

JidoDebugger lets Claude, Cursor, Codex, GitHub Copilot, and other MCP-aware agents run, watch, and debug Windows desktop & CLI software on your machine — like a tireless pair-programmer that actually sees the screen.

JidoDebugger BugViewer with timeline, finding text, and FAIL badge
Three lines that say what JidoDebugger is
01

Windows desktop apps and CLI tools — driven by an AI, running on your own machine, with the results actually shown back to you.

02

Connects to Claude, Cursor, Codex, GitHub Copilot, and any MCP-aware agent. A Windows-only AI copilot, on purpose.

03

Spin the write → run → fix loop at AI speed, in pair with the model you already use.

// demo

See it driving a real app

Watch JidoDebugger explore the stock Windows Calculator in blackbox mode — division by zero, square-root residue, overflow, and error recovery, all checked through UIA, with the AI even self-retracting a false positive after cross-checking with a WGC screen capture.

Calculator · blackbox session Drive elements directly via UIA, reconcile AccessibleName vs. actual pixels with capture, and watch the AI retract its own false alarm — all in one session.
// features

What it does

Four pillars, all designed for AI-driven QA on Windows.

🔌

MCP integration

First-class MCP server. 45+ tools your agent can call: capture screenshots, query UIA trees, click, type, record findings as xUnit/NUnit/MSTest stubs.

🪟

UI Automation (UIA)

Find, click, type, drag, wait — by AutomationId, name, or live tree survey. Resilient to layout changes, with concrete recovery hints when something drifts.

💥

Crash & perf analysis

Crash watch, FPS sampling, resource & VRAM sampling, a11y audit, visual baselines. Closes the loop from “something feels off” to a reproducible finding.

🛰️

Distributed grid (preview)

Bring-your-own-device and bring-your-own-cloud patterns. Run tests across a fleet of real Windows machines from one MCP endpoint. No vendor pool, no surprise bill.

// in action

Real debugging, real apps

Live captures from a Microsoft Store reviewer's reject — reproduced, root-caused, and exported as a repro.zip in one closed-loop jidodebugger session.

JidoDebugger Monitor showing live tool calls, active session, and WhiteBox mode badge
Monitor Real-time tool-call stream, active session attached to the target app, white-box mode badge, stderr log.
JidoDebugger BugViewer with timeline, finding text, and FAIL badge
BugViewer Capture → click → finding timeline, root-cause finding text, FAIL badge, one-click "Investigate with Claude Code".
// pricing

Free for the first 500. First-year discount for early adopters.

Until dhq-boiler becomes a registered company, JidoDebugger is fully free for the first 500 users — individuals and small teams included.

Individual
Free during pre-launch
  • Refresh token auto-renews while online
  • Up to 7 days offline grace
  • MCP + GUI Monitor + BugViewer
  • 5-language UI (en / ja / zh-CN / zh-TW / ko)
Claim a free seat →
When dhq-boiler incorporates and paid plans go live, every pre-launch user keeps 20% off for the entire first year. No retroactive billing, no surprise lock-in.
// faq

Frequently asked

When does dhq-boiler actually become a company?
Target is within the current fiscal year. Until then, JidoDebugger is shipped under the personal name dhq-boiler. The 500 free seats are guaranteed regardless of when incorporation finishes.
What is the difference between Individual and Organization licenses?
Both are free during pre-launch. The main differences are offline grace (7 vs 30 days) and silent-install / SCCM-style deployment for orgs. Both auto-renew while you’re online.
What happens if my machine is offline for a long time?
JidoDebugger keeps working until your refresh token expires (7 days for Individual, 30 days for Organization). Reconnect once and the timer resets.
What is a refresh token? Do I need to manage it?
It’s an automatic background mechanism. The installer stores it; the app refreshes it whenever it talks to the activation server. You never need to copy or paste anything by hand.
How is my data handled?
JidoDebugger runs locally on your Windows machine. Captures, UIA snapshots and findings stay on your disk. Outbound traffic to dhq-boiler is limited to license refresh and minimal anonymized telemetry (startup events and similar — on by default, opt-out in the Controller's Settings). Source code is never uploaded.
How do I cancel?
Uninstall via the installer’s Uninstall mode, or `JidoDebuggerSetup.exe uninstall --silent`. Your license seat is released and you’ll never be billed for pre-launch use.