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
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 doctoroutput,omacase version+ git SHA/channel,brew bundle checkresult, 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-tolerantScope
Future release; becomes valuable the day Omacase has its second user. Small, independent.
🤖 Generated with Claude Code