You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarify AGENTS.md layering: workspace replaces project, not layers
Make it clear that workspace and project instructions are mutually exclusive:
- Global instructions are always layered
- Workspace instructions REPLACE project instructions (not layered)
- Project instructions are only used as fallback when workspace doesn't exist
Changes:
- Simplified logic to only read project if workspace doesn't exist
- Updated comments to emphasize replacement vs layering
- Updated documentation to make behavior crystal clear
- Mode extraction only checks workspace OR project, not both
Priority within each location: `AGENTS.md` → `AGENT.md` → `CLAUDE.md` (first match wins). If the base file is found, cmux also appends `AGENTS.local.md` from the same directory when present.
12
13
13
-
**Fallback behavior**: If a workspace doesn't have its own AGENTS.md, the project root's AGENTS.md is used as a fallback. This is particularly useful for SSH workspaces where files may not be fully cloned yet.
14
+
**Fallback behavior**: Workspace instructions **replace** project instructions (not layered). If a workspace doesn't have AGENTS.md, the project root's AGENTS.md is used. This is particularly useful for SSH workspaces where files may not be fully cloned yet.
14
15
15
16
## Mode Prompts
16
17
@@ -22,7 +23,7 @@ cmux reads mode context from sections inside your instruction files. Add a headi
22
23
23
24
Rules:
24
25
25
-
-Workspace instructions are checked first, then project, then global instructions
26
+
-Context instructions (workspace or project fallback) are checked first, then global instructions
26
27
- The first matching section wins (at most one section is used)
27
28
- The section's content is everything until the next heading of the same or higher level
0 commit comments