FrootAI CLI
Build, inspect, validate, and ship the ecosystem from one operator shell.
Operate the Factory and Harvest engines, scaffold canonical primitives, validate protocol conformance, inspect executable capability evidence, preview releases, and drive MCP federation.
frootai + fai binariesMIT licensed$ fai capabilities --json
✓ 13 executable engines ready · 0 unavailable
$ fai engine --help
discover → fetch → extract → retrieve → scaffold → compose → commit
$ FROOTAI_DRY_RUN=1 fai ship all
preview registry checks · version checks · publish plan
✓ no artifacts publishedThe command surface changed after 5.4.2.
The current CLI is an operator tool. End-user Play discovery, architecture search, and guided health checks live on the web, FrootAI MCP, and VS Code. Orchard catalog commands remain available for accelerator discovery and installation.
The command map
Six jobs, one operator surface
Every command belongs to a clear responsibility. Repository writes and publishing stay explicit.
Factory
Harvest primitives, build the canonical catalog, diff changes, transform channel bundles, and validate output.
fai factoryHarvest engine
Discover, fetch, extract, retrieve, scaffold, compose infrastructure, customize, and commit harvested solutions.
fai engine --helpScaffold
Create agents, skills, instructions, and hooks from repository templates with the expected metadata shape.
fai scaffold agentValidate
Run cross-repository consistency and standalone FAI Protocol L0 conformance checks.
fai conformance .Ship
Preview and release one channel or all channels with registry preflight and version-tag enforcement.
FROOTAI_DRY_RUN=1 fai ship allMCP federation
Discover, trust-check, attach, test, invoke, and publish federated MCP areas from a shell.
frootai mcp --helpThe Harvest engine
Repository → grounded, deployable Solution Play
Eight tested stages preserve provenance, isolate writes, and hold publication behind explicit validation and review.
Discover
Resolve and validate an upstream repository before any local mutation.
Fetch
Snapshot allowed files at a pinned commit with bounded resource use.
Extract
Derive structured RepoFacts, provenance, confidence, and safety evidence.
Retrieve
Ground generation in the nearest reference plays and verified corpus.
Scaffold
Generate the play file set, policy overlay, evaluation, and documentation.
Compose
Produce deployable infrastructure under explicit provider and cost policy.
Validate
Apply schema, conformance, trust, WAF, and quality gates.
Commit
Bundle and publish only after review and release controls pass.
Executable evidence
Loaded from code, not a marketing checklist
The inspector requires each backend module, reads its exported command registry and callable contract, and reports its package-relative evidence path. Missing or malformed engines fail visibly.
npx frootai capabilitiesnpx frootai capabilities --json
# Newly routed tested enginesnpx frootai config --helpnpx frootai docs listnpx frootai e2e listnpx frootai errors codes --jsonnpx frootai update --helpEnterprise release controls
Fail closed from command to registry
Enterprise eligibility is produced by executable evidence, not page copy. The private-plan release model uses immutable tags, explicit dispatch, an automation token, retained checksums, and post-publish integrity comparison. It does not claim unavailable protected environments or GitHub artifact attestations.
Explicit mutation approval
External writes fail with exit 77 unless the audited router receives explicit approval. Force requires separate approval.
One-time child authorization
Release scripts require a recent operation-bound token; only its SHA-256 hash is retained in the audit chain.
Exact artifact promotion
One tarball is packed, isolated, tested, checksummed, retained as release evidence, and published without rebuilding.
Explicit tag publication
Tag pushes build and retain evidence. npm publication requires an explicit immutable-tag dispatch, exact confirmation text, and the configured automation token.
Cross-platform certification
Packed binaries run across Linux, macOS, and Windows on Node 18, 20, and 22.
Fail-closed evidence
Security, integrity, dependency, capability, audit, and startup budgets must all pass before release eligibility is true.
Start safely
Install locally. Inspect evidence. Preview before ship.
# Per-project installnpm install --save-dev [email protected]
# Verify executable engines and catalognpx frootai versionnpx frootai capabilitiesnpx frootai factory status
# Preview every channel releaseFROOTAI_DRY_RUN=1 npx frootai ship all# Create one canonical primitivenpx fai scaffold agent
# Inspect and validatenpx fai primitives --type agentsnpx fai conformance .
# Inspect the Harvest enginenpx fai engine --helpMCP from the shell
Discover, trust, attach, test, invoke
The MCP command group operates the federation kernel. Use shell completion to keep names, trust tiers, and flags discoverable.
Open MCP Composefrootai mcp listfrootai mcp discover --tier first-party-msfrootai mcp trust listfrootai mcp attach azurefrootai mcp test azurefrootai mcp invoke azure.subscription_list
# Explore all eight current subcommandsfrootai mcp --helpOperating boundary
Powerful because it refuses ambiguity
Operator audience
Designed for FrootAI monorepo authors, primitive maintainers, and release operators.
Node.js 18+
Uses Node built-ins and spawned repository scripts.
Repository aware
Walks upward for a compatible FrootAI Factory workspace before repository commands run.
Preview first
`FROOTAI_DRY_RUN=1` keeps every ship command in preview mode.
Evidence derived
`frootai capabilities --json` loads real dispatchers and reports their exported contracts and source paths.
Registry gated
Publishing requires channel credentials and enforces version progression.