One app for your whole software delivery.
From requirements to release: write the stories, hand them to agents, run QA workflows, review the evidence and ship the release, all in one desktop app. Plans and tests stay in your git repo. Mac, Windows and Linux.
npx @testchimp/studioSign in with your TestChimp account.
Problem
Plans in a ticket.Tests in the repo.Results in five dashboards.
QA work is scattered across a ticket tracker, the IDE, CI, a test case manager and a handful of reports. Every switch costs context, and the agents doing the work see even less of it than you do.
Plan it, run it, prove it.
Studio is the same product as the TestChimp web app, plus a local agent on your machine, beside the repo you already work in.
Plan work
Plans next to the agent.
Write and organise stories and scenarios before you hand them to agents, in the same app.
Markdown in your repo
Run workflows
QA agents on your machine.
Create tests, create a release, run performance tests and UX testers, throughout the delivery cycle.
ChimpHands · Bring your LLM
Track evidence
Every run, every release.
UI, API and performance history, failure traces and releases, without leaving the workspace.
UI · API · performance
From plan to evidence, in one window.
Plan where the agent reads
Stories and scenarios are Markdown files in your repo. Write and organise them in Studio, see each scenario’s coverage, and hand them to an agent without copying anything into a prompt.
Run agentic workflows locally
Create functional tests, create a release, author and run performance tests, run UX testers or capture a manual session. Run them with ChimpHands, your own API key from OpenAI, Anthropic and others, or a local model.
See every run
UI, API and performance execution history in one place, with detailed traces of failures and performance results compared across releases. Act on a failing test from the same screen.
The rest of TestChimp, in the same app.
Releases
Manage releases from your workspace.
Test runs, performance results, security checks and the release delta, to push releases on data.
Release governanceUX issues
Which screens need polish.
Issues ExploreChimp found, laid out by your app’s structure, so you see which screens are slow or broken.
UX postureContract coverage
Is the API contract tested?
Your OpenAPI spec is the contract the product promises. Track the gaps in its coverage and act on them.
Meaningful coverageQA knowledge base
Everything, connected.
Stories, scenarios, tests, releases, results and issues, with the relationships between them to explore.
Install in one line.
Certified installers for Mac, Windows and Linux, or run it with npx. Sign in and map the same project folder you use in the web app.
Any platform
npx @testchimp/studioStarts Studio from your terminal.
Then, in your coding agent
/testchimp run QAThe same workflows run from Studio or from Claude Code, Cursor and other agents, on one source of truth.
Where Studio fits.
| Coding IDEs | Test case managers | TestChimp Studio | |
|---|---|---|---|
| Plans and scenarios beside the code | Partly | No | Yes |
| Coverage and execution evidence | No | Partly | Yes |
| Runs QA agents with your choice of model | Yes | No | Yes |
| Release management | No | Yes | Yes |
| Manual session capture | No | Partly | Yes |
Coding IDEs: Cursor, Claude Code and similar, built for writing product code.
Questions about Studio.
What is TestChimp Studio?
How is Studio different from the TestChimp web app?
How is this different from Cursor or Claude Code?
Can I use my own LLM or a local model?
Does Studio work on Mac, Windows and Linux?
Do I need a separate project for Studio?
Plan, test and ship from one window.
Studio puts your plans, your agents and your evidence beside the repo.
Or run npx @testchimp/studio. No TestChimp account yet? 14 days free, no credit card.