rudder-desktop-dev-recovery-maintainer

What problem does it solve?

It helps diagnose and repair broken local Rudder Desktop development startup and update flows so you can get back to a known working state without confusing instance data or disrupting unrelated work.

Core Features & Use Cases

• Failure-mode classification: Determines whether the blocker is API/server, Electron shell, embedded Postgres, UI build/typecheck (including dirty-WIP issues), packaged smoke, or update/install/restart behavior.
• Safe, narrow repairs: Stops the right stale process, applies the minimal fix (including fixture/compile ownership packets), and avoids destructive actions like wiping local data unless explicitly authorized.
• Correct runtime validation & escalation: Verifies health via local API checks, validates Desktop launch and update/install pathways (with the strongest safe local checks), and routes the release portion to release-maintainer only after local Desktop state is green.

Quick Start

Ask the maintainer to diagnose your Desktop dev failure by providing the exact command you ran (for example pnpm dev), the relevant port/log excerpt, and whether API health is OK while Electron fails to start.