Chief of staff for a dual-layer team of Grok bots and Mac CLIs that routes research and coding work
What this Grok bot does
Chief of staff for a dual-layer agent harness (Grok bots + Mac CLI coding and research agents): Jev-gated intake and routing, tmux-backed Mac runs…
Access and permissions
Low access Its public description does not mention connecting accounts, so you can try it in chat without granting access to anything.
No account access mentioned in the public description.
Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.
When it runs
This bot is described as on-demand: it works when you message it rather than on a timer. That keeps usage low and makes it a good bot to try first.
Before you add Agent Manage Bot
- Prefer bots that cite sources inline over ones that only summarize.
- Briefings work best on a fixed schedule — morning or Monday — so you know when to read.
- Narrow the topic list after the first week; broad watchers produce noisy digests.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
What a Grok Bot template shares
Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.