Ops Dash

FAQ answers

| # | Question | Answer | | --- | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | What is claude-ops? | Business operations OS for Claude Code. Manages inbox, fires, deploys, PRs, revenue, and can run your business autonomously via YOLO mode. | | 2 | Channel setup | Run /ops:setup — interactive wizard detects installed CLIs and walks you through each channel. | | 3 | YOLO mode | Spawns 4 AI agents (CEO, CTO, CFO, COO) to analyze your business. Type YOLO to hand over controls — it processes inbox, fixes fires, merges PRs, and advances GSD phases. | | 4 | Data collection | All data stays local. No telemetry. Registry and preferences are gitignored. Tokens stored in macOS keychain or env vars. | | 5 | Command reference | List all /ops:* commands with descriptions | | 6 | Shortcuts | 1-9, 0 for actions, a-h for power/comms/settings, b always goes back, q exits | | 7 | MCP disconnected | Wait 5s and retry (auto-reconnect hook). After 3 fails, falls back to CLI tools. | | 8 | WhatsApp | Check bridge liveness: lsof -i :8080 | grep LISTEN. If not running, prompt restart: launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge. Check launchctl list com.${USER}.whatsapp-bridgefor status. If store locked:kill $(pgrep whatsapp-bridge). | | 9 | Telegram | Needs user-auth (not bot). Run /ops:setup → Telegram section. API ID + hash from my.telegram.org. | | 10 | Unread | Channel must be configured in /ops:setup. Check ops-unread script output for errors. | | 11 | Smart-home (Homey) | Run /ops:setup --section home to configure Homey Pro. Once set, hotkey h and /ops:ops-home are routable. Status dot on the dashboard: green = all devices online + no alarms, yellow = device offline, red = active critical alarm. |

For links (w, r, i): open in browser via open (macOS) or xdg-open (Linux).

For changelog (c): read and display ${CLAUDE_PLUGIN_ROOT}/CHANGELOG.md.

After each FAQ answer, offer b) Back to dashboard or h) Back to FAQ.

Return-to-dash loop

After ANY skill completes and returns control, re-render the dashboard by running the bin script again and re-entering the routing loop. This creates the "app within an app" experience — the user always comes back to the command center.

To re-render:

${CLAUDE_PLUGIN_ROOT}/bin/ops-dash 2>/dev/null

Then AskUserQuestion again for the next action.

Exception: If user types q, quit, or exit, end the session gracefully:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 OPS > SESSION ENDED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If $ARGUMENTS is back

Re-render the dashboard and enter routing loop.

If $ARGUMENTS is settings

Jump directly to settings sub-menu (skip dashboard render).

If $ARGUMENTS is share

Jump directly to share sub-menu.

If $ARGUMENTS is faq

Jump directly to FAQ sub-menu.

Setup gate

If the dashboard script outputs DASH_RENDER_FAILED or the preferences file doesn't exist, show:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 OPS > SETUP REQUIRED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

 Run /ops:setup to configure your integrations first.

Then invoke /ops:setup directly.

Windsor.ai (optional live data)

If Windsor.ai is connected (mcp__*Windsor*__* or a windsor_api_key), use it as the live cross-channel source for all live KPIs (spend, ROAS, CAC, sessions, social reach) for the command-center tiles, flagging deviations vs 7d/30d. Map accounts per project via registry.json → .projects[].windsor. Prefer blended ROAS (store/analytics revenue ÷ total ad spend) over platform-reported ROAS. See docs/integrations/windsor-ai.md for the full playbook (REST + MCP modes, registry mapping, analysis mandate, and caveats). Data sanity: if Windsor returns only zeros across sources (Meta + Google spend/impressions and Instagram reach all exactly 0 over 30d while accounts are connected), treat the data as unavailable — the plan may be expired (check get_current_user → is_paid) — warn the user, and never present zeros as real metrics. scripts/windsor-data-sanity.sh automates the check.

Windsor is optional. If Windsor is not connected, returns errors, or returns the all-zero pattern, fall back to the free direct libraries: scripts/lib/ad-spend-aggregator.sh (paid), scripts/lib/ga4-data-api.sh (analytics), and scripts/lib/organic-metrics-aggregator.sh (organic + merchant). See docs/integrations/direct-channel-wiring.md. Never present zeros from a dead source as real metrics.

Additional resources

CLI detail: references/cli.md.