i left Grok Bot with one side project at 80%, six specialist bots, and...

i left Grok Bot with one side project at 80%, six specialist bots, and one rule: nothing irreversible happens while i sleep the remaining 20% was a chain of small jobs i kept postponing. trace the issue back to its source. choose one owner. build on a branch. run the tests. review the change from a clean context. prepare a preview. remember why the decision was made so i set it up like a tiny night shift Scout watched the issues and kept every task tied to its source. Chief picked the next owner. Forge built and tested. Critic reviewed work it had not written. Ship prepared the preview. Ledger saved the reasoning for the next run all six used the same computer, repo, files, browser sessions, and logins. the task moved forward without me copying context from one tool into another then i removed five inboxes only Chief was allowed to interrupt me. the other bots handed the work forward quietly, with the source, branch, test output, review, and decision history still attached when i came back, Chief had reduced the night to one packet: a branch, test output, review notes, a preview, and one decision waiting merge to main, production deploys, external messages, secrets, spending, and deletion still stopped at the human gate that is the version of multi-agent work that helped me. six workers moved the project forward while the management came back as one decision i put the exact charters, schedules, handoff prompt, and rollout order in the article below. look for the sentence repeated in every charter. that sentence is what lets the whole thing run overnight.

Integrations