
Composal sends a swarm of agents through your product to check that users can still do what they came to do. When something breaks, it captures a recording, logs and steps to reproduce, so your coding agent can make the fix and Composal can verify it.
We're Pandelis, Jonathan and Jan, the founders of Composal (YC F26). We're building the verification scaffolding for autonomous software factories: the part of the loop that is still reliant on humans today, checking whether what the agents built actually works.
Coding agents have made building cheap. Checking has not kept up. Teams tell us about features that pass CI and get approved by a review bot, then fail the first time a real person tries them. So someone still clicks through every flow by hand before a release, or skips it and hears about the bug from a customer.
End-to-end test suites were supposed to solve this. In practice they are tedious to write, they break every time the UI changes, and they are the first thing to rot. As agents raise the pace of shipping, that gap widens every week.
Give Composal an environment to test and the credentials it needs. Our agents learn your product by using it, mapping features and exploring user journeys in parallel with different roles and goals.
For example, testing an invitation flow means following what happens to the person receiving the invite: can they join the right workspace and reach the features they need? A successful API response only answers part of that question.
When an agent finds a problem, Composal captures the evidence. Your coding agent uses it to investigate and make a fix, then runs the scenario again to confirm the result. What Composal learns becomes product knowledge and repeatable scenarios that keep running as your product changes.
We call this Continual Agent Verification: checking that users can still accomplish their goals as the product evolves.
CI checks code, CD ships it, Continual Agent Verification checks that user goals still work as the product changes.
Pandelis spent the last few years building coding agents as CTO at Cosine (YC W23). That team was no different from the teams we talk to now: ship a feature, test what changed, move on, then onboard a customer and find that a flow nobody had touched in weeks was broken. The agents kept getting faster. The checking stayed manual. Composal is the tool we wished we had.
We worked closely together at previous startups in London, and we keep hearing the same question from customers: how do you know an agent's work is ready for your users?
Our ambition is a self-healing software factory: you set the direction and agents carry the work from idea through building, testing and shipping, then keep improving the product. Verification is the first step, because nothing else in that loop can be trusted without it.
Build, Verify, Ship, Improve: a fault is caught and healed without stopping the loop.
If your team uses coding agents and still checks their work by hand, we'd like to test an upcoming feature with you.
Start at composal.com to run your first discovery, or book a call with us directly and we would be happy to setup your first batch of tests for you.
— Pandelis, Jonathan and Jan