RunPlan mission control

Tasks

IDTaskPriorityOwnerStatusDone versionChanged
Select a task.

Activity

Latest 60 events

    Agents

    Workers run at home in containers and connect out to here (php artisan mission:worker-token, mission/README.md): the coder (Claude), the reviewer (Codex: reviews, merges) and DevOps (ship, deploys). Each does one run at a time.

        People

        Everyone on the list (MISSION_ALLOWED_EMAILS) sees Mission. Writing to the sheet, requesting releases, starting or talking to agents, merging and deploying also need the person's "Mission control" switch — an opt-in against accidental clicks that an owner turns on or off.

          WhatsApp group

          The bot (its own number, a worker at home) relays the team's group here. Orders only from linked people with the Mission control switch — anything that changes something is repeated back and waits for their yes (DEPLOY for production). Everyone else's messages are kept 90 days to draft tasks from; tick them and draft.

          Orders from the group

            Task drafts

            The manager (Claude) drafts rows in the sheet's columns from the group's messages and checks them against the board. Nothing reaches the sheet until you write a draft: it then becomes the next PH3 task, Status "Not started".

            Release the desktop app

            Queues a Windows build on the build PC (the same request release.sh sends). The PC builds what GitHub has on the branch — push first.