How RunStory works
From the change you asked for to a failure your coding agent can reproduce and fix.
Start with your intent
You ask your coding agent: “Let customers edit their delivery address during checkout.”
RunStory uses that prompt and the resulting code changes to decide which workflows to try in the background.
It uses your software
In a separate environment, RunStory adds items to the basket, starts checkout, changes the delivery address, and continues shopping.
It checks the result of those actions, including behavior connected to the change.
Reports failures
The address saves, but the basket empties. Your coding agent receives the actions RunStory took and evidence of the missing items, so it can reproduce and address the failure.
And verifies the fix
After your agent's fix, RunStory repeats the journey. It checks that the address changes and the basket stays intact.
This is an illustrative example, not a live run. Your team keeps the final release decision.