Install CARBON

Before CARBONNew to coding agents? Optional setup guidance

For the simplest tester-friendly path, install Claude Desktop and open the folder that contains the code, requirements, test cases, findings, screenshots, results, and documentation you want CARBON to use. You can also install Codex and open that same project folder.

Give CARBON the project, not your whole computer. Open the narrowest directory that contains the relevant work. CARBON uses the context and local capabilities your coding agent can access.

Know before it runs. Every executable local CARBON run opens a protected plan link first, with the exact tests and initial time estimate. Keep it open to watch progress and remaining time update every second.

Recommended for testers

Claude Desktop

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

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

Download for ClaudeZIP · Complete plugin runtime

Terminal installation

Claude Code

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-help. Claude Code registers CARBON as namespaced skills, not unprefixed slash 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

Download for Claude Code

Temporary session fallback

unzip -o carbon-claude.zip
cd "/path/to/your/project"
claude --plugin-dir "$HOME/Downloads/carbon"

Plugin marketplace

OpenAI Codex

The Codex package contains a ready-to-add local marketplace and the full CARBON runtime.

Download and extract carbon-codex.zip into a folder named carbon-codex.
In Codex, open Plugins → Add marketplace.
Choose Local folder and select the extracted carbon-codex directory.
Open CARBON, choose Install, start a new task in your project folder, and run $carbon-help.

Shell fallback

cd "$HOME/Downloads"
unzip -o carbon-codex.zip -d carbon-codex
codex plugin marketplace add "$HOME/Downloads/carbon-codex"
codex plugin add carbon@carbon-local

Download for Codex

Portable package

Cursor

Keep the complete CARBON package together. Because CARBON's framework logic lives in the plugin runtime, copying only the skill Markdown is not a complete installation.

Download carbon.plugin and extract it to a permanent carbon folder.
Open Cursor's Settings → MCP screen.
Add a local stdio server named carbon, command node, with the absolute path to carbon/bin/carbon-mcp.mjs as its argument.
Open your project and ask: Use CARBON to test this automatically.

Download for CursorPortable package · Full runtime + MCP

Local plugin

Antigravity

Install the complete bundle so CARBON's runtime, skills, evidence contracts, and MCP server stay together.

Download carbon-antigravity.plugin.
Extract it into ~/.gemini/config/plugins/carbon.
Restart Antigravity and open the folder containing your project context.
Ask: Use CARBON to test this automatically. If the plugin surface is unavailable, configure the included bin/carbon-mcp.mjs as a local MCP server.

mkdir -p "$HOME/.gemini/config/plugins/carbon"
unzip carbon-antigravity.plugin -d "$HOME/.gemini/config/plugins/carbon"

Download for Antigravity

Any local MCP client

Standalone MCP

Use CARBON's 40 local tools and 44 workflows without a plugin installer, including native Vibium CLI and existing-test compatibility, higher-level test-generation APIs, the carbon-browser/v1 evidence contract, protected live pre-run plans, secure global test context, local TestRail/Xray conversion, and full imported-test bake-in. Node.js 22 or newer is required.

Download and extract carbon-mcp.zip to a permanent folder.
Open your client's Settings → MCP servers.
Add a local stdio server named carbon.
Set command to node and the only argument to the absolute path to carbon-mcp/bin/carbon-mcp.mjs.
Restart the client or begin a new task.

{
  "mcpServers": {
    "carbon": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/carbon-mcp/bin/carbon-mcp.mjs"]
    }
  }
}

Download CARBON MCP

Quick run

Start with one command.

Open your project in your coding agent and run /carbon. CARBON evaluates what needs testing, creates and executes the right checks, and produces an evidence-based confidence report.

Make it specific if you want. Add any plain-English direction after the command, such as /carbon test checkout accessibility using Playwright. In Codex, use $carbon; with standalone MCP, ask CARBON the same thing in natural language.

Download integrity

Confirm exactly what you downloaded.

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

Bring your existing tests

Import locally. Bake every converted intent.

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-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.

CARBON Plugin Feedback

Tell us what CARBON should do better.

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

First run

Open the project. Ask CARBON where to start.

Run CARBON Help first. It reads the project and current change, then recommends the best workflow and next steps without changing anything.

Read the quick start Explore CARBON