Linters check syntax. Git blame shows who edited a line. WhyBug runs locally on your machine to uncover the hidden production edge case or race condition a block of logic was guarding against—before you refactor it.
$ npm install -g whybug
$ whybug
processPayment, exposing synchronous gateway calls to transient network drops.Guarded against brief TLS handshake timeouts and HTTP 502 blips from the upstream payment gateway.
Single-packet drops will immediately fail customer checkouts and leave payment intents half-open.
Replace inline loop with an idempotency-keyed backoff policy rather than calling callGateway() bare.
Code in production often looks unusual or overly defensive: custom retry loops, 30-second clock-skew buffers, fallback shims, or manual cache locks. When another engineer "cleans up" that code six months later, they inadvertently reintroduce the exact race condition or outage it was written to prevent.
Surfaces the human and architectural reason behind legacy guards the moment you modify or delete them in VS Code, IntelliJ, or Vim.
Raw diffs, proprietary algorithms, and variables are parsed strictly in local RAM. Your source code never leaves your machine.
Runs silently on standard laptop CPUs under the native whybug process with no GPU required and zero IDE lag.
| Capability | Static Linters | Cloud AI Copilots | WhyBug |
|---|---|---|---|
| Explains Why Defensive Logic Was Written | No (Syntax only) | Requires uploading raw code | Yes — Real-Time Intent Archaeology |
| Zero Proprietary Code Sent to Cloud | Yes | No (Uploads files & snippets) | Yes — 100% Local Diff Parsing |
| Per-Project Isolated Cache & History | N/A | Shared cloud chat | Dedicated Workspace Cache per Repo |
| Complete 1-Command Uninstall | Manual | Leaves editor caches | whybug uninstall wipes everything |
WhyBug splits continuous code watching from deep architectural collision analysis so your proprietary source code never leaves localhost.
4040, 4041, etc.) so projects never mix.
Raw Git diffs stay locked in Layer 1 (Local RAM). Only sanitized, high-level intent statements pass through the Layer 2 filter when you request an audit.
{
"metadata": {
"summary": "Removed bounded 3-attempt retry loop in processPayment, exposing synchronous gateway calls to transient network drops.",
"symbols": ["processPayment"],
"affectedFiles": ["PaymentService.java"],
"commitTitle": "feat: resilient payment service",
"changeCategory": "intent-modification"
}
}
Select a scenario below to preview the synchronized Terminal output and localhost:4040 Deep Audit report.
whybug in Any Repository.
Install globally once via npm. From then on, simply run whybug inside any project folder—each repository automatically gets its own isolated workspace cache and port.
npm install -g whybug
Installs the whybug binary globally on your PATH so it is ready in every terminal.
whybug
Creates an isolated project cache for the current repository and launches the live dashboard at localhost:4040.
audit 1
Type audit <id> in the terminal or click Request Deep Audit in the web UI for a 3-part collision report.
whybug uninstall
Wipes all cached data, clears all project histories, and uninstalls the global CLI with zero residual files left behind.
Never. Raw Git diffs, variable names, and syntax are parsed strictly in local RAM. When you request an optional Deep Audit, only a 1-sentence abstracted intent statement is transmitted.
WhyBug automatically isolates each repository into its own workspace session and assigns a dedicated local dashboard port (4040, 4041, etc.) so your project histories never mix.
WhyBug runs under its own native process (whybug) with a lightweight footprint under 500MB RAM on standard laptop CPUs—no GPU required.
Run whybug uninstall (or whybug clean). It deletes all local cached data and project histories before uninstalling the global CLI package.