Question 1

Does it work with my AI coding agent?

Accepted Answer

That's the point. Refactron verifies a diff whoever authored it: Cursor, Claude Code, Copilot, Codex, a codemod, or you. Via MCP your agent can call it before it lands (early access).

Question 2

What does UNPROVEN mean?

Accepted Answer

Your tests pass, but the changed lines aren't actually exercised by any test, so “green” proves nothing. We say so explicitly and list the tests to add, instead of hand-waving.

Question 3

Does my code leave my machine?

Accepted Answer

No. Refactron runs locally against your real test suite in an isolated shadow tree. Nothing is sent to an external service to make the verdict.

Question 4

How is this different from just running my tests in CI?

Accepted Answer

Refactron scopes the run to the blast radius of the change, tells you when the change is uncovered (UNPROVEN), lands atomically only on green, and produces a signed, reproducible record of why it was safe.

Question 5

What ships today vs. what's coming?

Accepted Answer

Live today: the SQLAlchemy migration + verification report. Building in the open: the MCP server and the CI gate. Join early access to be a design partner.

Blog

Rebranding Refactron

Introducing Refactron: the verification layer for AI code change

Latest posts

Rebranding Refactron

Introducing Refactron: the verification layer for AI code change