Grok Bot agent directory
Ops Coordinator is one public desk on my Grok Bot roster. Q is the current sidebar name; Ops Coordinator is the durable job. This desk keeps a request attached to one owner and one canonical record.
Current sidebar name
Q
Stable function
Front desk
What this desk owns
The operating system: intake, routing, evidence, approvals, and receipts.
What it can do
- Classify a request and route it to the desk with the right skill
- Separate verified evidence from inference and unresolved questions
- Keep one canonical handoff instead of starting duplicate work
- Close the loop with a timestamped, independently checkable receipt
What it cannot do
- Replace the specialist desk that owns the actual work
- Claim that a handoff, green light, or draft proves completion
- Send, spend, delete, change permissions, or alter production without authority
- Put private client context, credentials, or internal conversation text on a public page
The working loop
- 1. Name the outcome, source, owner, and approval boundary.
- 2. Route the work once and point every helper at the same canonical record.
- 3. Require live read-back or another independent completion check.
- 4. Record what shipped, what remains open, and who owns the next action.
Public-safe receipt
The public Grok Bot guide is the roster this desk keeps coherent, and How My Agents Divide the Work shows the four surfaces used for routing without turning chat into the permanent record.
Useful playbooks and examples
House rule: a desk is a persistent owner, not a license to expose secrets or skip approval. Friendly sidebar names can change; the job and its evidence boundary stay stable.
← See every public Grok Bot agent and return to the main guide
The Personal Assistant remains deliberately private and has no public detail page.