t1k:cocos:omarchy:doctor
| Field | Value |
|---|---|
| Module | omarchy |
| Version | 0.4.2 |
| Effort | low |
| Tools | Bash, Read |
Keywords: cocos bridge health linux, omarchy cocos doctor, verify cocos on linux, winpodx cocos doctor
How to invoke
Section titled “How to invoke”/t1k:cocos:omarchy:doctor[--project <dir>] [--json]Omarchy Cocos doctor
Section titled “Omarchy Cocos doctor”bun .claude/skills/t1k-cocos-omarchy-winpodx/scripts/cocos-omarchy.cjs doctor [--project <dir>] [--json]
Read-only: never starts the guest, never writes. Statuses pass | warn | fail | skip (skip = not measured, never a pass).
Exit 0 ok, 1 a check failed, 2 config error, 3 not an Omarchy host. A stopped container and a closed bridge port are warn
(normal while the guest/editor is off), a missing package, forward, Hyprland rule or desktop entry is fail.
With --project it runs base’s editor-doctor.cjs (reused, not re-implemented) and reports its exit code; read its own
--json for findings. Probes use TCP connect to 127.0.0.1:<port> only - no token is sent or read.