PulseDev for Remix.Click it, fix the route.
Click any element in your running Remix app and say what’s wrong. Your agent opens the route or component behind it, and Vite HMR shows the edit before you approve the diff.
One minute of setup.
None of it ships.
Paste one tag into app/root.tsx and start your dev server. Keep the PulseDev app open while you work; it runs the server the widget talks to.
- Add
Paste the script tag.
Put it in app/root.tsx, the layout every page shares. Place it just before <Scripts /> in the Layout. The DEV check keeps it out of production builds.
app/root.tsx {globalThis._importMeta_.env.DEV && ( <script src="http://localhost:3899/widget.js" data-token="YOUR_TOKEN" /> )} - Run
Start Remix as usual.
The widget shows up in the corner of every page. Click it, then click the element you want changed.
terminal $npm run dev➜Local:http://localhost:5173/➜PulseDev:widget connected
It fits how
Remix works.
A click carries more than a selector. The page, the element and its selector go to your agent, which follows them to the right file.
Loader Inspector
View loader data for any route segment with request timing and response details.
Action Debugging
Debug form actions with mutation data, validation errors, and response inspection.
Nested Routes
Visualize the full nested route hierarchy and see which outlet renders what.
Error Boundary Tracking
See which error boundaries are active and what errors they caught.
Remix questions.
- Does it work with Remix v2?
- Yes! PulseDev fully supports Remix v2 with Vite and all its conventions.
- Can I debug loaders and actions?
- Absolutely. PulseDev inspects loader data, action mutations, and form submissions.
- Does it support nested routes?
- Yes, PulseDev visualizes the complete nested route hierarchy and data flow.
- Is there a performance overhead?
- PulseDev only runs in development. It is completely stripped from your production builds.
Your Remix app is running.Go point at the bug.
Windows coming soon. Free to start.