Grok Bot + GitHub

How a Bot connects

Fine-grained personal access token from a Bot GitHub user, scoped to specific repos with the permissions the routine needs. Event triggers on notifications.

The Bot's identity

A GitHub machine user (or GitHub App) with read on code, write on issues, no admin. Don't reuse a human's login. If you did, see shared computer cleanup.

Routines we've run

• On new issue — reproduce if possible, add labels, link related issues, post a triage comment
• Daily — stale PRs without review in 48h: nudge reviewers in Slack
• Weekly — dependency and CI failure digest

Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.

The thing to gate

Pushing code or merging. Bots open PRs; humans merge. No write to main.

Verdict

The engineering-side Bots (repro, triage, nudge) are where xAI's own team started. Keep merge rights human.

Setup notes

• Test every routine supervised until it's produced the right output three times.
• Add the routine's completion line to your heartbeat log so silent failures show up.
• Put the GitHub token in the Bot's connector settings or knowledge file, never in a chat message.