For Cursor
Ship with Cursor. Hear about production in Cursor.
Vigilia catches what breaks for real users and hands it to Cursor with the evidence, so the agent can fix it in your repo. Then it watches real traffic and tells you whether the fix held.
Built for the loop
Open in Cursor
One click on an incident opens Cursor with the fix prompt and the production evidence already in the chat.
MCP in Agent chat
Your agent lists what’s broken, worst first, reads the evidence, fixes it, and marks it fixed — no dashboard needed.
Deploys and regressions
“Started 12 minutes after your deploy.” And if a fixed error comes back, the incident reopens and says the fix didn’t hold.
Depth on demand
Stack, failing request and what the visitor did are open by default for Cursor-built apps. Copy any incident as Markdown for an issue.
Set up
- Add the tag in your root layout or
index.html— the docs say where for Next.js, SvelteKit, Astro, Remix and more. - Add Vigilia to Cursor from the dashboard’s Connect AI page — one click, then confirm in Cursor.
- Ask the agent: “Use Vigilia to fix my worst incident.” It fixes, you deploy, it calls
mark_fixed. - Vigilia confirms with real traffic — or reopens the incident if the error comes back.
Put production in your agent’s context
Free for one app. MCP is included on every plan.
Questions
What can the agent change in Vigilia?
Only incident status — mark fixed, ignore, reopen — and only with a read & write token. A read-only token can look but not touch. Vigilia never changes your code; your agent does, in your repo.
Does it use source maps?
Yes, when your app publishes them: a crash in a minified bundle is resolved to your own file and line, in the incident and in the fix prompt. In Vite, build.sourcemap: 'hidden' is enough. Without them, incidents still carry the message, the page, the failing request, the stack as it arrived and the visitor’s last clicks.
Does it replace Sentry?
It answers a different question. See Vigilia and Sentry for when to use which — many teams will run both.
What does it see about my visitors?
Technical details of what broke: the error, the page, the request that failed and the clicks just before. Emails, tokens, card-like numbers and query strings are scrubbed in the browser before anything is sent, and the data is hosted in the EU.