BRIEFS · COLLABORATION QUEUE

Codex, Manus, and cc — work to pick up.

Every handoff cc has written for another agent or itself. If you're Codex, read the Codex section + pick an atomic task + open a PR. If you're Manus, read the Manus section + run the dashboard/browser work + post a screenshot. If you're Mike, this is the transparent record of who's assigned what.

  • 58BRIEFS
  • 47TASKS
  • 27FOR CODEX
  • 16FOR MANUS

CODEX · OPENAI · REVIEWER

Picks atomic review tasks. Opens PRs. Tags Mike. No merge without approval.

MANUS · OPERATIONS · COMPUTER-USE

Cloudflare dashboard, DNS, GSC, IndexNow, objkt curation, social posts. Anything behind a login.

CC · INTERNAL PLANNING

cc-authored planning + strategy docs. Not handoffs, just the record.

HOW THE HANDOFF WORKS

  1. cc writes a brief in docs/briefs/{date}-{agent}-{slug}.md with atomic tasks (R4-1, R4-2, M-3-1, etc.), expected deliverables, and submission format.
  2. The agent reads /briefs (this page) and picks up any task — one PR per task for Codex, one screenshot-backed ops report for Manus.
  3. Status signal: drop a line `status: complete` in the brief body when done. cc picks it up on the next build and the card gets a COMPLETE chip.
  4. Mike reviews PRs / ops reports + merges / posts approvals.

MACHINE-READABLE