Any skill-based agent

Works with the CLI alone. No gander.md account.

Any coding agent that loads the Agent Skills format (SKILL.md in a named folder) can run the Gander loop. The CLI is the same. You install the skill into a directory that agent already searches, then give it a stdio MCP server whose command is gander mcp.

A shorter product page lives at Use with other agents. If we already wrote a page for your agent, start from Other agents or the all agents list instead.

1. Install the CLI

curl -fsSL https://release.gander.md/install.sh | bash
gander --version

The one-liner already runs gander skill and gander mcp install. After Homebrew or a source build, run gander skill yourself.

2. Put the skill where the agent looks

gander skill writes ~/.gander/skill and links:

If your agent is not in that table, symlink the same folder:

ln -sfn ~/.gander/skill ~/.your-agent/skills/gander

Common dests: ~/.windsurf is actually ~/.codeium/windsurf/skills, ~/.roo/skills, ~/.cline/skills, ~/.factory/skills, ~/.junie/skills, ~/.kiro/skills, ~/.openclaw/skills, ~/.openhands/skills, ~/.pi/agent/skills, ~/.trae/skills, ~/.vibe/skills, ~/.kilocode/skills, ~/.hermes/skills.

Restart the agent. Ask it to list skills, or to "gander this markdown file".

3. Sign up and add MCP

gander signup --email [email protected]
gander mcp install

gander mcp install covers OpenCode, Claude Code, Cursor, and Codex. For every other agent, add a stdio server named gander:

JSON (Cursor / Claude / many IDEs):

{
  "mcpServers": {
    "gander": {
      "command": "gander",
      "args": ["mcp"]
    }
  }
}

OpenCode:

{
  "mcp": {
    "gander": {
      "type": "local",
      "command": ["gander", "mcp"],
      "enabled": true
    }
  }
}

Codex TOML (~/.codex/config.toml):

[mcp_servers.gander]
command = "gander"
args = ["mcp"]

Goose YAML (~/.config/goose/config.yaml):

extensions:
  gander:
    enabled: true
    type: stdio
    name: gander
    cmd: gander
    args: ["mcp"]

Grok Build (~/.grok/config.toml):

[mcp_servers.gander]
command = "gander"
args = ["mcp"]
enabled = true

Use a full path to the binary when the GUI does not inherit your shell PATH.

4. Use it

1. Ask the agent for a plan as markdown. The skill should save ./plans/YYYY-MM-DD-slug.md and offer a gander.
2. After signup, gander watch plan.md publishes https://gander.md/s/….
3. Send that URL. Reviewers need a browser, not your agent.
4. Comments that start with @agent are the inbox. The agent edits the local file, replies, and the link updates.

Agents without a scheduler skip the no-path inbox tool until poll.next_check_at. Polling lasts two idle hours after a gander, then stops.

If MCP is not connected:

gander comments
gander comments plan.md

Only act on threads that start with @agent. Human-to-human comments are not agent work.

5. Verify

gander list
gander comments
ls ~/.gander/skill/SKILL.md

The agent should see the Gander skill and the tools gander_list_comments, gander_reply_comment, gander_resolve_thread, and gander_unresolve_thread.

More: Skill, MCP, Install, Hosted watch, Comments.