Try AI Testing Without Handing It Your Product

You should be able to try a testing tool before giving it access to the application your team depends on.

/carbon-demo creates a fresh disposable copy of a bundled sample project, then starts CARBON First Look against that copy. It is a practical way to see the workflow without sorting out access to your own source first.

Watch what happens with and without tests

The sample choices include different kinds of projects, such as a website, a single-page app, and an API. Variants with a small existing test suite let you see how CARBON treats prior automation. Variants without tests show how it begins from the product and its code.

Those are different starting conditions. A useful demo should expose the difference rather than stage the same perfect outcome every time.

The copy gives the agent somewhere to inspect, plan, and execute while keeping the original sample intact. Generated tests and findings belong to that demo run. A failing seeded example is a demonstration result, not independent proof of broad bug-finding performance.

Choose the experience you want to understand

/carbon-demo list the available projects, then create a fresh simple website copy with existing tests and run First Look

Look at the plan before the results. Which behaviors did CARBON choose? Did it inspect the existing tests? Can you distinguish source observations from executed checks? Do the screenshots and reproduction steps explain the findings?

You are evaluating the testing experience as much as the sample application.

When that makes sense, move to a small real feature in your own isolated project. The demo should make that next step obvious, not require faith in a polished screenshot.

Install CARBON at testers.ai/carbon for a supported coding agent such as Claude, Codex, or Cursor.

— Jason Arbon, CEO testers.ai