πŸ›° Mission Control

Only decisions at the top. Everything else keeps moving automatically.

πŸ“– System Docs
1need you now
0running for you
14finished
β™₯ Watchers healthy Β· last check just now

Needs you now

1

Only true decisions or exhausted safe recovery appear here.

🌟 GHL funnel / Finish pipeline operating system (07.31. 18:15)

! needs you
Your decision: Owner decision required: CAL-01 authenticated Google Calendar browser evidence is blocked by mobile 2FA. Wait without further work until Matt chooses whether to approve the phone prompt or explicitly accept weaker API-only evidence.
NowWaiting for Matt
NextOwner decision required: CAL-01 authenticated Google Calendar browser evidence is blocked by mobile 2FA. Wait without further work until Matt chooses whether to approve the phone prompt or explicitly accept weaker API-only evidence.

What happens next

Who keeps it moving

πŸ›‘ AI watcher is active and will handle technical stalls

Detailed work plan
  1. βœ“ Read instructions and mission
  2. βœ“ Inspect current state and plan
  3. ↻ Implement mission deliverables
  4. β—‹ Run review and QA
  5. β—‹ Document and finish session
  6. β—‹ Commit, push, and report

Running with AI watcher

0

These workers are active. Technical stalls are handled automatically.

No cloud work is running.
Completed runs (14)

πŸŒ‹ Fusion / Polish final client review pages (07.31. 08:48)

βœ“ done
NowPublished and verified the complete 46-preview Fusion client review with 520 sanitized comments, two clean QA rounds, and a pushed working branch
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Read instructions and inspect state
  2. βœ“ Execute presentation handoff
  3. βœ“ Verify deliverables and QA Β· pass 21 until
  4. βœ“ Write durable run record
  5. βœ“ Finish session and commit
  6. βœ“ Push branch and report

πŸ€– --help / --help

β€’
NowNo active worker
NextNo action unless you choose to restart it

What happens next

Who keeps it moving

πŸ›‘ Run inactive; no AI watcher is running

β˜€οΈ codex-smoke / Verify AI watcher recovery (07.29. 17:12)

βœ“ done
NowForced-stop recovery verified with the original Codex session, watcher thread, and run ID; report committed and branch pushed
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ initialize
  2. βœ“ wait for forced-stop test Β· pass 2 until Operator forced-stop window completes or worker resumes
  3. βœ“ verify resumed identity
  4. βœ“ finish

🎯 ColdEmail / Verify corrected repository lock (07.29. 15:48)

! failed
NowVerification probe stopped safely; no repository changes
NextNo action unless you choose to restart it

What happens next

Who keeps it moving

πŸ›‘ Run inactive; no AI watcher is running

Detailed work plan
  1. βœ“ Inspect repository instructions and lock state
  2. ↻ Verify pre-agent rejection behavior
  3. β—‹ Document, review, and ship branch record

πŸͺ¨ ColdEmail / Verify Codex cloud control path (07.29. 15:44)

βœ“ done
NowVerification-only smoke test passed; audit records committed and pushed on codex/cloud-workflow-hardening
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Verify safe local run prerequisites
  2. βœ“ Record, document, commit, and push audit

πŸ€– ghl-funnel-nts / ghl-funnel-nts

β€’ stopped
NowNo active worker
NextNo action unless you choose to restart it

What happens next

Who keeps it moving

πŸ›‘ Run inactive; no AI watcher is running

β˜€οΈ ColdEmail-contractor2500 / Build 2,500 verified HU contractor leads (07.27. 15:09)

βœ“ done
Now2,715 verified home-contractor leads (2,463 valid + 252 catchall) Β· 14/14 gates green Β· $11.38 of $50
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Pre-flight: disk/RAM, creds, live budgets
  2. βœ“ Hygiene: exclusion cleaner + freemail-gate tests
  3. βœ“ P0 probe: 3 gmaps cells + MX sweep + 200 NB credits
  4. βœ“ P1 free lanes: OSM, owned-crawl, Common Crawl
  5. βœ“ P2 paid gmaps July tranche (<=$16)
  6. βœ“ P3 paid gmaps August tranche (<=$34)
  7. βœ“ P4 free contact extraction waterfall
  8. βœ“ P5 MX triage + NeverBounce verify ALL
  9. βœ“ P6 assemble + 13 QA gates
  10. βœ“ P7 deliver: CSVs, sheet tab, run report

πŸ† telegram coach / SELF OS v3 β€” planning loop: durable fill, self-driving session, prep-skill rewrite (07.27. 01:26)

