For engineering managers

See the plan while it is still moving. Comment from wherever you are.

Plans, design docs, migrations, and postmortems, on a link you can open between meetings. No repo seat required.

The docs you produce now

Your team's agents are writing plans faster than you can join the sessions. You still need to see the rollout, the risk, and the postmortem timeline before they harden into a PR. You should not need an editor install to do that.

What you can review with Gander

A week with Gander

You open two links on Monday, both from engineers who ran gander watch. One is an implementation plan. One is a migration.

On the plan you leave a human thread asking who is on point overnight. On the migration you use agent connect: "@agent add the customer-facing window to each phase." The author's agent edits the file and replies. You read the update on your phone that night. The same links are what the team will turn into git history later.

What you need

You run the coding agent, run gander watch on the plan file, and send the link. macOS, Linux, or Windows through WSL. Reviewers only need a browser. No IDE, no repo clone, no agent account.

Agents that fit

Claude CodeEngineers already exit plan mode into a markdown file the skill can watch.
CodexA migration drafted in Codex stays a local file the team can comment on.
CursorThe doc lives in the repo folder, and reviewers still only need the link.

You do not need a seat in the agent session to review the plan. You need the link, and agent connect when the plan should change.

See how it works