Answers
Share Windsurf rules across repos with ~/.devin/rules, and with other agents through AGENTS.md
Published
In Windsurf, now Devin Desktop, rules placed in your home folder (~/.devin/rules/*.md and ~/.devin/global_rules.md) apply to every project on your machine, and AGENTS.md is the way to share rules with teammates on Codex, Cursor or Copilot, since Devin Desktop reads it as always-on rules. Enterprise admins can also deploy rules system-wide.
For Windsurf (Devin Desktop). Vendor facts are from the pages linked below, read on November 18, 2026.
Pick by who needs the rules
- Just you, every repo: put rules in
~/.devin/rules/*.mdor~/.devin/global_rules.md. - The team in one repo: commit AGENTS.md at the root, which Devin Desktop, Codex, Cursor and Copilot all read. Use
AGENTS.local.mdfor personal lines kept out of version control. - Coming from Cursor: Devin Desktop can import
.cursor/rules(.mdc) into.devin/rules/, so one set of scoped rules serves both editors. - Every machine in the company: ask an enterprise admin to deploy rules system-wide.
- Across many repos: sync AGENTS.md from one source repo, as with any other agent.
The numbers
| Measure | Value | Source |
|---|---|---|
| Rule scopes | Home folder (every project), workspace, and system-wide for enterprise admins | Devin Desktop FAQ |
| Instruction files read as always-on rules | 3: AGENTS.md, AGENTS.local.md, AGENT.md | Devin Local customizations |
| Public AGENTS.md files on GitHub | 1,142,784 | Harbor study, 18 Oct 2026 |
Study figures are weighted estimates from 1,935 CLAUDE.md and 1,970 AGENTS.md files sampled from public GitHub repositories on 18 October 2026, with GitHub's own counts for the totals. Every figure is in the study's CSV, and the method is in the study.
What the docs say
- Devin Local: customizations: Place the same files in your home directory to apply them to every project. AGENTS.md, AGENTS.local.md and AGENT.md are read as always-on rules at the workspace root and in subdirectories.
- Devin Desktop FAQ: Devin Desktop reads rules from AGENTS.md files and can import .cursor/rules (.mdc) into .devin/rules/. Enterprise admins can also deploy rules system-wide.
Where Harbor fits
Harbor has no hooks for this agent. Its MCP server can be added to any MCP client, but then the agent has to decide to call it, which is the same weakness as a file it has to choose to open. If this is your main agent, the free fixes above are the answer today.
Read next
- Why Windsurf ignores rules
- Sync AGENTS.md across repos
- Cursor Team Rules
- Share CLAUDE.md rules across repos with ~/.claude/rules, a symlinked .claude/rules, or a managed CLAUDE.md
- Codex shares instructions across repos only through ~/.codex/AGENTS.md, one person at a time
- Copilot organization instructions reach every repo, but only on GitHub.com and in code review
- Gemini CLI reads AGENTS.md only if context.fileName lists it; Antigravity CLI reads it by default
- Every answer, by agent and problem
Questions
How do I make a Windsurf rule apply to every project?
Put it in ~/.devin/rules/ or ~/.devin/global_rules.md in your home folder. Devin Desktop applies files there to every project on that machine.
Can Windsurf and Cursor share the same rules?
Yes, two ways. Both read AGENTS.md, and Devin Desktop can import .cursor/rules .mdc files into .devin/rules/.
Can a company set Windsurf rules for every developer?
The Devin Desktop FAQ says enterprise admins can deploy rules system-wide.