Cursor. GitHub Copilot. Windsurf. AI coding tools are shipping features faster than ever. A prompt becomes a component. A request becomes a refactor. What used to take days now takes minutes.
But there’s a blindspot no one talks about.
AI can’t see what it broke
Yes, some AI tools can open a browser and take screenshots. But seeing one screen isn’t the same as understanding the whole app.
An AI agent can write a perfect button component. It can refactor your state management. It can even preview the screen it’s working on.
What it can’t do is see the side effects — the screens it didn’t touch, the states it didn’t test, the flows it didn’t navigate.
A PR that “just adds a button” might accidentally:
- Break the layout on mobile
- Shift elements on unrelated pages
- Cause visual inconsistencies in edge states
- Hide a critical call-to-action behind an overflow
These aren’t logic bugs. They’re visual regressions — the side effects that slip through code review because reviewers are looking at diffs, not screens.
Code review catches logic bugs. What catches visual regressions?
Today, the answer is usually “a QA engineer, if you’re lucky” or “your users, if you’re not.”
That’s a problem. AI is accelerating development, but our review processes haven’t caught up. We’re shipping faster than we can see.
Introducing Regression Check
Regression Check is a GitHub Action that detects unintended UI regressions in your pull requests — automatically, on every PR.
Here’s what makes it different:
| Traditional Visual Testing | Regression Check |
|---|---|
| Requires maintaining test scripts | Zero configuration |
| Compares screenshots you define | Detects side effects you didn’t expect |
| Catches what you’re testing for | Catches what you missed |
| Slow feedback loops | Results in seconds |
We’re not replacing your test suite. We’re catching the regressions your test suite wasn’t designed to find — the unintended visual side effects that happen when AI writes code fast and you ship faster.
Built for the age of agentic coding
The shift to AI-assisted development isn’t slowing down. If anything, it’s accelerating. Tools like Cursor and Copilot are becoming the default way engineers write code.
That’s a good thing. But it means we need new guardrails — not to slow teams down, but to give them confidence that speed isn’t coming at the cost of quality.
Regression Check is that guardrail for visual quality.
- Automatic PR Comments — Regression findings posted directly to your pull request
- Visual Context — See what broke, not just what changed
- Zero Configuration — Works with your existing app, no SDK required
- Fast Feedback — Get results in seconds, not minutes
The graph sees what code review can’t
Regression Check is built on the same foundation as the Natural Graph — the technology that now powers Cortex, our AI-powered technical prioritization platform.
When AI agents can see the graph, they gain spatial awareness of what they’re building. Regression Check extends that awareness to the review process: it knows which screens might be affected by a change, even screens the PR author never touched.
That’s the difference between “did my code compile?” and “did my code break the experience?”
Try it now
Regression Check is available on the GitHub Marketplace. Add it to your repository in minutes:
- Request access and get an API key from the Dashboard
- Store your API key as
NATURALLINK_API_KEYin your repository secrets - Add the workflow to
.github/workflows/regression-check.yml
Every PR now gets automatic visual regression detection.
AI writes code fast. We help you see what it broke. Get started with Regression Check — and join the Cortex waitlist for full-stack technical prioritization.