npx claudepluginhub davepoon/buildwithclaude --plugin codex-hud# Setup Codex HUD Install (or re-install) the statusline integration so the Codex usage bars render below claude-hud's statusline. Read the JSON output. Report concisely to the user: - If `ok: true`, confirm that the symlink was created (or already in place) and that `~/.claude/settings.json` is configured. - If `settingsUpdated: true`, remind them to run `/reload-plugins` or restart Claude Code. - If `ok: false`, print the `message` field so the user can fix it. Then briefly check API key status (informational only, no prompt): Interpret the output: - `"status": "connected"` → tell...
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupDetects ghost or inconsistent claude-hud plugin installations (orphaned cache, stale registry, temp files) and offers cleanup on user confirmation for macOS/Linux/Windows.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupGuides enterprise admins through Claude Office add-in setup for Vertex AI, Bedrock, or custom gateway; provisions credentials and generates deployable manifest.xml.
/setupRuns interactive setup wizard: detects AI providers (Codex, Gemini, Ollama, etc.), installs missing tools, configures auth, sets up RTK token optimization.
/setupConfigures claude-hud as Claude Code statusline by providing ~/.claude/settings.json config, build instructions, manual setup, and troubleshooting steps.
Install (or re-install) the statusline integration so the Codex usage bars render below claude-hud's statusline.
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" install-statusline --json
Read the JSON output. Report concisely to the user:
ok: true, confirm that the symlink was created (or already in place) and that ~/.claude/settings.json is configured.settingsUpdated: true, remind them to run /reload-plugins or restart Claude Code.ok: false, print the message field so the user can fix it.Then briefly check API key status (informational only, no prompt):
node "${CLAUDE_PLUGIN_ROOT}/dist/index.js" setup --json
Interpret the output:
"status": "connected" → tell the user costs tracking is active."status": "no_key" → tell the user: "Admin API key not configured. Costs commands will show a no-key notice. If you want to enable dollar cost tracking, run /codex-hud:setup-key. Otherwise no action needed — rate limits and usage work without a key.""status": "error" → show the error.Do not prompt for the API key from this command. Direct the user to /codex-hud:setup-key if they want to configure one.