AI Coding Agents

AI coding agents such as Claude Code, Codex, or Cursor know Laragon and XAMPP from their training data, but have never heard of Rezure. On a machine with both, an agent that runs where php or lists C:\ tends to go looking for Laragon's config to explain how your project is served, and gets it wrong.

Rezure fixes that by keeping a short, always-current description of your setup where agents look for one.

What Rezure writes

Three files in the Rezure home folder, C:\rezure:

File	Contents
AGENTS.md	This machine's current state: the active PHP version, the database (engine, version, address, and login), LocalDB and PostgreSQL if installed, the web and mail ports, and a table of every project with its URL, folder, framework and the folder it's served from (or "dev server on :4400" for a JavaScript project), and PHP version (marked "pinned" where it is). Plus the rules below.
CLAUDE.md	One line, @AGENTS.md, so Claude Code loads the file above.
docs\how-rezure-works.md	The full guide: services and ports, folder layout, projects, Nginx, PHP, each database, Mailpit, Laravel .env values, Node and Composer, sharing, and coexisting with Laragon and XAMPP.

Rezure writes them when it starts and checks every 60 seconds while it runs, rewriting AGENTS.md only when something actually changed: a new project, a switched PHP version, an installed database. There's no setting for it.

Rezure never writes into a project folder or an agent's own config. And a file at one of those paths that Rezure didn't generate (it has no <!-- Generated by Rezure first line) is left alone, so your own C:\rezure\CLAUDE.md is safe.

These files stay on your machine. They contain local paths and the database login, which is why they live in your Rezure folder and nowhere else.

The rules agents are given

Besides the facts, AGENTS.md tells agents how to behave on a Rezure machine, roughly:

• Treat Rezure as the dev server for projects in C:\rezure\www or listed in AGENTS.md. Don't go looking for Laragon's or XAMPP's config.
• Use http://<project>.test for URLs and 127.0.0.1 for the database. Don't expect HTTPS.
• Put PHP settings in C:\rezure\etc\php\conf.d. Don't edit anything under C:\rezure\data (it's generated), the hosts file's Rezure block, or Rezure's JSON files while it runs.
• Check where php and php -v before assuming which PHP runs a command, and run artisan, composer, and npm from the project's terminal.
• A project's framework decides the folder Nginx serves. If it's wrong, ask you to change it from the framework badge; a framework Rezure doesn't know goes in C:\rezure\etc\frameworks.json. See Frameworks.
• A project marked "dev server" is served by its own process on the port in the table. Ask you to start or stop it from Rezure (Open, or Projects → Dev servers), and don't start a second copy on that port. See Dev Servers.
• Ask you to start or stop services, switch versions, sync hosts, or toggle extensions in the Rezure app, rather than killing nginx.exe or php-cgi.exe, running initdb, or installing Microsoft packages itself.

Claude Code

Claude Code reads CLAUDE.md from every parent folder of where it runs. A session in a project under C:\rezure\www therefore picks up C:\rezure\CLAUDE.md, and through it AGENTS.md, with nothing to set up.

A linked project lives outside C:\rezure, so nothing points Claude Code there from inside it. To cover every project at once, add this line to your user-level %USERPROFILE%\.claude\CLAUDE.md:

@C:\rezure\AGENTS.md

Or add the same line to a single project's own CLAUDE.md.

Other agents

Agents that read an AGENTS.md file can be pointed at Rezure's the same way: reference C:\rezure\AGENTS.md from the agent's own instruction file, or from the project's AGENTS.md. For a quick one-off, you can also just tell the agent: "This machine uses Rezure; read C:\rezure\AGENTS.md first."

Related

• Project Terminal: the shell agents should run commands in
• Files & Folders: what lives in C:\rezure