βœ“ done
Now24/26 green (0 RED), deployed + verified live; sim below bar but proven to be n=5 noise; main NOT merged
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Orient + sync nested repo
  2. βœ“ Baseline QA (24 RED)
  3. βœ“ C1 durable fill (V3-1..5)
  4. βœ“ C2 self-driving session (V3-6..12)
  5. βœ“ C3 prep skill (V3-13..16)
  6. βœ“ C4 research packs (V3-17..18)
  7. βœ“ C5 workbook UX (V3-19..20)
  8. βœ“ C6 session identity (V3-21..22)
  9. βœ“ C7 gates + paid sim (V3-23..25)
  10. βœ“ Deploy + live verify (V3-26)
  11. βœ“ Report + finish-session + push

πŸ—ΊοΈ ColdEmail-hu12k / Build 12,000-lead HU redesign table (07.26. 20:49)

βœ“ done
Now12,231-row HU redesign-lead index Β· 2,966 sendable queue Β· 12/12 QA gates Β· $2.43/$100 Β· frozen + upkeep installed
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Phase 1 infra: budget/suppression ledgers, gates, controller
  2. βœ“ Probes P1 (Apify economics) + P6 (grader model)
  3. βœ“ Phase 2 owned assets: tail, census, email-less, HTML audit, sibling union
  4. βœ“ Phase 3 regrade engine (Lighthouse T1 + consensus T2) Β· pass 0 until 17,262 domains audited, severity-scored
  5. βœ“ Phase 4 free reservoirs (OSM + Common Crawl .hu)
  6. βœ“ Phase 5 contact waterfall (email discovery)
  7. βœ“ Phase 7 verification + hygiene
  8. βœ“ Phase 8 assemble targets.csv, QA gates, sheet upload

πŸ† uncategorised / Mission: Thorough 3-month forensic analysis of Vincze Norbert's (07.26. 20:00)

βœ“ done
NowNorbert did real work β€” 678 changes on 30 days β€” but 32 days of portfolio-wide silence, and 596 'conversions' are only 36 real ones
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Read prior audit + set up API/browser access
  2. βœ“ Extract change data per account (8 subagents)
  3. βœ“ Cross-check API vs UI, save raw JSON
  4. βœ“ Write markdown deep-dive analysis
  5. βœ“ Build 5-view HTML report
  6. βœ“ Deploy to Cloudflare + verify live
  7. βœ“ Run record, changelog, commit, push

🎯 uncategorised / Grant reactions:write scope to Slack app (07.25. 17:09)

βœ“ done
Nowreactions:write granted + ack() proven; CDP :9222 supervised; ops changelog logged
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Identify the Slack app + token in use
  2. βœ“ Confirm reactions:write is missing (API probe)
  3. βœ“ Add scope in api.slack.com app config
  4. βœ“ Reinstall app / refresh token
  5. βœ“ Verify reactions.add succeeds live
  6. βœ“ Report + commit

🦦 AI-lifeOS-tools / Slack Reply Relay (07.25. 15:49)

βœ“ done
Nowslack wiring smoke test complete
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. βœ“ Capture thread + notify.sh slug
  2. βœ“ Build slack-relay.py daemon
  3. βœ“ Install as persistent service
  4. βœ“ Stale-lock reclaim bonus
  5. βœ“ E2E test
  6. βœ“ Docs
  7. βœ“ Ship: commit/push/sync/notify

πŸͺ kertujitok / Deploy GFN phone-whitespace fix live (07.24. 11:12)

↻ stalled
Nowstarting: GFN whitespace fix deploy + call-conversion retest
NextNo action unless you choose to restart it

What happens next

Who keeps it moving

πŸ›‘ Run inactive; no AI watcher is running

Detailed work plan
  1. βœ“ Apply source fix (navbar+footer)
  2. ↻ Deploy both blocks live in GHL + verify
  3. β—‹ Retest GFN swap live (wcm diagnostic)
  4. β—‹ Commit + report verdict

πŸŒ‹ csupi / Finish Track A missions and postmortem (07.20. 17:44)

βœ“ done
NowAll 5 Track A missions live-verified + Track B postmortem shipped to production
NextReview the result, then pull it back when useful

What happens next

Who keeps it moving

πŸ›‘ Run complete; AI watcher has stood down

Detailed work plan
  1. ↻ Reviews widget live (Places API + KV)
  2. βœ“ Visual QA loop on 10 new + 3 old pages Β· pass 1 until clean at 1280/768/390, no defects
  3. βœ“ Fix GSC duplicate-canonical errors
  4. βœ“ SERP competitor analysis
  5. βœ“ GBP optimization (if access landed)
  6. βœ“ Track B: run-1 postmortem + skill refinements
  7. βœ“ Ship: merge->main->deploy->verify live