Skip to content
Ultracite
Esc
↑↓navigate↵open⌘Jpreview

Warp’s agent reads AGENTS.md, unless WARP.md wins

Warp’s agent reads Ultracite’s rules from AGENTS.md as a project rule, in the Warp app and the Warp Agent CLI alike. Warp has no post-edit hook, so the loop is the one the rules describe: after editing, the agent runs ultracite fix and fixes what’s left. An entry in your profile’s command allowlist lets that run without a prompt.

Warp by WarpChecked against Warp 0.2026.10.07.08.29

# Ultracite Code Standards

This project uses **Ultracite**, a zero-config preset that enforces strict code quality standards through automated formatting and linting.

## Quick Reference

- **Format code**: `npx ultracite fix`
- **Check for issues**: `npx ultracite check`
- **Diagnose setup**: `npx ultracite doctor`

Oxlint + Oxfmt (the underlying engine) provides robust linting and formatting. Most issues are automatically fixable.

…
Ultracite’s rules
Where Warp looks for instructions
  1. 1~/.agents/AGENTS.mdA global rule file that applies to every project, alongside the Global Rules you keep in Warp Drive.
  2. 2AGENTS.mdUltraciteThe repository root’s file, applied whenever you work inside the repository.
  3. 3WARP.mdStill supported. In a folder that has both, Warp uses WARP.md and skips that folder’s AGENTS.md.
  4. 4ui/AGENTS.mdYour current directory’s file, applied automatically and ahead of the root’s on conflicts.
  5. 5api/AGENTS.mdAnother subdirectory’s file, added on a best-effort basis when the agent edits files there.

How Warp reads the rules

Warp treats AGENTS.md as a project rule. It applies the root file and the one in your current directory automatically, and tries to add a subdirectory’s file when the agent edits there.

Precedence
The current directory’s rules file, then the root’s, then Global Rules.
Same folder
Warp keeps one rules file per directory and prefers WARP.md, so an AGENTS.md beside it is skipped.
File name
All caps only: AGENTS.md, not agents.md or Agents.md.
Linking
/init can link CLAUDE.md, AGENT.md, GEMINI.md, .cursorrules, .clinerules, .windsurfrules or .github/copilot-instructions.md to AGENTS.md.
Check it
Rules the agent used appear under References in the conversation.
Open them
/open-project-rules opens the project’s rules in Warp’s editor.

Warp’s agent runs what the rules ask for

Warp’s agent has no post-edit hook, so Ultracite’s loop lives in AGENTS.md: after editing, run ultracite fix, then fix what it reports. Commands go through your Agent Profile’s permissions, where an allowlist entry lets ultracite run without asking.

- **Format code**: `npx ultracite fix`
- **Check for issues**: `npx ultracite check`
- **Diagnose setup**: `npx ultracite doctor`
What the rules tell it to run
  1. 01The agent applies a code diff to your file.
  2. 02Following AGENTS.md, it calls for npx ultracite fix.
  3. 03If the command matches your allowlist, it runs at once; otherwise your Execute commands setting decides whether Warp asks.
  4. 04The agent reads the output and fixes what’s left.

Worth knowing about Warp

  • An allowlist entry for Ultracite

    Add a regular expression such as npx ultracite (check|fix)(\s.*)? under Settings, Agents, Profiles, Command allowlist; allowlisted commands always run without asking. The denylist overrides it, and Run until completion bypasses the denylist unless you turn that off.

  • Review comments the agent acts on

    The Code Review panel shows uncommitted changes, the agent’s included. Leave an inline comment on a line and the agent can act on it in real time, or revert a single hunk yourself.

  • One set of rules for app and CLI

    The Warp Agent CLI picks up the same AGENTS.md, WARP.md and skills as the app, and re-scopes them when you cd, so Ultracite’s rules follow you between the two.

  • The Ultracite skill

    Warp loads skills from .agents/skills/ (its recommended project folder) and several others, from your current directory up to the repository root, so it finds the Ultracite skill init installs. Run /skills in the Warp Agent CLI to browse them.

Warp questions, answered

Does Warp read AGENTS.md?
Yes, as a project rule. Warp applies the AGENTS.md at the repository root and in your current directory automatically, and ultracite init --agents warp writes Ultracite’s rules to the root file.
Why isn’t Warp following my AGENTS.md?
Look for a WARP.md in the same folder. Warp keeps one rules file per directory and prefers WARP.md, so move its contents into AGENTS.md and delete it. Also check the name is all caps: Warp ignores agents.md and Agents.md.
Does Warp read CLAUDE.md?
Not on its own. /init can link an existing CLAUDE.md, .cursorrules, GEMINI.md and a few other tools’ files to AGENTS.md. Ultracite writes AGENTS.md directly, so its rules don’t need a link.
Does Warp support hooks?
Not for its own agent: Warp’s agent docs describe no post-edit hook. Ultracite’s loop runs through the commands in AGENTS.md, and your command allowlist decides whether they need a click.
Where do Warp’s global rules go?
In Warp Drive under Personal, Rules, Global, or in a file at ~/.agents/AGENTS.md, which applies to every project. A project’s rules files win over them when they conflict.

Sources

Keep going

Ship less slop

One command sets up your linter, formatter, editor and agents. Works with Oxlint, Biome and ESLint.