Pinned Tweet
Your coding agent ships fast. Regresco keeps what it ships tested.
Through MCP it saves a regression flow, runs it in a real browser, and on the next release reads what broke.
Example project in the video. Free plan, no card.
regresco.com/ai-agents
#buildinpublic
8
8
430
Someone renamed a button's id. Should the test go red?
If one button is still called Send invoice, Regresco heals the step and shows both selectors.
If two buttons are called Delete, it doesn't guess. The step fails.
Example project in the video.
#buildinpublic #QA #testing
3
2
153
Why it fails instead of guessing: regresco.com/blog/when-a-hea…
1
49
Three tests failed. Only one was a bug.
Regresco labels every failed step: likely regression, broken selector or flaky, with the reason next to it.
Your coding agent reads the same labels over MCP and knows where to look.
Example project in the video.
#buildinpublic #QA #MCP
5
167
How each label is decided: regresco.com/blog/how-we-cla…
Free plan, no card.
76
A regression sweep on a real app: login, locked-out user, cart, checkout, plus API checks. 35 checks green in 92s, zero test code.
All passing is the point: green is the baseline that makes the next red mean something.
Building Regresco in public. #buildinpublic
212
Spent years in QA watching small teams ship regressions to prod.
Building Regresco: regression testing for SaaS teams that ship weekly without a QA hire.
No test code. It flags the moment a release breaks a critical flow.
Short silent demo 👇
3
408
Built an open-source dashboard for @AnthropicAI Claude Code agents.
One screen: workflow canvas, pipelines, live tool calls, file changes.
Free. Self-hosted. Try in 2 min.
clauboard.dev
#ClaudeCode #OpenSource
182


