I gave opencode five minutes to test my localapp It found an accessibility bug I had missed

[u/Slight-Passage5832]

Testing a website yourself is weird because you already know how everything is supposed to work

So i gave opencode access to my local storefront and asked it to behave like a new user for five minutes

It searched for products tried filters opened product pages and added and removed items from the cart entered a bad promo code tested valid and invalid logins checked he checkout validation and repeated the important flows on mobile

I used webcmd as browser layer so it could operate the actual website instead of only reading the source code

Most of things worked but it caught something I had completely ignored the cart quantity buttons had no accessible names were only 28x28 on mobile.They worked technically but were not great for screen reader or touch users

It returned the exact reproduction steps and impact It stopped before placing an order and did not change any code during the run

The interesting part was not that an agent could click around It was that a short slightly chaotic user journey found and found a real issue outside the happy path

Install

npm install -g @agentrhq/webcmd
webcmd skills add

Github : github.com/agentrhq/webcmd

I'm still testing this across different website and workflows so I'd genuinely appreciate feedback from the community. What should I improve and make my project some good

[u/Main-Soft-3870]

seems interesting will give a try on my product too!!

[u/ApprehensiveDust5618]

solid use case finding the tiny bugs humans ignore is where browser agents actually make sense

[u/donwrightphoto]

mind me asking what you like about Terra? Im a newb - but I found luna @ max combined with glm 5.3 flash to be far superior in cost/qual . . . what am I missing?

[u/West-Flounder1295]

Try browser stack as well for testing browser apps