Skip to content

[Improvement] omacase debug — one-command support bundle #26

Description

@splaice

Quattro feature

Omarchy 4 ships omarchy-debug, collecting diagnostic data into one artifact for support (their Discord). It exists because "run doctor and paste these five other things" doesn't scale past the maintainer's own machines.

Omacase fit

Everything the bundle needs already has a producer: omacase doctor output, omacase version + git SHA/channel, brew bundle check result, OmniWM version + omniwmctl ping, LaunchAgent states (launcher/usage), theme + wallpaper state, recent migrate/update markers, tail of tracker.log. What's missing is one command that gathers them with secrets scrubbed.

Proposed shape

  • omacase debug → writes ~/Desktop/omacase-debug-<ts>.txt (or stdout with -): sections per source above, each failure-tolerant
  • Scrub rules stated in the header: no tokens, no Keychain access, usage records summarized as counts only, $HOME replaced with ~
  • Completion + menu entry; README one-liner

Scope

Future release; becomes valuable the day Omacase has its second user. Small, independent.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    improvementSystemic improvement for a future release — not a defectquattro-parityInspired by Omarchy 4 Quattro — evaluate for Omacase parity

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions