PulseDev for Remix.Click it, fix the route.

Click any element in your running Remix or React Router app and say what’s wrong. Your agent opens the route module behind it, proposes a diff, and Vite hot-reloads after you approve.

Remix on Vite and React Router framework mode. Loads in dev only.

Last updated:

PulseDev on a running Remix site: the Growth plan button is outlined with its selector, and a comment box asks the agent to restyle it.

Nested routes, nested fixes.

Remix renders a URL as a stack of nested routes, each with its own module in app/routes. One screen might combine a layout route, a parent with an <Outlet />, and the leaf route that owns the content you clicked. The page URL goes with every note, and the agent uses the route file names to work out which module to open.

Remix has since merged into React Router v7. If your project uses React Router’s framework mode, the structure is the same: app/root.tsx exports the Layout, and the snippet goes in the same place.

One minute of setup.
None of it ships.

Set up project sees Vite and React in package.json and treats this as a Vite + React app. It adds @pulsedev/vite to vite.config.ts (not on npm yet) and looks for an index.html, which Remix doesn’t have. Skip it and paste the snippet into app/root.tsx. About the Vite plugin.

  1. Add

    Add it to the root Layout.

    Put it in the Layout export of app/root.tsx, next to <Scripts />. Vite replaces import.meta.env.DEV with false in production builds.

    app/root.tsx
    {import.meta.env.DEV && (
      <script src="http://localhost:3899/widget.js" data-token="YOUR_TOKEN" />
    )}
  2. Run

    Start the dev server.

    Remix on Vite and react-router dev both serve on localhost:5173 by default. Open a route and the PulseDev button appears after hydration.

    terminal
    $npm run dev

Notes for
Remix apps.

How route modules shape where a fix lands.

  • Loaders and actions

    When the bug is the data on screen, the fix is often in the route’s loader rather than its JSX. Both live in the same module, so the agent has them in front of it.

  • app/root.tsx

    The root Layout

    The Layout export wraps every route and the error boundary, so the button is there on error pages too.

  • Route file names

    Flat routes like _index.tsx, pricing.tsx and pricing.$plan.tsx map to URLs in a predictable way. That naming is what lets the agent get from the URL you were on to the right file.

  • Approve, then HMR

    Edits stay as a proposed diff until you approve them. After that, Vite HMR and React Fast Refresh update the route in the open tab.

Remix questions.

Remix or React Router v7?
Both. The root.tsx Layout export looks the same in each, and so does the snippet.
What about the classic Remix compiler?
The script tag works on any dev server, but the import.meta.env.DEV check needs Vite. On the classic compiler, check process.env.NODE_ENV in root.tsx instead.
I already ran Set up project. What now?
Restore vite.config.ts from the vite.config.ts.pulsedev.bak copy, or delete the pulsedev import and the pulsedev() entry, until @pulsedev/vite is published. Then add the root.tsx snippet.
Does it support nested routes?
Yes. The page URL goes along with your note, so the agent can find every route file that contributes to the screen.

Your Remix app is running.Go point at the bug.

Download for macOS

Windows coming soon. Free to start.