Session Resumes
3 sessionsBuilt Claude Code spend & session tracking end-to-end on ops-dashboard. /claude-usage page (local + VPS, DB or filesystem-backed), per-project usage cards on /project/[slug] with session resumes section, session drill-down at /claude-usage/session/[id] with cumulative-cost chart, tools breakdown, and a write-fingerprint card showing top folder + per-folder file counts (free narrative signal — no LLM). Statusline wrapper around claude-hud appends session $ line. Local PM2 auto-starts at Windows logon; pushes aggregated summaries to VPS every 15 min. Session resumes wired into project + session views with friendly session_name overriding random UUIDs.
Tune pricing for 1M-context Opus (currently under-counts); consider adding Caddy /api/claude-usage/ingest auth requirement to VPS session-resume endpoint too (currently public); session_resumes have no VPS→local sync, so resumes posted from VPS sessions won't appear locally; possibly add files_written column to recent-sessions table on home dashboard for fleet-wide quick scan
Built Claude Code usage tracking + session resumes integrated into project + session views.
Add a Stop hook for fully-automatic resume posting
Built ops-dashboard from scratch (SvelteKit 5 + SQLite). 30 projects registered across 2 VPS. Self-evolving engine (baselines, anomaly detection, health scoring, action items, weekly digest). Activity feed via HTTP hooks. Session resume system. Superpowers page. Installed 9 upgrades: SSH MCP, Prometheus MCP, singularity-claude, 5 custom skills, HTTP hooks, Agent Teams, Jarvis AI Ops, Mission Control.
1. Restart Claude Code to activate MCP servers + hooks + skills. 2. Create Discord bot for Jarvis (https://discord.com/developers/applications). 3. Install Prometheus on VPS-2 to enable metrics MCP. 4. Run /schedule in fresh session for cloud tasks. 5. Deploy Mission Control to VPS-2 for remote access. 6. Register logistics-offers project when deployed to VPS.