PulseDev for Nuxt.Click it, fix the .vue.
Click any element in your running Nuxt app and say what’s wrong. Your agent opens the page, layout or component behind it, proposes a diff, and HMR shows it once you approve.

Where things live in a Nuxt app.
Nuxt spreads a page across several conventions: the route file in pages/, a layout in layouts/, auto-imported components, and styles that might come from a module like Nuxt UI or Tailwind. The DOM you click doesn’t say which of those produced it, but the page URL and the element’s markup usually narrow it to one or two files.
Nuxt 4 moved source files into app/ by default, so pages live in app/pages and components in app/components. Your agent reads the project as it is, and the config snippet below is the same for both versions.
One minute of setup.
None of it ships.
Set up project recognises Nuxt and tells you what to add to app.head.script, with your token and port filled in. It doesn’t edit nuxt.config.ts itself. Nuxt restarts on its own when the config changes. More in the widget docs.
- Add
Add it to the dev environment.
The $development block only merges in when you run nuxt dev. nuxt build ignores it, so the script never reaches production.
nuxt.config.ts export default defineNuxtConfig({ $development: { app: { head: { script: [{ src: 'http://localhost:3899/widget.js', 'data-token': 'YOUR_TOKEN' }], }, }, }, }) - Run
Start Nuxt.
The script goes into the head of every server-rendered page. Open one and the PulseDev button appears once the page has loaded.
terminal $npx nuxt dev
It fits how
Nuxt works.
Nuxt conventions the agent works with, not around.
- composables/useCart.ts
Auto-imports
useFetch() and your composables resolve through auto-imports. The agent edits the file they live in instead of adding an import that shouldn’t be there.
- pages/pricing.vue
Pages and layouts
The page URL goes along with your note, so “only broken on /pricing” points your agent at pages/pricing.vue.
- server/api/plans.get.ts
Nitro routes
Your agent can follow a bug from the page into the server route behind it, because it reads your whole project.
Approve before anything changes
Edits arrive as a proposed diff in the widget. Approve writes them, and Nuxt’s Vite HMR updates the component without a full reload.
Nuxt questions.
- Does it work with Nuxt 3 and Nuxt 4?
- Yes. app.head and the $development override work the same in both. Only the default source folder differs.
- What does it cost?
- Free to start with 1 project, 1 agent and unlimited runs. Pro is $12 a month or $96 a year. Founder Lifetime is $149 once, for the first 200 buyers. Agent runs use the Claude Code, Codex or Gemini plan you already pay for.
- Does it work with Nitro?
- Yes. Your agent can edit server routes and API endpoints like any other file in the project.
- What about Nuxt UI and other modules?
- It works alongside Nuxt UI and other modules. PulseDev reads the rendered page, so it doesn’t need to know your module list.
Your Nuxt app is running.Go point at the bug.
Windows coming soon. Free to start.