Install CARBON

Pick your AI coding agent.

Download. Install. Start testing. Local CARBON needs no testers.ai account or API key.

Claude Desktop

Download for ClaudeZIP · Complete plugin runtime

Use Claude's graphical plugin screen for Chat and Cowork. No Terminal is required.

Your Claude plan must support custom plugins. CARBON does not require a testers.ai subscription.

  1. Download carbon-claude.zip and keep the ZIP in Downloads.
  2. Open Claude Desktop and choose Customize → Plugins.
  3. Choose Add plugin → Upload plugin, select carbon-claude.zip, and choose Install.
  4. Open your project folder in Cowork, start a new conversation, and ask: Use CARBON Help to assess this project and recommend next steps.

New to coding agents?

Install Claude Desktop or Codex, sign in, and open your project folder. Then choose your agent above to add CARBON.

Have code? Ask Use CARBON to test this project. No code yet? Ask Run CARBON Demo for a disposable sample project.

What should I give CARBON access to?

Open only the project folder with relevant code, requirements, test cases and evidence—not your whole computer. Review the proposed scope before testing.

Verify your download

Every CARBON package has a published SHA-256 value. Compare your downloaded file with the release checksums before installation.

Accounts, credentials & settings

After installation, run $carbon-settings in Codex, /carbon:carbon-settings in Claude Code, or /carbon_settings in an MCP client. The protected local page lets you save a reusable test username/password, global prompt, and context documents for CARBON runs across projects.

CARBON commands

Use your coding agent's local project and installed browser/API capabilities. No testers.ai account or API key is required.

  • Global test username/password in secure storage
  • Reusable prompts and local context documents
  • Local sites, private previews, source and API analysis
  • Prompt tests, evidence and reports under .carbon

Optional external services

The default public command surface is local. External integrations require separate configuration and approval; do not assume cloud workflows are installed. Store credentials in the protected settings UI, never in chat.

  • Email-based daily and weekly sample routes
  • Managed-browser and full-site runs
  • Cloud history, saved suites and schedules
  • Explicit confirmation for paid or public work
Bring your existing tests

Give CARBON a TestRail or Xray export, CSV, TSV, JSON, JSONL, XML, XLSX, DOCX, supported automation source, or manual test file. It preserves source IDs and hashes, converts the cases to adaptable AI intent, then runs every new intent through the matching local adapter.

Ask your coding agent

$carbon-tests import ./testrail-export.csv
/carbon:carbon-tests import ./xray-export.json
/carbon_tests import ./legacy-tests

Evidence-gated bake

CARBON repairs only converted test-definition failures and reruns them up to the chosen limit. Observed passes activate. Product failures and infrastructure blockers remain drafts with a responsive local report.

Send CARBON feedback

Your feedback is submitted as CARBON Plugin Feedback for CARBON. Name and email help us follow up; the IcebergQA contact option is separate and opt-in.