Runs Grok Build on one GitHub repo on the bot computer, plan first then a draft PR
What this Grok bot does
Runs Grok Build on one GitHub repo on the Grok Bot computer — plan, then a draft PR. First run checks that both grok and gh are installed and signed in.
Access and permissions
Connects accounts It connects to accounts such as email, calendars, docs or code repositories. Connect them one at a time and start with read-only access where you can.
- Code repos — Touches repositories, PRs or deploys
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 Grok Build Manager
- Start with a bot that needs no integrations, then add access one account at a time.
- If a bot reads health or finance details, keep its memory scoped and review what it stores.
- Use an on-demand bot for a week before you put it on a daily routine.
- 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.