Netlify · Vercel · Cloudflare Pages
Test every redirect before it 404s in production.
Edgewright turns your _redirects and vercel.json into a live console. An AI agent drives it through WebMCP: test any URL, audit for rules that shadow each other, fix the order, export a clean config. Every button runs the same code the agent does.
404 Loaded now: /shop/sale-2026 never reaches the sale.
8 tools registered on this page. The same code your buttons run.
The problem
A broad rule above a specific one is a silent 404.
Redirect and rewrite rules are first-match-wins. The first rule that matches a path wins. The rest never run. Put a broad /shop/* above a specific /shop/sale-2026 and the specific rule is dead code. It works on your machine, passes review, then 404s in production, on a URL a real user hits.
- First match wins. A broad rule above a specific one swallows it. Nothing warns you.
- The rules live in a flat file with no console to test them against.
- Order is the fix. Edgewright makes the order visible, testable and fixable.
The console
Work the rules. An agent works the same table.
Rules
Request simulator
Audit
The agent
Point an agent at this page. Watch it fix the bug.
Walkthrough transcript
scripted walkthrough, real tool output- Press Play the story or ask a connected agent to run the five tool calls.
WebMCP leverage
Eight tools on document.modelContext.
An agent in the browser calls them, the UI re-renders from the same store, so agent and human run identical code. Read-only tools run without a prompt. Tools that change rules ask first.