Install
Dashboard

Windsurf

coord login does not register Windsurf on its own. Windsurf reads a single global MCP config, so you name it once per machine with coord install windsurf --user, which also adds the coordination rules for every repo.

Set it up

Once per machine, after you have logged in:

coord install windsurf --user

To also write Windsurf's rules file into a repo, for a team that commits it, run this inside the repo:

coord connect --repo-files --clients windsurf

Without --clients, coord connect --repo-files writes Windsurf's rules file when the repo already has a .windsurf/ directory, or when it finds Windsurf on this machine (~/.codeium/windsurf, or windsurf on your PATH) and you say yes to its one question.

Refresh the MCP list in Cascade to pick up the tools.

What gets written

On this machine

coord install windsurf --user writes one entry in ~/.codeium/windsurf/mcp_config.json:

{ "mcpServers": { "coordigent": { "command": "/Users/you/.tower/bin/coord-mcp", "args": [], "env": {} } } }

The path is absolute because desktop apps start MCP servers with a short PATH. Other servers in the file stay. No token is stored here: coord-mcp reads your login from ~/.tower/config.json.

It also adds the coordination rules to ~/.codeium/windsurf/memories/global_rules.md, between <!-- coordigent:start --> and <!-- coordigent:end --> markers. The rest of the file is yours.

In the repo, with --repo-files

  • .windsurf/rules/coordigent.md: the coordination rules, with trigger: always_on front matter so Cascade applies them in the repo.

Windsurf has no per-repo MCP config. In a repo, coord install windsurf without --user writes the rules file only, and prints the global entry it would have written with a reminder to re-run with --user.

coord connect --repo-files also writes Claude Code's repo files; see Claude Code.

Update

coord update

This downloads the current coord and coord-mcp and restarts the daemon. Refresh the MCP list in Cascade to load the new coord-mcp.

Check it

coord doctor windsurf

coord doctor lists windsurf with a ✓ and the config file it found. A ✗ line names the command that fixes it. In Cascade, open MCPs > coordigent, refresh, and ask the agent to call coordigent.status.

What works and what degrades

Coordigent uses none of the optional MCP features with Windsurf: no resources, prompts, sampling, elicitation, roots or server notifications. It does not need them.

  • Files in use. Coordigent has no hook or log reader for Windsurf, so it does not see what a Cascade agent edits. The agent still appears in the project once it calls a coordigent.* tool, and can read status and send messages.
  • Messages. A message or conflict waits until the agent's next coordigent.* tool call, and arrives as a ⚠ COORD: banner on its result. coordigent.message.inbox reads the rest.

Remove

To remove Coordigent from this machine entirely, run coord uninstall (add --dry-run to see the plan first). It keeps anything you edited by hand.

To remove only Windsurf's setup by hand, delete the coordigent entry from ~/.codeium/windsurf/mcp_config.json, the marked block in ~/.codeium/windsurf/memories/global_rules.md, and .windsurf/rules/coordigent.md in each repo.

Next