SecOpsAI Dashboard

SecOpsAI Dashboard is a lightweight control surface for the current SecOpsAI product.

It is focused on:

• findings visibility
• triage task management
• native triage queue visibility
• helper-backed native investigate/apply-action/guarded close controls
• approved subscription-backed intelligence actions and ChatGPT app status
• Supabase-backed operational state

It is not the core execution runtime. Native SecOpsAI and OpenClaw still own investigation, orchestration, and outbound operator messaging, but the local helper can now invoke selected native SecOpsAI triage actions directly.

Current surfaces

• Overview — top-level run, blocker, review, and findings posture
• Tasks — Kanban workflow for work items
• Findings — findings backlog with task correlation
• Native Triage — local helper health, pending actions, orchestrator history, and selected native action controls
• System — platform health, the local Codex bridge, durable intelligence jobs, and the read-only SecOpsAI ChatGPT app endpoint

What was removed

The dashboard no longer ships the older generic mission-control extras that were not aligned with the current SecOpsAI direction:

• Discord dispatcher runtime
• direct dashboard-side Discord messaging
• Paperclip setup flow
• Org Map / Agents / Artifacts UI surfaces

Current stack

• HTML + Vanilla JS
• Tailwind CSS
• Supabase JS SDK
• optional local Python helper server for integration status, run-output reads, native triage state, and selected native triage actions

Important files:

• secopsai-dashboard/index.html
• secopsai-dashboard/app.js
• secopsai-dashboard/styles.css
• secopsai-dashboard/config.template.js
• secopsai-dashboard/generate-config.py
• secopsai-dashboard/dashboard_server.py
• secopsai-dashboard/start-local-dashboard-stack.sh
• secopsai-dashboard/serve-dashboard.sh

Data model

Primary tables:

• agent_runs
• work_items
• dashboard_events

Optional but supported tables:

• findings
• run_requests
• channel_routes

The UI degrades safely if optional tables are not present yet.

Local run

cd secopsai-dashboard
cp .env.example .env
python3 generate-config.py
./start-local-dashboard-stack.sh

Then open:

http://127.0.0.1:45680

SecOpsAI Edge integration

The Edge workspace treats SecOpsAI Core as the canonical source for network assets, graph changes, and Edge-origin findings. The local helper can enrich that view with live site, sensor, schedule, and scan-job status from the Edge API.

Configure these values on the helper host, never in browser configuration:

• SECOPSAI_EDGE_API_URL
• SECOPSAI_EDGE_OPERATIONS_TOKEN

Generate the second value from the Edge dashboard under Settings → Workspace integration tokens → Create dashboard token. It is workspace-scoped, revocable, shown once, and limited to operations:read. The legacy SECOPSAI_EDGE_ADMIN_TOKEN variable is accepted temporarily for migration but is intentionally marked as degraded in the operator UI.

SecOpsAI Intelligence

Open System → SecOpsAI Intelligence to use either integration:

• The local Codex bridge uses the Codex CLI's existing ChatGPT sign-in and processes only fixed, read-only SecOpsAI analysis actions. It does not persist ChatGPT credentials.
• The hosted ChatGPT app exposes nine read-only tools through an OAuth-protected MCP endpoint. SecOpsAI OAuth controls data access independently from the user's ChatGPT account.

Local action controls require INTELLIGENCE_ADMIN_TOKEN in secopsai-dashboard/.env. Hosted Pages uses server-side SECOPSAI_CORE_INTELLIGENCE_TOKEN; neither value belongs in browser configuration. See the full integration guide for setup and security boundaries.

Product fit

This dashboard now complements the latest secopsai repo work:

• native triage workflow
• triage orchestrator
• action queue / apply-action flow
• findings sync into Supabase

The local helper now exposes native SecOpsAI triage state so the dashboard can show:

• local triage summary
• pending triage actions from action_queue.json
• recent orchestrator summaries under reports/triage/orchestrator/
• latest local findings artifact metadata
• direct helper-backed triage investigate
• direct helper-backed triage apply-action
• direct helper-backed guarded triage close