Skip to main content

Changelog

The era of self improvement

A test run should leave the next one better informed.

With v2, agent-qa deepens the loop between running a test and learning from it. Completed runs feed failure analysis, memory curation, and improvement proposals, turning execution evidence into context future runs can use. Here is a first look at what is coming.

Self-improving QA

See the whole failure

Failure analysis looks across the completed run, connecting its steps and artifacts. It helps distinguish an application bug from a test problem or an environment issue, and can leave the verdict uncertain when the evidence does not support a confident answer.

Turn evidence into memory

Observations from a run can become persistent knowledge for future tests. Memory curation retains the run and outcome history behind each change, so useful guidance comes with a record of where it came from. Your corrections to recorded verdicts can also help calibrate the evidence used for learning.

Put proposed improvements to the test

When evaluation is configured, candidate guidance can be replayed against recorded decisions before wider use. Promotion checks and canary evidence help decide whether to advance a candidate, while provenance makes it possible to trace and roll back memory changes.

Keep the learning loop moving

Analysis, curation, and improvement proposals run as durable background jobs. Checkpoints and bounded retries let work recover from interruptions, keeping the learning workflow separate from the test you are running now.

Introducing agent-qa

We’re introducing agent-qa: a QA harness for developers and coding agents, built to test real web and mobile applications.

Describe a journey in plain language, run it against your app, and inspect the actions, screenshots, and checks behind the result.

QA for the future

Why we built it

Coding agents are making software faster to produce. Knowing whether it works still takes time and attention. We built agent-qa to help close that gap: a harness that can exercise real applications and bring evidence back to the people responsible for shipping them. It is our first step toward the verification layer described in our manifesto, where humans and agents work together to ship quality confidently.

Read our manifesto ↗

Inside the dashboard

The local dashboard brings the testing workflow into one place. Browse run history, write and debug tests, and inspect the evidence behind each result. The tour below also shows suites, memory, insights, and workspace configuration.

We’re just getting started

This first release lays the foundation for the verification layer we want to build. We’ll keep shaping agent-qa around real applications, difficult test journeys, and the teams using it. Try it on a flow you care about, inspect the results, and tell us where it falls short. We want to build this with you.