Windsurf rules are now Devin rules: where they go
Windsurf became Devin Desktop on June 2, 2026. Project rules now go in .devin/rules/*.md; .windsurf/rules/ and a root .windsurfrules are still read as fallbacks, so nothing you have breaks. For rules your team shares across agents, an AGENTS.md does the same job, and most other agents read it too.
What happened to Windsurf rules?
The Windsurf app became Devin Desktop through an over-the-air update. Its FAQ says it "continues to read all of your existing Windsurf rules" and nothing needs to change. What changed is the preferred location: .devin/ is now the primary workspace directory, .windsurf/ the fallback.
docs.windsurf.com redirects to docs.devin.ai/desktop, which documents rules under Devin Local Customizations.
Where do Windsurf (Devin Desktop) rules go?
| Path | Scope | Status |
|---|---|---|
.devin/rules/*.md | Project, one rule per file | Preferred; takes precedence over .windsurf/rules/ |
.devin/global_rules.md | Project, one always-on file | Current |
~/.devin/rules/*.md, ~/.devin/global_rules.md | You, in every project | Current |
AGENTS.md, AGENT.md, AGENTS.local.md | Always-on rules, per directory | Current; read from the workspace root down to the working directory |
.windsurf/rules/*.md, .windsurf/global_rules.md | Project | Legacy; imported by default |
.windsurfrules | Project, single file at the workspace root | Legacy; still read, with no .devinrules equivalent |
System-wide rules that enterprise admins deploy move from the Windsurf system directories (on macOS, /Library/Application Support/Windsurf/) to the Devin ones (/Library/Application Support/Devin/); both are read.
How do I write a Windsurf rule file?
Each rule is a Markdown file whose trigger: frontmatter decides when it applies:
trigger | Applies |
|---|---|
always_on | Every session |
glob | When the agent works with files matching globs |
model_decision | When the agent decides the rule's description is relevant |
manual | Only when you invoke it |
.devin/rules/tests.md (the example from Devin's docs)
---
trigger: glob
globs: "**/*.test.ts"
---
All test files must use `describe`/`it` blocks and mock external API calls.
A model_decision rule needs a description, since that is what the agent judges. The current docs state no character limit for rules; older Windsurf docs' per-rule limits are gone.
What does a Windsurf rules directory look like?
A rules directory that leaves shared rules in AGENTS.md
AGENTS.md # commands, layout, conventions: read by most agents
.devin/
rules/
migrations.md # trigger: glob, globs: "db/migrations/**"
release.md # trigger: manual
workflows/
deploy-preview.md # run as /deploy-preview
Both directories hold one Markdown file per rule, so moving from .windsurf/rules/ is a directory rename. Devin Desktop can also import .cursor/rules .mdc files into .devin/rules/.
Windsurf rules vs AGENTS.md: which should I use?
Use AGENTS.md for what always applies: build and test commands, layout, conventions. Devin Desktop reads it as an always-on rule, per directory, as do Codex, Cursor, Copilot, Devin cloud and others, so a teammate on another agent gets the same instructions. .devin/rules/ adds what AGENTS.md can't: rules that load only for matching files, only when relevant, or only on request.
AGENTS.local.md is read too, for personal rules kept out of version control.
Where do Windsurf workflows go?
In .devin/workflows/ (or the legacy .windsurf/workflows/), one Markdown file each, capped at 12,000 characters. Run one in Cascade with /name-of-workflow. Personal global workflows stay in ~/.codeium/windsurf/global_workflows/.
Does Devin (the cloud agent) read Windsurf rules?
It pulls them into its Knowledge: Devin's docs list .windsurf, .rules, .mdc, .cursorrules, CLAUDE.md and AGENTS.md among the files it reads. It also looks for AGENTS.md before it starts coding and includes the first 16 KiB of each.
Do popular repos commit Windsurf rules?
Almost none. We read the whole file tree of 388 GitHub repos on our board on 2026-11-16 and counted repos with each file:
| File | Repos |
|---|---|
.windsurf/rules/ | 0 |
.windsurfrules | 1 |
.cursor/rules/*.mdc | 13 |
| AGENTS.md, anywhere in the tree | 218 |
The census didn't look for .devin/rules/, which is only months old. What these projects commit for every agent is in AGENTS.md.
Questions people ask
- Is .windsurfrules deprecated?
- Legacy, but still read at the workspace root. There is no single-file
.devinrules; new rules go in.devin/rules/, one per file. - Where are Windsurf global rules now?
~/.devin/rules/*.mdor~/.devin/global_rules.md.- Do I need to rename .windsurf to .devin?
- No. Devin Desktop falls back to
.windsurf/. If both exist,.devin/rules/takes precedence. - Does Devin Desktop read AGENTS.md?
- Yes, as always-on rules:
AGENTS.md,AGENT.mdandAGENTS.local.md, in each directory from the workspace root to the one it works in. - Is there a character limit on Windsurf rules?
- Devin Desktop's current docs state none for rules. Workflows are capped at 12,000 characters each.
From the docs: docs.devin.ai/devin-desktop-faq (new tab) · docs.devin.ai/memories (new tab) · docs.devin.ai/workflows (new tab) · docs.devin.ai/knowledge-onboarding (new tab) · docs.devin.ai/agents-md (new tab)
Check your AGENTS.md · Cursor rules vs AGENTS.md · One file for every agent · What each agent reads · All guides