Install AITS
The engine needs Node.js 20 or later and installs nothing else, because it ships as a single file inside each adapter. Pick the environment you work in.
Requirements: Node.js 20 or later
Claude Code
In Claude Code two commands are enough. The plugin brings the 11 agents, 4 commands, 7 playbooks, 10 execution graphs, schemas, references, the engine as an MCP server and three hooks: one at session start that tells sub-agents where the plugin files are, and two that submit every sub-agent output to the engine, in the foreground or in the background.
/plugin marketplace add fabiolalli/aits-agents
/plugin install aits@aits-marketplaceupdate an existing install (then restart Claude Code):
/plugin marketplace update aits-marketplace
/plugin update aits@aits-marketplacecommands:
/aits:full Should we launch Product X in the EU market in Q2?
/aits:quick Approve this marketing budget reallocation?
/aits:diverge We're stuck between hiring and outsourcing. What else is possible?
/aits:board for last/aits:full runs a complete analysis with human control at every step, /aits:quick a rapid decision where conditional agents join only when a rule calls them, /aits:diverge a purely generative phase with the Critic left out on purpose, /aits:board shows the state of a decision. From 3.0.1 the commands have these names, in 3.0.0 they were /aits:aits-full and so on.
claude.ai and Agent Skills
For any runtime that reads Agent Skills, copy skills/aits/ into the skills folder your runtime reads, for example .agents/skills/aits/ in a project. The skill uses the engine through MCP when available, otherwise through node scripts/aits.mjs, otherwise it declares enforcement: absent.
For claude.ai, zip the content of skills/aits/ with SKILL.md at the root of the archive and upload it as a skill.
MCP client
Point the client to the engine bundled in the skill folder.
{
"mcpServers": {
"aits": { "command": "node", "args": ["/path/to/aits-agents/skills/aits/scripts/aits.mjs", "mcp"] }
}
}tools:
aits_start_runaits_planaits_submitaits_statusaits_gate_respondaits_skip_agentaits_aggregateaits_synthesizeaits_recallaits_record_outcomeaits_calibrationaits_patternsaits_verifyaits_export
when the client supports MCP elicitation, gates are asked to the person through a form and a decision sent by the model is ignored. Set gates.elicitation: never in the configuration to skip the form.
Command line
aits start "Raise the SMB price from 29 to 35 EUR?" --graph go-no-go --mode autonomous
aits submit analytical.json
aits status
aits gate R3#1 proceed --quote "Go ahead, with grandfathering for older customers"
aits synthesize synthesis.json
aits exportaits is node skills/aits/scripts/aits.mjs (or node plugins/aits/server/aits.mjs). Run aits help for every command.
Configuration
Copy aits.config.example.yaml to aits.config.yaml in your project. Without it the engine works, but it cannot tell which models produced the outputs, and the report marks model diversity as unverified. In the file you map each tier (deep, standard, fast) to a model, give each model a family label and choose the memory embedder, local hashing by default or any OpenAI-compatible embeddings endpoint, including a local one.
node skills/aits/scripts/aits.mjs build --target claude-code --config aits.config.yaml --out .this command builds the Claude Code plugin with your own model mapping.
Migrating from version 2
v2 envelopes are accepted by the v3 engine. If you installed v2 as a plugin, update it from the marketplace; if you copied v2 files into ~/.claude/, first remove aits-*.md from agents/ and commands/ and the playbooks/, references/ and schemas/ folders, then install the plugin. v2 memory in .aits/memory/ is not migrated.