A standing tech lead that holds the system picture and delegates the coding out
What this Grok bot does
Persistent technical and product lead for a research product.
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 Mercury
- Give each bot in a team one owner and one job.
- Route anything external — email, posts, payments — through a single approving bot.
- Start with a two-bot handoff before building a five-bot org chart.
- 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.
More from @chiefjeeb
Disk Janitor
@chiefjeeb
Frees disk by clearing dead git worktrees and clones, and reports the GB recovered.