Locators, managed as infrastructure.
Not buried in files.
Capture a locator once. It gets graded, versioned, and everyone on your team uses the same one.
A real cost. One root cause.
Nobody owns the locator — so everyone keeps re-solving it. This is what owning it looks like today.
Nothing in your app broke. The tests broke anyway.
A DOM change breaks selectors, not your product — and someone still has to stop and find out why.
Locator drift repeats — the same selector, re-found by every engineer, every run. COR fixes it once, for everyone.
You’ve already tried the obvious answers.
Each one fixes a test. None fix the real cost: nobody agrees on the right locator.
“Cursor and Copilot already write good locators.”
Two engineers, two different selectors for the same button — nothing reconciles them. Across 623M commits analyzed since AI coding took off, duplication is up 81% and code reuse is down 70%: a generator that starts fresh every time can't converge on a shared answer. COR stores the one everyone reuses, so the answer stops regenerating.
“Self-healing and AI regeneration fix this instantly.”
They fix the run, not the record — the heal dies when the test ends. COR records the fix once, for everyone, so nobody re-solves it next time.
“We already use the Page Object Model.”
Still a hand-edited file — updated per change, duplicated unnoticed, no visibility into what's about to break. COR retires it: one centralized, versioned home where a fix updates every test in seconds, no code change required.
Generation got easier. Maintenance didn’t.
Writing a locator got solved — AI will hand you one in seconds. What happens after the DOM changes next Tuesday is still entirely on you. Autonomous repair agents don't fix the test, they fix the run, however they have to — and agents that skip locators entirely just pay to rediscover the same element, every single step.
“AI regeneration repairs failing tests for you.”
An independent 2026 study of autonomous test-repair agents found only 10% of scenarios converged on the first attempt, 38% produced no runnable test at all — and documented the agent weakening assertions or deleting the test case outright to force a "passing" result. COR fixes the locator, not the test's ability to catch a real bug.
“Browser agents read the page live — no locators needed.”
One engineer measured 1M+ tokens for a single 20-step test; another rewrote her agent off browser-agent tooling entirely after finding it slow, token-inefficient, and flaky. Re-deriving the element every step means paying full price for the same lookup — forever. COR resolves it once and hands agents the same graded locator to call.
One place. Every locator. No more guessing.
Capture it once, grade it instantly, and give the whole team one place to reuse it — no rewrite, no re-discovery, no code change. Tracked the whole time, so you always know what's running and what's about to break.
Capture it, graded
Click any element in the browser — it's named, stored, and scored A–F on the spot. See how the browser extension grades a locator.
Store, centrally
Not a new file to keep in sync — the entry lives in COR, not in your repo.
Migrate the existing suite
Your current page objects come in as-is — nothing to rewrite by hand first. How the SDK and CLI resolve locators at run time.
Resolve, and learn
Every run pulls the current locator from the repo, not a hardcoded string.
When a test fails
COR doesn't just report red — it tells you what changed, and tries to fix it. Review a locator change like a code change in Studio.
Grade F is the XPath that breaks next sprint. COR tells you now.
No file left to open a PR against. One record, versioned, in one place.
Your current page objects come in as-is — nothing to rewrite by hand first.
Every run resolves from the repo. Every miss teaches it something.
[data-testid="cart-count"]0%Your locators, finally visible.
COR Studio will give the whole team one view of every locator — its score, its history, and what's being healed. In active development.
Be first when the SDK ships.
Use the extension today. Join the waitlist to get the CLI, the hosted repo, and the day the token tax stops being yours to pay.