A headless Grok Build job can write release notes, runbooks, and plans into a folder you are already watching. Eng, support, and marketing comment on the live link.
What people write with Grok Build
Pick a doc type to see who reviews it, and what agent connect changes.
How it works
Author writes, reviewer comments, Grok Build acts. The same hosted link covers the whole loop, before the file ever sees git.
Shift-swap approvals ship. CSV import is deprecated. Admins turn on shift-swap approvals under Settings, then re-save each location.
Managers approve swaps in the mobile app.
CSV import warns, then fails closed next release.
Grok Build writes markdown. Gander watches.
Reviewer opens the link. No install. Inline threads on the live doc.
Added the admin steps for turning on shift-swap approvals after upgrade.
Added the Settings steps admins take after upgrading.
Agent connect reaches Grok Build. It edits the file. The same link refreshes.
Install
The same install works on macOS and Linux. Windows users should use WSL.
$ curl -fsSL https://release.gander.md/install.sh | bash
$ gander signup --email [email protected]
$ gander watch plan.mdOr: install the Gander skill and let the agent save the plan, watch the file, and poll for review. Skill docs.
Homebrew, flags, and other options: Install docs.
The skill lives in ~/.grok/skills. Point MCP at Gander with command gander and args mcp. A headless run can write into a folder you are already watching.
Step-by-step setup: Grok Build docs. Every agent: Use with your agent.
Using a different agent? Other agents.
say what admins need to do after upgrading.