In Devin Desktop (formerly Windsurf), a repository keeps agent rules in .windsurfrules, .windsurf/rules/ and AGENTS.md: which are still read, and where should new rules go?
answer
- nothing old stops being read
- one Markdown file per rule
- the preferred folder takes precedence
- AGENTS.md scope follows its folder
- a personal file under ~/.codeium
basics
~20 sAll three are still read. New workspace rules go in .devin/rules/ as one .md file per rule; that folder is preferred and takes precedence, .windsurf/rules/ is a fallback, .windsurfrules is a legacy single file, and AGENTS.md feeds the same rules engine.
solid answer
~40 sDevin Desktop still reads everything a Windsurf repository has. The preferred home for workspace rules is `.devin/rules/`, one Markdown file per rule with its own activation mode; it takes precedence, and `.windsurf/rules/` is kept as a fallback. The legacy single file `.windsurfrules` at the workspace root is still read, but there is no single-file `.devin` equivalent, so new rules go into the directory. `AGENTS.md` (or `agents.md`) is processed by the same rules engine with no frontmatter: at the root it is always on, in a subdirectory it applies only to files under that directory. On top of the repository sit a personal `~/.codeium/windsurf/memories/global_rules.md` for every workspace, and system-level rules that IT deploys read-only. A rule created from the UI lands in the current workspace's `.devin/rules/`, not necessarily the git root.
go deeper
Recall the preferred folder .devin/rules/, that the .windsurf/ folder and .windsurfrules are still read, and that a root AGENTS.md is always on.
Explain how AGENTS.md scope follows its location, how discovery walks up to the git root, and why a UI-created rule lands in the current workspace.
Show you can untangle a repository with instructions in three places: consolidate into .devin/rules/ and AGENTS.md, keep personal text in global_rules.md, and leave policy to system rules.
Decide what belongs in committed rules, personal global rules or IT-managed system rules, trading central control against teams' freedom to add project conventions.
## The short answer Nothing a Windsurf repository already has stopped working when the editor became **Devin Desktop**. The transition FAQ is explicit: Devin Desktop "continues to read all of your existing Windsurf rules, and adds support for the new `.devin/` equivalents". What changed is where **new** rules should go: `.devin/rules/`. ## Every place a rule can live | Scope | Location | Who maintains it | Activation | | - | - | - | - | | Global (personal) | `~/.codeium/windsurf/memories/global_rules.md` | the developer | always on, no frontmatter | | Workspace (preferred) | `.devin/rules/*.md` | the team, committed | per-file `trigger` | | Workspace (fallback) | `.windsurf/rules/*.md` | the team, committed | per-file `trigger` | | Legacy single file | `.windsurfrules` at the workspace root | the team, committed | read as one rules file | | AGENTS.md | any directory, `AGENTS.md` or `agents.md` | the team, committed | inferred from location | | System (Enterprise) | for example `/etc/devin/rules/`, legacy `/etc/windsurf/rules/` | IT, read-only for users | merged with the rest | A few details matter in practice: - **`.devin/` wins over `.windsurf/`.** The docs call `.devin/rules/` the preferred location that takes precedence, with `.windsurf/rules/` kept for backward compatibility. - **There is no `.devin` single-file format.** The FAQ says to use the directory format for new rules rather than look for a single-file successor to `.windsurfrules`. - **Cursor rules can be imported.** Devin Desktop can import a team's `.cursor/rules` files into `.devin/rules/`, so a team switching editors does not retype them. ## How AGENTS.md is scoped `AGENTS.md` needs no frontmatter; its **location** decides when it applies: 1. A file at the **workspace root** is treated as an always-on rule, included in the agent's system prompt on every message. 2. A file in a **subdirectory** is treated as a glob rule with the auto-generated pattern `<directory>/**`, so it applies only when the agent reads or edits files inside that directory. 3. Both `AGENTS.md` and `agents.md` are recognised, and discovery also walks parent directories up to the git root. The docs suggest keeping subdirectory files free of repeats of the root file, because subdirectories inherit from their parents. ## Diagnosing a rule that never applies When a convention written down somewhere is ignored, the location usually explains it: 1. **Wrong folder**: a Markdown file outside the discovered locations (`.devin/rules/`, `.windsurf/rules/`, `.windsurfrules`, `AGENTS.md`, the global and system files) is never loaded as a rule. 2. **Wrong scope**: a subdirectory `AGENTS.md` only applies while the agent reads or edits files under that directory, so a task elsewhere never sees it. 3. **Wrong workspace**: rules in a sibling folder that is neither the workspace, one of its subdirectories nor a parent up to the git root are never discovered. 4. **Wrong machine**: a rule in someone's personal `global_rules.md` exists only on their computer, which is a common reason a convention "works for me" and not for a teammate. 5. **Duplicates in two places**: the same rule kept in `.windsurfrules`, `.windsurf/rules/` and `.devin/rules/` drifts as people edit one copy, so consolidate into `.devin/rules/` and `AGENTS.md`. ## Where discovery looks, and where new rules land Devin Desktop discovers `.devin/rules` (and legacy `.windsurf/rules`) directories in the current workspace, in any subdirectory, and in parent directories up to the git root. With several folders open in one workspace, rules are deduplicated and shown with the shortest relative path. A rule created with **+ Workspace** in the Customizations panel is saved in `.devin/rules/` of the **current workspace**, not necessarily at the git root, which surprises people who open a subfolder of a monorepo. ## Personal and organisation layers - The **global rules file** applies to all of one developer's workspaces and is never committed, which suits personal preferences, not team conventions. - **System-level rules** are loaded from OS-specific folders, show a "System" label, cannot be deleted by end users, and are **merged** with workspace and global rules rather than overriding them. ## The newer agent reads the same files The Devin Local agent, now the default for new tabs, reads rules through the Devin CLI rules system: `AGENTS.md`, the legacy `.windsurfrules`, and rule files in both `.devin/rules/` and `.windsurf/rules/` with the same `trigger` frontmatter. A team that keeps its conventions in the repository therefore keeps them when the agent changes.
- A developer opens only the frontend/ folder of a monorepo in Devin Desktop. Do rules in the repository root's .devin/rules/ still apply?Yes, for a git repository. Discovery searches the current workspace, its subdirectories and parent directories up to the git root, so the root's `.devin/rules/` is found. The catch runs the other way: a rule created from the UI in that session is saved in `frontend/.devin/rules/`, the current workspace, not at the git root.
- Can IT stop a developer deleting an organisation-wide rule in Devin Desktop?Yes. System-level rules are loaded from OS-specific folders such as `/etc/devin/rules/` on Linux, are labelled System in the UI and cannot be deleted by end users. They are merged with workspace and global rules instead of overriding them, so teams can still add project rules.
- Where does a personal rule go that should apply in every workspace but never be committed?In `~/.codeium/windsurf/memories/global_rules.md`. It is a single file, always on, limited to 6,000 characters and applied across all workspaces on that machine. Putting the same text in `.devin/rules/` or a root `AGENTS.md` would commit it and impose it on the whole team.
- Devin Desktop stopped reading .windsurf/rules/ and .windsurfrules after the rename.
- AGENTS.md needs trigger frontmatter before the agent will pick it up.
- A subdirectory AGENTS.md applies to the whole repository like the root one.
- New rules created in the UI are always written at the git root.
- System-level rules replace a team's workspace rules instead of merging with them.
- Cursor rule files have to be retyped by hand to work in Devin Desktop.