mpapazian

2 ms·

1.
by mpapazian 1y ago
This is one of our biggest challenges, you're spot on! What we're working on taking this includes a memory layer that agents have access to - thus state changes become part of their knowledge and accounted for while conducting a t
2.
by mpapazian 1y ago
You could definitely do that and get some good results! But if you want a repeatable process with detailed bug reports (including logs, reasoning, etc.) and a large enough search area with agents that can continuously build an understanding
3.
by mpapazian 1y ago
The agents can definitely detect when something is off, given they're using VLMs. They don't necessarily compare it to previous versions, rather they have opinionated takes on whether something looks broken / off. So - yes!
4.
by mpapazian 1y ago
hi! Looking at your swarm results, you might not have given the swarm login credentials to use, which is why most of the runs are failing out. Please feel free to try it again and give them access.
5.
by mpapazian 1y ago
We don't handle mobile yet, but we might get to it at a future date!
6.
by mpapazian 1y ago
ah good catch! Fixed :)
7.
by mpapazian 1y ago
Great question! The swarm takes a first pass to generate tests and can continuously add as it runs again over time. In the off chance it misses specific tests - we have tools to let you build them directly with ai support, either by giving
8.
Launch HN: Propolis (YC X25) – Browser agents that QA your web app autonomously(app.propolis.tech)
116 points by mpapazian 1y ago|37 comments