Self-healing loop

It ships. It looks. It fixes its own bugs.

The agent that screenshots its own work, spots the broken pixel, and reships until the page actually looks right.

Download for Mac

See how it works

preview · localhost:3001/checkout

verify failed

your cart3 items

Mechanical keyboard× 1

$89.00

USB-C cable, 2m× 2

$12.20

Notebook · Field× 1

$14.00

assert failed · total === 0

total$0.00

verify loop · q1self-healing · 3 attempts max

auto-heal attempts before paging you

visual

verification on every UI task, not just green tests

every run

logs a before and after image

How it works

Here is what happens, step by step.

01step
Ship the change
The agent edits files, restarts the dev server if needed, and opens the page that should have changed.
02step
Verify by sight
Codus screenshots the live preview through its embedded browser, then compares the image against your acceptance criteria. Visual or written, it doesn't matter.
03step
Heal or escalate
If the screenshot fails, the agent rereads the diff, finds the bug, edits, screenshots again. Three attempts before it stops and shows you the broken image with full context.

why this matters

Agents shipping confidently-broken UI is the #1 complaint with Cursor and Windsurf.

Code-only verification misses entire categories of UI bugs. Text rendered in the same color as the background. Components that don't mount. CSS that overflows the parent. Codus closes the loop by making the agent look at what it just shipped.

More features

More of what makes codus different.

Visual planner

Draw the architecture. Codus writes the code.

Sketch a diagram. Codus reads the nodes, the edges, and the dependencies, then ships the workflow.

Learn more

Agent behaviour

You set the bar. Codus holds it.

Sliders for testing rigor, security review and response detail — plus a 2D style pad for visual fidelity. Global defaults, per-project overrides, applied live.

Learn more

Mobile companion