# JidoDebugger
> Windows app AI copilot delivered as an MCP server. Adds 45+ tools that
> let Claude, Cursor, Codex, GitHub Copilot, and other MCP-aware agents
> see, drive, and debug Windows desktop and CLI software running on the
> user's own machine. Pre-launch: free for the first 500 verified-email
> users, no time limit, no credit card.
## Quick start (5 steps, ~10 minutes)
1. **Sign up** at with an email
address. Slot is allocated if one of the 500 pre-launch seats remains;
otherwise a waitlist position.
2. **Verify** by clicking the link in the resulting mail. The browser
downloads `license.dat` (ECDSA-signed payload, a few KB).
3. **Download the installer** from the link in the same mail:
(Windows single-file, ~108 MB).
4. **Run installer**: launch `JidoDebuggerSetup.exe`. On the LicenseKey
page, drag and drop `license.dat` onto the drop zone. Walk through
the TelemetryConsent, MachineActivation, install-location pages,
then finish.
5. **Wire your AI client** to the local MCP server installed in step 4.
One-line examples:
- Claude Code: `claude mcp add --transport stdio jidodebugger jidodebugger-mcp.exe`
- GitHub Copilot (VS Code 1.99+): `code --add-mcp '{"name":"jidodebugger","command":"jidodebugger-mcp.exe"}'`
- Cursor / Claude Desktop / Codex: see the "For your AI" section at
After step 5, your AI agent has 45+ Windows automation tools available
inside the same conversation it was using to write code.
## Two MCP servers
There are intentionally two separate MCP surfaces. Don't confuse them.
| Server | Transport | URL / command | Purpose |
|---|---|---|---|
| **Docs MCP** (this site) | HTTP+SSE | `https://jidodebugger.dhq-boiler.dev/mcp` | 5 anonymous explainer tools (`jidodebugger_overview`, `jidodebugger_feature`, `jidodebugger_pricing`, `jidodebugger_grandfather`, `explain_mcp_concept`). Read-only. Optional — you only register this if you want your AI to explain the product to you without leaving its chat. |
| **Local MCP** (installed via JidoDebuggerSetup.exe) | stdio | `jidodebugger-mcp.exe` | 45+ tools for actually driving Windows apps: `uia_*` automation, `capture` / `ocr`, `record_*` recording, `crash_watch_*`, `vram` / `sample_fps` / `sample_resource`, `a11y_audit`, `submit_feedback`, `workspace_locate_automation_id`, etc. Required to actually use the product. |
## Pricing
| Tier | Status | Price | Audience |
|---|---|---|---|
| **Pre-launch** | Current | Free, first 500 verified-email users, no time limit | Anyone willing to be an early user |
| **Individual** | Post-incorporation | TBD; 20% off first year for pre-launch users | Solo devs, indie studios, QA freelancers |
| **Organization** | Post-incorporation | TBD per-seat; 20% off first year for pre-launch users | QA teams, mid-size studios, enterprise Windows teams |
Hosting policy: JidoDebugger does NOT host worker pools. Customers own
and operate the Windows machines that run their test workloads. We sell
software, not compute.
## Grandfather offer for pre-launch users
- First 500 verified-email users get free access for the entire
pre-incorporation period — no time limit.
- License is refresh-token-backed: it auto-renews silently as long as
the user's machine can reach the activation server.
- After incorporation and the move to paid plans, pre-launch users keep
**20% off the standard Individual or Organization tier for the first
year**.
- The 500-user cap exists for two reasons: (1) honest scarcity around
support quality at this stage, (2) it converts "register if you
remember" into "register before it fills".
- Beyond 500 users, registrations land on a waitlist. As pre-launch
users drop off (uninstall, fingerprint mismatch, refresh failure),
waitlist slots open.
## Features (cataloged)
- **WhiteBoxMode** — agent has read access to the source that produced
the target binary (via `--workspace` or `JIDODEBUGGER_WORKSPACE`).
Cross-references UI AutomationIds back to source via
`workspace_locate_automation_id`.
- **BlackBoxMode** — binary-only mode. UIA tree, screenshots, OCR are
the only signal.
- **BugViewer** — replayable bug-report viewer. Drops a zip after
`record_finding` calls.
- **Recording** — `record_start` / `record_stop` brackets a session.
Tool calls, screenshots, console events all captured. `record_finding`
exports xUnit / NUnit / MSTest test skeletons.
- **UIATools** — 25+ Microsoft UI Automation tools for WPF / WinForms /
WinUI. `uia_click`, `uia_set_value` (with `commitMode=LostFocus`),
`uia_get_tree`, `uia_survey`, etc.
- **CrashWatch** — process crash watching with diagnostics capture.
- **ResourceSampling** — VRAM / CPU / FPS sampling for the target process.
- **A11yAudit** — accessibility audit pass (Name properties, focus
order, keyboard alternatives).
- **FeedbackLoop** — `submit_feedback` posts user-facing feedback /
feature requests to the JidoDebugger team. Anonymous by default.
- **DistributedGrid** (roadmap, Phase 1.5) — run jobs across multiple
Windows workers, BYO-device or BYO-cloud. Not vendor-hosted.
## Designed for / not for
**Designed for**: Solo devs building Windows desktop apps, QA teams who
want to write tests in plain English, indie game devs (Phase 2) who
need ViGEm controller input.
**Not designed for**: macOS / Linux desktop automation (Windows-only by
design), replacing your existing AI coding assistant (it pairs, not
competes), cloud-hosted CI for non-Windows targets.
## Data handling
JidoDebugger runs locally on the user's Windows machine. Screenshots,
UIA snapshots, and findings stay on the user's disk. Outbound traffic
to jidodebugger.dhq-boiler.dev is limited to license refresh and
minimal anonymized telemetry (startup events; on by default, opt-out in
the Controller's Settings). Source code is never uploaded.
## Languages
The website and installer ship in five languages: English, 日本語,
简体中文, 繁體中文, 한국어.
## Where to learn more
- Marketing site:
- Installer download:
- Docs MCP server:
- Email: