Use the CARBON marketplace package for a persistent user-wide installation with the complete runtime and all namespaced CARBON skills.
Download carbon-claude-marketplace.zip.
Extract it to a permanent carbon-claude-marketplace folder.
Add that folder as a Claude marketplace and install carbon@carbon-local for your user.
Run /carbon:carbon-help. Claude Code registers CARBON as namespaced skills, not unprefixed slash commands.
Shell commands
cd "$HOME/Downloads"
unzip -o carbon-claude-marketplace.zip -d carbon-claude-marketplace
claude plugin marketplace add "$HOME/Downloads/carbon-claude-marketplace"
claude plugin install --scope user carbon@carbon-local
cd "/path/to/your/project"
claude
Temporary session fallback
unzip -o carbon-claude.zip
cd "/path/to/your/project"
claude --plugin-dir "$HOME/Downloads/carbon"
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.
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.