Open the CapusQA dashboard in your browser — the live web view of every run, session, finding, persona and setting (the same store chat uses). Use for "open the dashboard", "show me the dashboard", "where's the dashboard", "launch the UI", or /capusqa:dashboard.
Check the CapusQA environment and fix what's red — daemon health, macOS Accessibility/Screen-Recording permissions, vision models, browser support, MCP/plugin wiring. Use when setting up, when clicks/typing do nothing, perception is degraded, or anything misbehaves and the user doesn't know why. Can trigger the…
The CapusQA menu — opens when the user types /capusqa. Mirrors the dashboard's navigation (New test, Runs, Issues found, Settings) plus Setup, Update, Doctor, and routes to the right command. Use for "/capusqa", "what can capusqa do", "how do I…", "which command", when the user is new, or used a command wrong.
The CapusQA issues board — the chat version of the dashboard Issues page ("Issues found"). Findings grouped into clusters across all runs, by severity; mark fixed, rate helpful/not, re-test; and send selected issues to your coding agent (the handoff). Use for "what did it find", "show the bugs/issues", "triage", "fix…
Watch CapusQA runs — the chat version of the dashboard Runs page. List runs, drill into sessions, see live screens and step traces, exit verdicts and cost; steer or stop a live session; start the runner. Use for "what's running", "show my runs", "is it done", "watch/steer/stop that session". To START a test use…
Configure CapusQA — the chat version of the dashboard Settings page. Asks which area to configure (Test modes, Run defaults, Handoff mode, Findings, Personas, Audiences, Saved secrets, Role logins, Usage, Your plan), then does it through the daemon. Use for "settings", "configure", "add a login/credential", "add…
Get CapusQA ready to test an app — first-run environment wiring (macOS permissions, vision models, browser) and project prep (add personas, add a login). Use for "set up capusqa", "first time", "get ready to test", "nothing's set up yet". For pure environment health use /capusqa:doctor; to update versions use…
Start a CapusQA test — the chat version of the dashboard Home launcher. Asks the SAME questions Home asks, in Home's order, as multiple choice with the dashboard's exact wording (app URL, what to test, project folder, repository code analysis, who your users are, test mode, automatic improvements, how thorough), then…
Update CapusQA to the latest version — the package, the Claude plugin, and the vision models — then restart the daemon. Use for "update capusqa", "is there a new version", "upgrade", "get the latest", or after pulling new code. Fixes being stuck on an old version because setup is install-only, not upgrade-aware.
Open the CapusQA dashboard in your browser — the live web view of every run, session, finding, persona and setting (the same store Codex uses). Use for "open the dashboard", "show me the dashboard", "where's the dashboard", "launch the UI", or $capusqa-dashboard.
Check the CapusQA environment and fix what's red — daemon health, macOS Accessibility/Screen-Recording permissions, vision models, browser support, MCP/skills wiring. Use when setting up, when clicks/typing do nothing, perception is degraded, or anything misbehaves and the user doesn't know why. Can trigger the…
The CapusQA menu for Codex — the command map that mirrors the dashboard's navigation (New test, Runs, Issues found, Settings) plus Setup, Update, Doctor, and routes to the right $capusqa- skill. Use for "what can capusqa do", "how do I…", "which capusqa command", when the user is new, or used a command wrong.
The CapusQA issues board from Codex — the dashboard Issues page ("Issues found"). Findings grouped into clusters across all runs, by severity; mark fixed, rate helpful/not, re-test; and send selected issues to your coding agent (the handoff). Use for "what did it find", "show the bugs/issues", "triage", "fix these"…
Watch CapusQA runs from Codex — the dashboard Runs page. List runs, drill into sessions, see live screens and step traces, exit verdicts and cost; steer or stop a live session; start the runner. Use for "what's running", "show my runs", "is it done", "watch/steer/stop that session". To START a test use $capusqa-test.
Configure CapusQA from Codex — the dashboard Settings page. Asks which area to configure (Test modes, Run defaults, Handoff mode, Findings, Personas, Audiences, Saved secrets, Role logins, Usage, Your plan), then does it through the daemon. Use for "settings", "configure", "add a login/credential", "add personas"…
Get CapusQA ready to test an app — first-run environment wiring (macOS permissions, vision models, browser) and project prep (add personas, add a login). Use for "set up capusqa", "first time", "get ready to test", "nothing's set up yet". For pure environment health use $capusqa-doctor; to update versions use…
Start a CapusQA test from Codex — the chat version of the dashboard Home launcher. Asks the SAME questions Home asks, in Home's order, as numbered multiple choice with the dashboard's exact wording (app URL, what to test, project folder, repository code analysis, who your users are, test mode, automatic improvements…
Update CapusQA to the latest version — the package, the Codex skills, and the vision models — then restart the daemon. Use for "update capusqa", "is there a new version", "upgrade", "get the latest", or after pulling new code. Fixes being stuck on an old version because setup is install-only, not upgrade-aware.