support / local-first diagnostics

Get unstuck without exposing your work.

WaitDojo support begins with local, reviewable diagnostics. No support bundle is uploaded automatically, and you decide what leaves your machine.

Start with the product doctor.

waitdojo doctor --product

Use the linked WDOJO_* code to jump to the exact remediation on the doctor guide.

Preview before sharing.

waitdojo support-bundle --preview
waitdojo support-bundle --explain-redactions

The bundle reports product version, coarse platform kind, command availability, terminal dimensions, path kinds, stable error codes, and remediation text. It excludes full home paths, usernames, PATH, prompts, code, agent output, tokens, and secret values.

Product provenance.

publisherInterstellar Manufacturing Corporationreleases →

founder / builderNishant Bhargavaemail →

published installerv0.2.4 public betachecksums →

published UI proofDeterministic v0.2.4 product captures bound to the release archivereview proof →

security boundaryChecksummed with Ed25519 signatures and signed provenancedetails →

Preview a clean uninstall.

waitdojo uninstall --dry-run
waitdojo uninstall

The default uninstall removes managed hooks, tmux control state, PATH entries, and the binary while keeping local progress and settings. Add --remove-data only when you also want WaitDojo's local progress, settings, backups, and support files deleted.

What to include in a support message.

WaitDojo version and whether you selected Codex or Claude Code.
macOS, Linux, or WSL2 and the stable WDOJO_* error code.
The reviewed, redacted doctor output or support-bundle preview.

Do not send prompts, repository contents, tokens, full paths, or coding-agent output.