Grace works where your team already works.
Not another dashboard to remember to open. Grace sits on your GitHub repository, your error tracker and your editor, stops new problems before they land, and shows up as a pull request when there's something to fix.
Connected today
- GitHub
- Sentry
- Your editor
Repository monitoring
Every change checked before it's merged.
On Pro, switch reviews on for an app, and on every push and every pull request Grace reads the change and looks for regressions, fresh technical debt, and security holes, before any of it is merged. The result lands on the pull request as a status check.
- Push / PR opened
- →Analysis
- →PR status
- →Fix plan
Auto-remediation
Turn the alert into a pull request.
When an error surfaces in Sentry, Grace reads the stack trace, traces it back to the cause in your code, and opens a corrective pull request. You review the diff, you merge. That's the whole loop.
- Error in Sentry
- →Root cause
- →Corrective PR
- →You approve
Grace in your editor
Your AI writes the code. Grace checks it first.
Most new code is now written by an assistant, and that is where new problems start. Connect Claude Code, Cursor or the Claude app to the Grace MCP: before your AI writes, Grace tells it what the project already decided; before it commits, Grace reviews the change. With the Claude Code plugin, Grace speaks up on its own. It runs on your model and your subscription, and it's included on every plan, Free too.
- You ask your AI
- →Grace briefs it
- →Review before commit
- →Memory kept
What it looks like on the pull request.
The analysis lands where the review already happens. No new tab, no new login, and nothing merged on Grace's initiative.
The new /admin/export route reads every row for the account but never checks the caller's role. Two existing tests cover the happy path; neither covers an authenticated non-admin.
- Missing role check on a data-export route
- No regression on the 3 revenue paths
- Build, lint, and 61 tests pass
→ Open the fix plan in Grace to have the fix drafted as a pull request.
Illustration of a Grace review. Findings and wording depend on your code.
What Grace connects to, and what it does there.
Connecting the repo is the only step that isn't optional. Everything else is there to shorten the distance between an alert and a fix.
GitHub
GitHub App · Push & PR
Reviews each push and pull request, and reports the result as a status on the PR
Sentry
Error alerts
Reads the stack trace, finds the root cause, opens a corrective PR
Your editor
Claude Code · Cursor · MCP
Briefs your AI with what the project already knows, and checks its changes before they're committed
| Integration | How it connects | What Grace does |
|---|---|---|
| GitHub | GitHub App · Push & PR | Reviews each push and pull request, and reports the result as a status on the PR |
| Sentry | Error alerts | Reads the stack trace, finds the root cause, opens a corrective PR |
| Your editor | Claude Code · Cursor · MCP | Briefs your AI with what the project already knows, and checks its changes before they're committed |
Access to your repo is not a blank cheque.
Grace listens, analyses, and proposes. It opens branches and pull requests; it never merges and never pushes to your default branch. The repos in scope, how strict Grace is in your editor, and which emails you get are all yours to set, and the app is hosted in France.
Connecting the repo takes a minute.
The health check runs on it straight away, and you see what Grace sees before you wire anything else up.