Your stack

AI agent for Vue applications

Vue applications keep their workflow logic in composables and single-file components, which is a readable place for an analyser to find both the fields a step needs and the order steps run in.

What Merlean reads in a Vue codebase

Merlean connects to your repository through GitHub or GitLab and analyses the application rather than recording a user clicking through it. In a Vue project, that analysis draws on:

Vue Router configuration, including nested routes and navigation guards that gate access.
Composables and Pinia or Vuex stores, where API calls and workflow state usually live.
Single-file components, with their form fields, bindings and conditional rendering.
Validation schemas from VeeValidate, Zod or Yup, which give types and required rules.
Nuxt server routes when present, which put part of the backend in the same repository.
The backend repository when it is connected, for authoritative permissions.

The result is a machine-readable model of what the application can do, which fields each action needs, which order multi-step work has to run in, and who is allowed to run it. That model is what user requests are resolved against.

Authentication and permissions

Merlean uses the same credentials your frontend holds - a session cookie or a bearer token - so requests arrive at your backend already authenticated as that user, with all existing checks intact.

Worth knowing about Vue specifically

Navigation guards are a useful permission signal, but they are a frontend convenience. Merlean follows the backend, which is where authorisation is actually decided.
Nuxt applications benefit from connecting a single repository, because server routes and pages sit together and the workflow is visible end to end.
Stores that mutate state optimistically before the server confirms are recognised, so a failed request is reported as failed rather than as the optimistic result.

Getting started

Connect the repository, run the first analysis, and review what Merlean understood. Reviewing is the step worth spending time on: the analysis is derived from your code, so where it is wrong it is usually pointing at something genuinely ambiguous in the application.

Then add the widget with a single script tag, or expose the application over the Model Context Protocol so an AI agent your users already use can reach it.

Frequently asked questions

Does Merlean automate the browser?

No. It calls the endpoints your components call. That is why component refactors and layout changes do not break it.

Does it support Nuxt?

Yes, including server routes and server-side rendering. Nuxt projects are often easier to analyse because more of the system lives in one repository.

Vue 2 or Vue 3?

Both. The Options API and the Composition API are read equally well.

See it against your own application

Merlean reads your repository and shows you what it understood before anything is exposed to a user. The fastest way to judge the fit is to point it at a real codebase.

Get in touch Read the docs