How it works
Three steps. No new tools for the reviewer.
Author writes, reviewer comments, agent acts. The same hosted link covers the whole loop, before the file ever sees git.
1
Watch
live · rollout-plan.md
Checkout rollback plan
The agent is drafting this for review before anyone opens a PR. Keep the file local. Comments land on the live link.
Goal
Cut over store checkout to the new payment adapter without a flag-day outage.
Rollout
- Tuesday 10:00 UTC: staff accounts only
- Tuesday 16:00 UTC: 10% of production
- Wednesday: 50%, then 100% if error budget holds
Cursor writes markdown. Gander watches.
2
Comment
You send a link. Reviewer comments live.
3
Act
Updated just now
Rollout
Ship behind rollout_v2. Keep the old adapter in process for two weeks.
- Tuesday 10:00 UTC: enable for staff accounts only.
- Tuesday 16:00 UTC: 10% of production traffic.
- Wednesday: 50%, then 100% if error budget holds.
Cleanup owner: payments platform. Ticket PAY-4412.
@agent comments reach Cursor. It keeps going.
Install
Install for Cursor
The same install works on macOS and Linux. Windows users should use WSL.
Terminal
$ curl -fsSL https://release.gander.md/install.sh | bash
$ gander signup --email [email protected]
$ gander watch plan.md
macOS · Linux · WSL
Or: 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.
Install the Gander skill into Cursor if your setup supports skills; run gander mcp install so @agent comments reach the session.
@agentname the feature flag in this section and say who owns the two-week cleanup.