Mission Control
for Claude Code

I'm setting up Claude Control. Please verify I have the prerequisites installed: git, Node.js 18+, npm, and the Supabase CLI. Run version checks for each. If any are missing, pause and tell me what to install before continuing. Once everything is verified, clone https://github.com/mkanasani/claude-control-kit-community.git into the current directory, cd into it, and run `npm install`. Report when complete and stop — I'll give you the next lesson.

I'm about to create a free Supabase project. Walk me through it step by step: 1. What region should I pick (I'm in ). 2. After it's provisioned, where do I find these four values: Project URL, Project Ref, publishable anon key, service_role key. 3. As I share each value, validate the format (URL should be https://*.supabase.co, project ref is the subdomain, keys start with sb_publishable_ or eyJ...). Save the values to a temporary in-memory note. Don't write them to disk yet — we'll use them in the next lesson.

Using the Supabase project ref I gave you in Lesson 2: 1. Run `supabase login` if I'm not already logged in. 2. Run `supabase link --project-ref ` from the cloned repo directory. 3. Run `supabase db push` to apply all 72 migrations. 4. Watch for failures and report any that don't apply cleanly. 5. After migrations finish, list the tables in the public schema with `supabase db dump --schema public --data-only=false` (or via the dashboard) and confirm tasks, ai_log, ai_status, ops_apps, and ai_agents all exist. Stop when verified.

Set up the Supabase edge-function secrets: 1. Generate a random webhook secret with `openssl rand -hex 32`. Save the value — I'll call it CLAUDE_CONTROL_WEBHOOK_SECRET. 2. Run `supabase secrets set CLAUDE_CONTROL_WEBHOOK_SECRET=`. 3. Generate a second random hex with `openssl rand -hex 32` for AI_TASKS_API_KEY. Set it the same way. 4. Ask me for my Anthropic API key (https://console.anthropic.com — keys start with sk-ant-). Set it as ANTHROPIC_API_KEY. 5. Confirm all three secrets show up in `supabase secrets list`. Save the webhook secret to a local notes.md file in the project root so I have it for Lessons 7 and 9. Don't commit it.

Deploy every edge function in the kit: 1. List all directories under supabase/functions/ — these are the functions to deploy. 2. For each one, run `supabase functions deploy --no-verify-jwt`. 3. Report success or failure for each. 4. After they're all deployed, smoke-test ai-tasks by curling it with the webhook secret from Lesson 4: curl -X POST https://.supabase.co/functions/v1/ai-tasks \ -H "Content-Type: application/json" \ -H "x-webhook-secret: " \ -d '{"request_type":"status","action":"update","is_online":true,"agent_name":"Setup","agent_emoji":"🛠️"}' The response should be {"success": true, ...}. Pause and report.

I need to create my admin user so the dashboard has someone to authenticate. Walk me through it: 1. Tell me to open the Supabase Dashboard → SQL Editor for my project. 2. Give me the SQL to insert myself into auth.users with my email and full name (ask me for both). 3. After I run it, give me the verification SQL: `SELECT id, email, raw_user_meta_data->>'full_name' as name FROM auth.users;` 4. Confirm the user exists and save the user_id — Claude Code will reference it later when assigning tasks.

Set up the frontend: 1. Create a .env.local file in the project root with these three variables — pull the values from Lessons 2 and 4: VITE_SUPABASE_URL=https://.supabase.co VITE_SUPABASE_PUBLISHABLE_KEY= VITE_CLAUDE_CONTROL_WEBHOOK_SECRET= 2. Run `npm run dev` and tell me the localhost URL. 3. I'll visit /auth and sign up with the same email I used in Lesson 6. 4. After I confirm the dashboard loads, kill the dev server. If the page is blank with no console errors, the env vars aren't being read — Vite bakes them at build time, so they MUST be in .env.local before `npm run dev` starts.

Time to deploy the dashboard to a live URL. Ask me whether I want Netlify or Cloudflare Pages, then walk me through it: For Netlify: - Install netlify-cli globally. - Run `netlify login` then `netlify init`. - Build with the VITE_ env vars inline in the shell command (NOT just from .env.local — the build needs them in the environment when triggered remotely too). - Run `netlify deploy --prod --dir=dist`. For Cloudflare Pages: - Install wrangler globally. - Run `wrangler login`. - Run `wrangler pages project create claude-control --production-branch=main` (skip if exists). - Build with VITE_ env vars in shell. - Run `wrangler pages deploy dist --project-name=claude-control --branch=main`. Either way: after deploy, give me the live URL and verify it loads without a blank page (devtools network tab should show requests to my Supabase project).

Wire my live Claude Code agent to the dashboard: 1. Ask me for the absolute path to the project where I run Claude Code most often. 2. Copy CLAUDE.md from this kit's repo root into that project as ./CLAUDE.md (or merge with an existing one — preserve my customizations). 3. Add these two env vars to my shell rc file (~/.zshrc or ~/.bashrc — detect which): export CLAUDE_CONTROL_API_URL="https://.supabase.co" export CLAUDE_CONTROL_WEBHOOK_SECRET="" 4. Source the rc file or open a new terminal so the vars are live. 5. Curl the status endpoint to confirm Claude Code can reach the dashboard: curl -X POST $CLAUDE_CONTROL_API_URL/functions/v1/ai-tasks \ -H "Content-Type: application/json" \ -H "x-webhook-secret: $CLAUDE_CONTROL_WEBHOOK_SECRET" \ -d '{"request_type":"status","action":"update","is_online":true,"status_message":"First connection","agent_name":"MyAgent","agent_emoji":"🤖","ring_color":"green"}' 6. Tell me to refresh the dashboard at my deployed URL — I should see MyAgent online with a green ring.

Run the four-step smoke test against my Claude Control dashboard. Use $CLAUDE_CONTROL_API_URL and $CLAUDE_CONTROL_WEBHOOK_SECRET from my shell. After EACH step, pause and ask me to refresh the dashboard to confirm the result is visible: 1. Status update: set agent SmokeTest online with green ring. 2. Task create: title "First Task", column "todo". 3. Log entry: category "general", message "Claude Control is alive!" 4. Insight push: insight_type "summary", title "Setup Complete", content "All systems online". If any step fails, debug it before moving on — check the Supabase edge function logs in the dashboard for the specific error. When all four pass, congratulate me — I'm officially live on Claude Control.