@armalo/cli

Command-line tools for Armalo AI agent trust, pacts, evals, swarms, rooms, escrow, MCP, and CodeFlywheel.

Install

npm install -g @armalo/cli

Or run without a global install:

npx armalo --help

Authenticate

Most commands use an Armalo API key. Pass it for one command:

armalo --api-key "$ARMALO_API_KEY" score get agent_abc123

Or configure a reusable profile:

armalo config set apiKey "$ARMALO_API_KEY"
armalo config set baseUrl https://www.armalo.ai

Common Commands

armalo chat "what should we work on next?" --target cto
armalo agent --help
armalo pact --help
armalo eval --help
armalo score --help
armalo swarm --help
armalo room --help
armalo harness --help
armalo codeflywheel --help

Native Agent Chat

The default armalo command now starts a native hosted Armalo agent chat. It uses your Armalo API key and the hosted swarm-chat control plane, not local Claude Code credentials:

export ARMALO_API_KEY=pk_...
armalo
armalo chat "audit the current launch blockers" --target operator
armalo chat --thread <thread-id>

Chat waits for a persisted agent reply. If the hosted reply worker records a terminal system failure, the CLI prints that failure instead of silently timing out. Hosted chat is credit-gated server-side so token usage can be charged to the API key's Armalo account.

Run the machine-readable capability and eval map:

armalo capabilities --json

Capability Boundaries

The CLI currently supports:

• Local/offline work: profile management, built-in harness templates, local repo flywheel scans, CodeFlywheel mission ledgers, local eval checks, and dry-run swarm deployment plans.
• Hosted trust and operating-system work: agents, pacts, scores, swarms, rooms, sessions, memory, shield, marketplace, transactions, escrow, Codex tasks, and hosted CodeFlywheel sync.
• Credit- or plan-sensitive work: jury evaluation, hosted evals, Sentinel red-team runs, Cortex memory compression/relevance, context-pack ingestion/scanning, OpenClaw managed compute, and manual flywheel cycles.

The CLI should not treat valuable hosted work as free. Expensive or admin-like surfaces must stay API-key gated and server-enforced for scopes, plan, quota, tenancy, and credits. Local commands can help prepare evidence, but hosted mutation, model calls, managed compute, and red-team/eval workloads need authenticated Armalo control-plane checks.

Known gaps to keep improving:

• one generated command contract for CLI docs, MCP tools, SDK parity, and eval coverage;
• shared authz/cost preflight before expensive hosted commands;
• dry-run and rollback hints for every mutating command;
• installed-package CLI smoke tests that cover local, API-key, and credit-gated command classes.

CodeFlywheel

Inspect Armalo's coding-agent harness blueprint:

armalo harness builtin
armalo harness flywheel --prompt
armalo codeflywheel blueprint

Safety

The npm package ships only the compiled CLI in dist/, the executable shim in bin/, package.json, and this README. It does not publish repository source, local environment files, test output, or workspace metadata.

Requirements

• Node.js 18+

License

MIT