Docs Use Relia every day
Fix bugs from your editor
Use Relia every day from Claude Code, Cursor or any AI assistant with four questions, from "what needs my attention?" to "did my deploy break anything?".
Once your AI assistant is connected to Relia, you can do your daily Relia work without leaving your editor. Your assistant reads Relia's evidence, and the code changes happen in your editor, with your approval.
Before you start
Your AI assistant is connected to Relia. If not, run this once in a terminal and restart your tools:
npx -y relia-sdk@latest mcp installOpen the repository of the app Relia watches. In a repository set up with Relia, your assistant finds the project id in
.env.local(RELIA_PROJECT_ID) or insrc/relia.ts/relia.tracing.js. With several projects, you can also name the project in your question.On Free, your assistant gets Relia's status and each problem's headline. Explanations and fix plans need Growth or Pro.
Tip: watch Connect Claude Code, Cursor and Codex to Relia (MCP setup) (2 min).
Steps
Ask what needs you.
Use Relia: what needs my attention?Your assistant calls Relia's status tool and answers in plain words, for example "GET /api/search has been failing since just after 3 p.m., 46 users affected".
Ask for the fix.
Show me how to fix it.Your assistant reads the incident and Relia's fix plan: the root cause, the file and the line. It shows you the change before writing anything. Say yes, and it edits the file. Then deploy as you normally do. Getting the fix plan the first time uses one of your plan's monthly fix plans.
Mark it fixed.
Mark it fixed in Relia.Relia changes nothing without your yes, so your assistant asks you first. Say yes, and Relia starts watching real traffic. Once enough requests pass without the problem, Relia confirms the fix and sends "Your fix worked". See Fix it and confirm the fix worked.
Check your deploy.
Did my last deploy break anything?Your assistant reads recent deploys and changes, then what started or got worse after the latest one, and tells you whether the deploy is fine.
Ready-made prompts
Claude Code and other tools list Relia's prompts. In Claude Code, type /mcp__relia__ to see them:
| Prompt | What it does |
|---|---|
fix-top |
Fix the most important problem: finds it, reads its evidence and fix plan, fixes it in your code, then offers to have Relia verify the fix. |
deploy-check |
Did my last deploy break anything? Compares before and after the latest deploy. |
review-pr |
Review this change against production: checks your current diff against how those routes, queries and pages behave live. |
status |
What needs my attention? |
check |
Is Relia receiving everything? |
setup |
Set up Relia in this repository. |
What your assistant can and can't do
- Reads freely: status, incidents, fix plans, Ask Relia answers, dashboards, funnels, requests (
relia_trace), logs, sessions, database queries, page speed, uptime and recent changes. - Asks you first, every time: marking a fix (
relia_mark_fixed), giving a verdict on an incident (relia_set_verdict), "I'm on it" (relia_ack), recording a deploy (relia_report_change) and creating a project. Relia refuses these without your confirmation, and each one is in the project's audit log. - Your role applies: a viewer can't acknowledge, and only owners and admins can mark something expected.
- Can't change Relia's settings, delete data, or see passwords. Relia itself never changes your code.
The full list is in MCP tools.
If something's wrong
- Your assistant doesn't know Relia: restart the tool after
mcp install. In Claude Code, type/mcp, pick relia and choose Authenticate. - It picks the wrong project: name the project in your question, for example "Use Relia project Shop".
- "Upgrade" instead of a fix plan: the project is on Free. See Plans and billing.
Next
Last checked against the product: 1 Nov 2026