# Mission Control - Future Improvements **This document tracks potential future enhancements for Mission Control.** **Last Updated:** 2026-05-10 **Current Version:** v0.0.4 ## How to Use This Document This file is a living document. Agents should: 1. Read this file before proposing changes 2. Add new recommendations with priority levels 3. Never add completed items - move those to HISTORY.md instead 4. Reference this file when dispatching improvement tasks 5. Only Ripley can remove items from this list. ### Priority Format All items must include the priority emoji in their heading, matching the section they belong to: | Priority | Emoji | Heading Format | |----------|-------|---------------| | CRITICAL | 🔴 | `### 🔴 Title - CRITICAL` | | HIGH | 🟠 | `### 🟠 Title - HIGH` | | MEDIUM | 🟡 | `### 💡 Title - MEDIUM` | | LOW | 🔵 | `### 🔵 Title - LOW` | | NICE TO HAVE | 💭 | `### 💭 Title - NICE TO HAVE` | Items are grouped under their priority section heading (`## 🔴 CRITICAL`, `## 🟠 HIGH`, etc.) and sorted most-impactful-first within each tier. --- ## Pending Recommendations ### 🟠 HIGH ### 🟠 Gateway Data Collection Service - HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-10 by Ripley **Completed:** 2026-05-11 GatewayCollectorService created in `src/backend/app/services/monitoring/`. Background asyncio task polls gateway RPC endpoints (cost, cron, sessions, health) and upserts into monitoring models. Configurable intervals via env vars. Startup/shutdown integrated into main.py lifespan. ### 🟠 Monitoring Database Models - HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-10 by Ripley **Completed:** 2026-05-11 All 7 models created, migrated, CASCADE + composite indexes verified in running DB. Committed as v0.0.3. **Description:** Create new PostgreSQL models for tracking data (cost, sessions, crons, system health, alerts). **Implementation Notes:** - CostSnapshot, CronJobStatus, SessionEvent, SubAgentRun, SystemHealthMetric, AlertRule - Alembic migration for all new tables - CRUD API endpoints under `/api/monitoring/` ### 🟠 WebSocket for Agent Events - HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-10 by Ripley **Completed:** 2026-05-11 WebSocket endpoint at `/ws/agents` with initial state snapshot (last 50 events) and background polling (every 2s). Event parser ported from TS source. Committed in v0.0.4. --- ### 🟡 MEDIUM ### 🟠 Monitoring API Endpoints - HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-11 10 read-only endpoints at /api/v1/monitoring/* with org-scoping, pagination, and filtering. Schemas in app/schemas/monitoring.py, router in app/api/monitoring.py. ### 🟠 Dashboard Logic Port - HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-11 Data processing functions ported to Python: `ModelName()`, `BuildDailyChart()`, `BuildAlerts()`, `FmtTokens()`, `BuildCostBreakdown()`. Event parser ported: `parse_session_event()`, `format_tool_status()`. WebSocket endpoint at `/ws/agents` with initial snapshot + polling. All committed in v0.0.4. ### 🟠 Cost Summary API Endpoints — HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-12 by Neo **Description:** "How much have I spent today, and which model is burning the most?" — Cost Cards + Cost Breakdown API endpoints. **Implementation Notes:** - Today's cost, all-time cost, projected monthly cost - Per-model cost breakdown (7d/30d/all-time tabs) - Use existing `data_processing.BuildCostBreakdown()` and `data_processing.BuildDailyChart()` - New API endpoints: `GET /api/v1/monitoring/cost-summary` and `GET /api/v1/monitoring/cost-breakdown?range=7d|30d|all` - Org-scoped, paginated where applicable - Neo implemented cost-summary and cost-breakdown endpoints ### 🟠 Health Summary API — HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-12 by Neo **Description:** "Is my gateway actually running right now?" — System health summary endpoint. **Implementation Notes:** - Gateway status (online/offline), PID, uptime, memory, compaction - CPU, RAM, swap, disk gauges - Use existing `monitoring/health` endpoint data + `data_processing` functions - New API endpoint: `GET /api/v1/monitoring/health-summary` - Neo implemented health-summary endpoint ### 🟠 Cron Summary API — HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-12 by Neo **Description:** "Which cron jobs ran, which failed, and when does the next one fire?" — Cron summary endpoint. **Implementation Notes:** - List all cron jobs with status, schedule, last/next run, duration, model - Filter by enabled/disabled, gateway - Use existing `monitoring/cron-jobs` endpoint - New API endpoint: `GET /api/v1/monitoring/cron-summary` - Neo implemented cron-summary endpoint ### 🟠 Sessions Summary API — HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-12 by Neo **Description:** "What sessions are active and how much context are they consuming?" — Active sessions summary. **Implementation Notes:** - Recent sessions with model, type badges (DM/group/cron/subagent), context %, tokens - Use `data_processing.ModelName()` and `event_parser.parse_session_event()` - New API endpoint: `GET /api/v1/monitoring/sessions-summary` - Neo implemented sessions-summary endpoint ### 🟠 Sub-Agents Summary API — HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-12 by Neo **Description:** "Are my sub-agents doing useful work or spinning in circles?" — Sub-agent activity summary. **Implementation Notes:** - Sub-agent runs with cost, duration, status + token breakdown (7d/30d tabs) - Use existing `monitoring/sub-agents` endpoint - New API endpoint: `GET /api/v1/monitoring/sub-agents-summary` - Neo implemented sub-agents-summary endpoint ### 🟠 Cost Trends API — HIGH **Priority:** HIGH **Status:** DONE ✅ **Added:** 2026-05-11 by Ripley **Completed:** 2026-05-12 by Neo **Description:** "What's the cost trend over the last 7 days — am I accelerating?" — Charts & trends endpoint. **Implementation Notes:** - Cost trend line (7d/30d), model cost breakdown bars, per-model usage - Use `data_processing.BuildDailyChart()` - New API endpoint: `GET /api/v1/monitoring/trends?range=7d|30d` - Neo implemented trends endpoint with 7d/30d support ### 🟡 Cost Tracking UI - MEDIUM **Priority:** MEDIUM **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Port the dashboard's cost cards, donut charts, and trend lines to React/Recharts components. **Implementation Notes:** - Today's cost, all-time cost, projected monthly - Per-model cost breakdown (7d/30d/all-time tabs) - Cost trend line chart (SVG → Recharts) - Theme-aware styling ### 🟡 Session & Sub-Agent UI - MEDIUM **Priority:** MEDIUM **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Active sessions with model, type badges, context % bars, sub-agent activity grid. **Implementation Notes:** - Session list with filtering (model, type, status) - Context % bars, token counts - Sub-agent activity grid with cost/duration/status - Session detail panel with conversation preview ### 🟡 Cron Job Management - MEDIUM **Priority:** MEDIUM **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Cron job list with schedule, status, run history. Trigger manual runs from UI. **Implementation Notes:** - List, add, edit, delete cron jobs via gateway RPC - Run history with duration and status badges - Manual trigger button - Uses existing `cron.*` gateway RPC methods ### 🟡 System Health Dashboard - MEDIUM **Priority:** MEDIUM **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Gateway status, CPU/RAM/disk gauges, alert banners with configurable thresholds. **Implementation Notes:** - Gateway uptime, PID, memory, compaction status - CPU/RAM/swap/disk gauge cards - Alert banner for high cost, failed crons, gateway offline - Auto-refresh with countdown timer --- ### 🔵 LOW ### 🔵 AI Chat Panel - LOW **Priority:** LOW **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Port the dashboard's AI chat to a React component that uses OpenClaw gateway's `/v1/chat/completions`. **Implementation Notes:** - Context-aware: feed live monitoring data into system prompt - Persistent chat history per user - Streaming responses ### 🔵 Theme System Merge - LOW **Priority:** LOW **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Port the 6 dashboard themes into Mission Control's Tailwind config. **Implementation Notes:** - Map dashboard's 19 CSS color variables to Tailwind config - Theme picker in header (persists via localStorage) - Glass morphism effects where appropriate ### 🔵 Engineering Reference Manual - LOW **Priority:** LOW **Status:** PENDING - Requires explicit user initiation **Added:** 2026-05-10 by Ripley **Description:** Comprehensive engineering reference manual documenting the full system architecture, API endpoints, data models, frontend pages/components, and infrastructure. **Implementation Notes:** - ⚠️ This task requires explicit initiation by the user. Do not create the Engineering Reference Manual unless specifically asked. - Should document: system architecture, tech stack, all API endpoints, data models, frontend structure, Docker setup, auth flows - Bishop would own this task when initiated --- ### 💭 NICE TO HAVE ### 💭 Pixel Agent Canvas - NICE TO HAVE **Priority:** NICE TO HAVE **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Port the pixel-art office scene with agent sprites, activity bubbles, and day/night cycle to React Canvas. **Implementation Notes:** - Use `useRef` + `requestAnimationFrame` for animation, not React state - Agent sprites with activity state (working, idle, talking) - Activity bubbles showing current task/conversation - Conversation heat glow based on recent activity - Pan/zoom controls (touch + mouse) ### 💭 Hardware Monitor & Service Controls - NICE TO HAVE **Priority:** NICE TO HAVE **Status:** PENDING **Added:** 2026-05-10 by Ripley **Description:** Server rack component for hardware gauges, breaker panel for gateway start/stop/restart. **Implementation Notes:** - CPU/GPU/RAM/disk/network gauges - Gateway start/stop/restart controls - Update checker (ham radio component) - All via gateway RPC methods