Sign up

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

Signup is the line between the two halves of the CLI. Until an API token exists, gander --help lists local preview, local watch, the runner, skill, uninstall, upgrade, and completion. After signup it also lists share, hosted watch, list, remove, invite, comments, MCP, manage, and auth.

You need an account when you want a URL someone else can open, comments, a team, or MCP reading the inbox. You do not need one to render a file on your laptop.

gander signup --email [email protected]

The CLI posts a signup intent, opens the browser form, and polls until you finish. It then writes the token to ~/.gander/config.json (directory mode 0700, file mode 0600). Treat api_token as a password. The default API origin is https://gander.md.

After signup, the loop is:

gander watch plan.md
gander mcp install

gander watch is the hosted link. gander mcp install is how @agent comments come back. If the one-liner already ran MCP install, you can skip the second command.

Token on another machine

The dashboard can rotate the token. The old one stops working. Install the new value on each machine that should keep talking to gander.md:

gander auth gmd_…

The CLI validates the token against GET /api/shares before overwriting ~/.gander/config.json. If the server rejects it, your existing config is left alone.

You can also open the dashboard with gander manage. See Dashboard.

Profiles

One checkout can talk to prod and to a local gandermd without mixing tokens. Set GANDER_CONFIG=<name> to use ~/.gander.<name>/. Field table, permissions, and new-share defaults: Config.

GANDER_CONFIG=dev gander signup --email [email protected]
GANDER_CONFIG=dev gander list
GANDER_CONFIG=dev gander watch plan.md

Profile names must be a single path component: no /, \, ., or ... Named profiles never fall back to a legacy ~/.mdp file.