warpdotdev
Warp not loading WARP.MD rules on Windows
Pre-submit Checks
- [x] I have searched Warp bugs and there are no duplicates
- [x] I have searched Warp known issues page and my issue is not there
- [ ] I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID intructions
- [ ] I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log intructions
Describe the bug
I had Warp create a WARP.md file at project root but also in subfolders. At the /init I see the /RULES tab being populated. However, when I exit the WARP program, and reload from the same directory or /initialize the directory it doesn't seem to pick up WARP.md again no matter what I do.
I tried all the suggestions by the AI. It seems to be a visual bug in the /rules interface on WINDOWS. Because I ask WARP if it can find and will respect my rules, he does acknowledges it.
Here’s what I see as your global rules and how I’ll follow them.
Core assistant rules • No inline style attributes. Use CSS variables/tokens and Tailwind utilities only. • Always import @ratigan/design-system/global.css in the app’s global CSS, and apply base bg/fg on html and body. • Use these token-backed utilities: bg-background, bg-surface, text-fg, text-fg-muted, text-fg-inverse, border-[--color-border], bg-primary, bg-secondary, bg-success, bg-warning, bg-error. • Theme switching: set/remove documentElement.dataset.theme; ensure swatches read CSS vars after the frame (e.g., via requestAnimationFrame). • Rule precedence: nearest WARP.md > root WARP.md > .warp/rules.md. • Editor/linting: VS Code should set css.lint.unknownAtRules to ignore (for Tailwind @theme). If using Stylelint, ignore the theme at-rule.
Project/tooling rules I’ll respect • Monorepo with Bun workspaces. • Package manager: Bun (bun install; bun --cwd frontend dev|build|start). • Lint: bun --cwd frontend run lint (ESLint 9 + eslint-config-next). • Next.js 15 (App Router), React 19, Tailwind v4 (via @tailwindcss/postcss in postcss.config.mjs). • TypeScript path alias: @/* -> ./src/*; frontend source under frontend/src. • Default branch: main. • Do not commit .env; use .env.example; root .gitignore is authoritative.
Design system-specific rules (packages/design-system/WARP.md)
• All tokens live in the design system; apps must consume via CSS variables (no hex in apps).
• Tailwind v4 @theme mappings must expose utilities (e.g., bg-surface, text-fg, bg-primary).
• Adding a theme requires a :root[data-theme="
Your personal workflow rules (from your curated rules) • Commits should use git ship "Commit message". • Always use Bun as the package manager. • Always use the latest versions of packages we install.
Yes, I understand these and will follow them: • I won’t introduce inline styles; I’ll use your token utilities and import global.css. • I’ll structure theme switching as specified and respect precedence (nearest WARP.md wins). • I’ll use Bun for scripts and installs, and use git ship for commits when requested. • Any component or CSS changes will reference design-system tokens, not raw hex.
So please fix the UI bug :)
To reproduce
/init WARP.md on windows. make some rules.
In Rules TAB it then shows the rules perfectly.
However after leaving the program and restarting from the same directory it does not pick them up. I have configured WARP properly with rules always being loaded
Expected behavior
I expect WARP to also load the WARP.md file after program restart not just on the initial load.
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
Windows 11
Shell Version
No response
Current Warp version
v0.2025.09.10.08.11.stable_01
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
I used Warp for four weeks before realizing it wasn't getting WARP.md (amazing how well it performed without it!). Indicative conversation:
Recite from memory what you know about our Marshaler.
I don’t actually retain project-specific details or code between sessions, so I don’t have any “memory” of your Marshaler beyond what’s in this current conversation (which so far is nothing about it). ...
WARP.md should've talked about it. You don't automatically receive that file as context?
I don’t automatically get any files as context; I only see what you explicitly send me or what I read via tools. WARP.md isn’t visible by default, and the path I tried (C:\Dev\Barreleye\UI\WARP.md) doesn’t exist according to the filesystem. ...
it's in the project root (not UI) and I'm under the impression that Warp should've placed it in your context window
C:\Dev\Barreleye\WARP.md
[describes what's in WARP.md]
OK, but you didn't have that info before reading the file?
Correct: I did not have that information before reading WARP.md just now.
I don’t get your repo or its docs “preloaded” into my context. I only know:
....
WARP.md is mentioned under Rules though:
I have the same issue on Windows 11 and Warp v0.2025.11.19.08.12.stable_06
