A QA agent with its own desk and its own budget.
ChimpHands is TestChimp’s native QA agent. It runs on your CI machines, interactively from the web app or unattended on triggers, so QA work stops competing with your developers’ agents for time and money.
14 days, no credit card.
Problem
Your coding agent is busy shipping features.
When QA runs in the same coding agent as development, it competes for the same sessions, the same context and the same budget. Nobody knows what QA costs, and the release checks wait for someone to start them.
QA work, isolated and accountable.
On your CI
Runs where your code runs.
Built on OpenCode, ChimpHands runs on your CI machines with your repo checked out and your app running, inside your infrastructure.
Built on OpenCode
Interactive or triggered
Chat with it, or let it run.
Work with it in a session from the TestChimp web app, or let automation triggers start it on releases, pull requests or a schedule.
Web app · automations · Studio
Its own budget
QA costs, kept separate.
QA spend is budgeted and audited on its own, per run and per workflow. Save your coding agents for development.
Flex pools · audited per run
The same workflows, without taking a seat.
ChimpHands runs the same /testchimp workflows your coding agent would: run QA, create release, performance and security checks, and ExploreChimp walks.
On your CI machine
Each session checks out the repo at the right commit, starts the app and runs the workflow, then opens a pull request with what it wrote. Your code and data stay on your infrastructure.
Interactive when you want it, unattended when you don’t
Ask for work in a session from the web app and review the result as a pull request. Or set triggers, such as create release when a release branch is cut, run QA on every pull request, or smart smoke and ExploreChimp nightly. Unattended sessions run on flex pools for cost-effective execution.
A budget you can see
QA agent spend has its own budget, broken down by workflow, and every run is audited with its duration, trigger and cost. Your developers’ coding agents keep their own budget, and QA never draws on it.
- Budgeted apart from development.
- Every run audited.
- Flex pools for unattended runs.
Where QA agents usually run.
| Your coding agent | Hosted AI testers | ChimpHands | |
|---|---|---|---|
| Runs on your own infrastructure | Yes | No | Yes |
| Starts on triggers, unattended | Partly | Yes | Yes |
| QA spend budgeted separately | No | Yes | Yes |
| Every run audited | No | Partly | Yes |
| Tests land in your repo as plain Playwright | Yes | Partly | Yes |
| Uses your measured QA posture | With the skill and MCP | No | Yes |
Questions about ChimpHands.
What is ChimpHands?
Do I still need a coding agent?
Where does it run?
Can I use it locally?
Save your coding agents for the code.
Let ChimpHands do the QA on your CI, on its own budget.
14 days, no credit card.