Skip to main content
One command installs Monk and connects it to every coding agent on your computer:

​
What It Does

  1. Installs Monk under ~/.monk/bin, or updates it if you already have it. Every download is checked against a list signed with Monk’s release key, and a download that doesn’t match is refused.
  2. Starts Monk in the background, so your agents can reach it at http://127.0.0.1:7419/mcp.
  3. Finds your coding agents and shows one plan: what it will do in each, and which files it will change.
  4. Asks once. Nothing changes until you say yes.
  5. Sets up each agent the way that agent supports best: the Monk plugin for Claude Code, Codex, Devin and Antigravity, and a monk MCP server entry plus the Monk skill for the others. Every config file is backed up to ~/.monk/agent/setup-backups/ before it is edited. Per-agent details.
  6. Offers to sign you in in the browser. Skip it and you can sign in later from your agent.
It finishes with a summary and how to reload each agent.
Cursor installs plugins from its own marketplace, so the installer doesn’t change Cursor. Install Monk from the Cursor marketplace. The installer still sets up Monk itself, so Cursor finds it running.
The same goes for Grok Build: install Monk from its marketplace with grok plugin install monk --trust, or see Agents.
On first use, Monk also installs its runtime (the monk CLI and monkd) through your package manager: Homebrew on macOS, apt or dnf on Linux, and a dedicated Ubuntu WSL distro on Windows.

​
Options

Options go after sh -s --:
In PowerShell:

​
Updating

Run the install command again. It updates Monk, brings each agent’s Monk plugin or config up to date, and leaves anything already current alone.

​
Is It Safe to Pipe Into a Shell?

The script is short and readable: open get.monk.io/stable/plugin to see exactly what runs. It doesn’t need sudo, and it only installs files that match Monk’s signed release list; if a check fails, it keeps the version you already have. --dry-run shows everything it would change first.

​
Uninstall

Remove the plugin from each agent (see Agents for where), then remove Monk itself:
On Windows, download uninstall-monk-agent.ps1 and run:
To also remove the Monk runtime (CLI and daemon), add --runtime (-Runtime on Windows). Add --keep-data to keep Monk’s local state in ~/.monk/agent.

Agents

Set up one agent by hand

Troubleshooting

When something doesn’t connect