For content and social

The draft is done. Editor, claims, and the poster review one link.

Blog posts, social threads, the editorial calendar, and the launch pack. Human threads for taste. Agent connect when the words should change.

The docs you produce now

Posts, threads, calendars, and launch packs are short, and everyone has a note. The agent can rewrite in a minute. The slow part is gathering the editor, the claims owner, and the person whose name is on the post.

What you can review with Gander

A week with Gander

You watch a blog draft Monday and a five-post thread on Tuesday. Both links go to the same three people.

The editor and the claims owner talk in a human thread on the blog. On the social thread, the founder uses agent connect: "@agent this reply reads like an ad, make it a plain answer." The agent rewrites that reply and the link updates. The calendar gets its own link later in the week when someone needs two slots swapped. Finished posts go to the CMS and the scheduler, not into Gander.

What you need

One person on your team runs an agent that writes markdown to a file on their machine (macOS, Linux, or Windows through WSL) and installs the Gander CLI. That person is the author. Everyone else opens the link in a browser. No install, no agent account.

Agents that fit

Grok BotProse-first drafts from a brief, then agent connect back through the Gander MCP server.
Claude CodeWhen the posts live in a repo, the skill and MCP keep agent connect in the session.

Short copy still needs the people who can say no. Give them the live file, not a paste.

See how it works