Employee fleets with a chief of staff
One fleet per person. A chief of staff. You still cap spend.
shared by @brandon_ai ↗
How it's set up
Every employee at their agency should have a Grok Bot fleet with a chief of staff, they posted. Employees have fleets, they have a fleet, and they have swarms that work together, with Agent-Ops on GitHub as the shared source. Token use is heavy, they said. We have the tweet. No dollar. No public install.
- 01Give one person one fleet. Name a chief of staff. One job list.
- 02Scope each tool so workspaces do not mix. Cold outbound waits for your yes.
- 03Cap tokens. They said heavy use burns the bill. Watch the cap.
- 04Keep the shared files in one place you already use.
- 05Write a fee from work you billed. Do not invent a dollar.
Prompt
We cannot write an honest starter prompt from what was published. Use the steps above.
How the money works
A shop that runs this way still bills clients for the work people ship. They posted no dollar. First proof is one named fleet with a spend cap — not an agency month we have not seen.
What to try first
This week: one named fleet, a spend cap, and you still approve outbound.
Watch out
- Tokens: fleets and swarms can burn the week. Cap the run.
- Time: one checked fleet beats a swarm you did not read.
- Claim: Employee fleets with a chief of staff, plus swarms, are what they posted. Not an agency we sat. Not a public install.