TestChimp Studio
In brief: TestChimp Studio is the desktop control pane for TestChimp—plan requirements, run agentic QA, govern releases, and inspect coverage without stitching together a dozen tools.
TestChimp Studio is the companion desktop app for TestChimp: an IDE for software delivery. It takes the same control plane you use in the browser and runs it as a local workspace—so you can go from “what are we building?” to “is it ready to ship?” without hopping across planning tools, issue trackers, CI dashboards, and coverage products.
Marketing overview: testchimp.io/studio. Download and install: Download TestChimp Studio.
Why Studio exists
Going from a story to a confident release still means stitching context by hand:
| You need | Where it usually lives |
|---|---|
| Requirement planning | A TMS, wiki, or issue tracker disconnected from tests |
| Agentic QA | A coding-agent IDE, plus prompts you paste yourself |
| Release sign-off | Spreadsheets, Slack threads, and a green CI badge |
| Execution evidence | Separate E2E, API, perf, security, and UX dashboards |
| Coverage | Schema checkers, RUM tools, and requirement matrices that do not talk |
| QA knowledge | Stories, issues, tests, and traces scattered across products |
Studio consolidates that loop in one desktop workspace. QA can run autonomously while you keep full transparency into posture—and how it lines up with product intent.
What you can do in one workspace
| Surface | What it is for |
|---|---|
| Requirement planning | Author and organize stories and scenarios, then hand them to agents without leaving the app. See Requirement Planning. |
| Agentic QA execution | Run catalog /testchimp workflows—create tests, upkeep, explore, implement—with full local repo context. |
| Release governance | Track testing work per version: test runs, checks, and readiness evidence before you push. See Release Management. |
| Issue tracking | Review and act on issues found by agents and humans, tied back to plans and executions. |
| Execution visibility | Inspect E2E, API, performance, security, and UX runs from the same IDE—traces, comparisons, failures. |
| Coverage & governance | See gaps across requirements, API schemas, and real-user behaviour (TrueCoverage, API contract coverage). |
| QA knowledge-base | Explore how stories, scenarios, tests, releases, and issues relate—then drive the next QA move from that graph. See InfiniTrace / QA Brain. |
The product UI itself still loads from your configured App URL (production by default) and updates independently of the desktop binary. Studio ships the local shell + agent runtime; the web product is the shared source of truth.
Agents on your machine
Studio is built on OpenCode infrastructure. You choose how the local agent is billed and routed under Settings → LLM:
| Option | When to use it |
|---|---|
| ChimpHands | TestChimp’s own coding agent—metered QA credits, same catalog workflows as cloud ChimpHands. |
| Bring your own LLM | OpenAI, Anthropic, ChatGPT/Codex OAuth, or another models.dev / OpenCode provider. Your API key, your bill. |
| Local / custom endpoint | Point a custom base URL at a local or self-hosted model. No ChimpHands credits consumed. |
Studio starts one OpenCode serve for the active workspace, installs the TestChimp skill, and talks to the agent over a local bridge—no cloud tunnel required for the desktop loop. Cloud automations and CI ChimpHands remain available when you want fire-and-forget runs on GitHub Actions.
Studio vs the web app vs a generic IDE
| TestChimp web | TestChimp Studio | Generic coding IDE | |
|---|---|---|---|
| Planning, releases, coverage, QA Brain | Yes | Yes (same product) | No |
| Local repo + agent runtime | No | Yes | Yes (no TestChimp catalog) |
Catalog /testchimp workflows | Via MCP / skill in another host | Built-in OpenCode + skill | Only if you wire the skill yourself |
| ChimpHands / BYO / local LLM | Cloud agent + web chat | Settings → LLM in-app | Per-host subscriptions |
| Best for | Browser access, sharing links | Day-to-day delivery workspace | Implementation outside the QA loop |
Use the web app when you want a URL. Use Studio when you want the control pane and the agent on the same machine as your checkout.
Get Studio
- Download TestChimp Studio — certified installers for macOS, Windows, and Linux, or
npx @testchimp/studioon any of them. - Sign in with your TestChimp account.
- Map a local project folder (plans + tests, same Git mapping as the web app).
- Run a workflow from a story or the Code view—or keep using
/testchimpplaybooks with the local agent.
Updates for certified builds are in-app. See Studio updates.
FAQ
What is TestChimp Studio?
TestChimp Studio is TestChimp’s companion desktop app: an IDE for software delivery that consolidates requirement planning, agentic QA, release governance, issues, executions, coverage, and QA knowledge-base exploration in one local workspace.
How is Studio different from the TestChimp web app?
Studio loads the same product UI from your App URL and adds a local OpenCode agent runtime. The web app remains the shared control plane; Studio is the day-to-day desktop workspace next to your repo.
Which LLM can I use in Studio?
Settings → LLM supports ChimpHands (TestChimp credits), bring-your-own API keys (OpenAI, Anthropic, ChatGPT OAuth, models.dev providers), or a custom base URL for a local or self-hosted model.
Does Studio replace Cursor or Claude Code?
No. Use those IDEs for implementation. Studio is the delivery workspace—plans, releases, executions, coverage, and catalog /testchimp workflows next to a local agent.