Other AI coding agents
AGENTS.md works almost everywhere.
AGENTS.md is an open format that many coding agents support. The agents.md project keeps a list that includes Jules, Factory, goose, opencode, Warp, Amp, Junie, RooCode, Kilo Code and Augment Code. If your tool is on it, a vagejs site works out of the box. Here's what to know about a few popular ones.
Devin Desktop (formerly Windsurf)
Windsurf's editor is now called Devin Desktop. Its agent, Cascade, always reads the root AGENTS.md, and an AGENTS.md in a subfolder applies to that folder. Your own rules go in .devin/rules/. In the terminal settings, choose Allowlist Only and add npm run check and npm run build. See the Devin Desktop docs.
Cline
Cline is an open-source agent for VS Code. It supports AGENTS.md as a rules file, alongside its own .clinerules/ folder. If Cline doesn't pick up the vagejs instructions, start your first message with "Read AGENTS.md". Details are in Cline's rules docs.
Aider
Aider doesn't load instruction files on its own. Tell it to read the vagejs file each time:
aider --read AGENTS.mdOr make it permanent in .aider.conf.yml at the site root:
read: AGENTS.mdAider's conventions guide explains how read-only files work.
Zed
Zed's agent uses the first instruction file it finds from a fixed list. A vagejs site has both AGENTS.md and CLAUDE.md, and Zed picks AGENTS.md, which is the one you want. Don't add a .rules file unless it includes the vagejs instructions, because Zed would read that instead. See Zed's instructions docs.
Any other tool
If your agent doesn't support AGENTS.md, you can still use vagejs:
- Start each session with "Read AGENTS.md and follow it."
- Ask it to run
npx vage info --jsonbefore changing settings. - Ask it to finish with
npm run checkand report the result.
Chat assistants without file access, like ChatGPT or Claude in a browser, can help too: paste AGENTS.md and the page you're working on, and run the commands yourself.