@latticeai/cli

@latticeai/cli is the underlying CLI for both Lattice Core and Lattice Architect installs.

It powers:

• Core setup for existing repositories
• agent instruction generation for Codex, Cursor, and Claude Code
• verification, drift detection, release checks, and security scanning
• Architect project installs with create --id
• OpenClaw runtime and generated-workspace installs with openclaw install --id
• runtime-neutral agent setup installs with agent install --id
• reviewed Hermes releases and personalized profile distributions with hermes install --id

Install

npm install -g @latticeai/cli

Or use the public launcher:

npx latticeai

Core workflow

latticeai setup --projectType nextjs --preset startup
latticeai verify
latticeai security-scan
latticeai update

Architect workflow

latticeai create --id <project-id>

OpenClaw workflow

npx --yes latticeai@latest openclaw install --id <project-id>

The guided installer requires Node.js 22.19 or newer. It opens official OpenClaw onboarding for credentials and channel authorization, keeps the gateway bound to loopback by default, backs up managed files, validates the generated patch, and rolls Lattice-owned changes back if verification fails.

Agent Setup workflow

Let the paid project select its runtime automatically:

npx --yes latticeai@latest agent install --id <project-id>

The existing OpenClaw command remains supported. Hermes projects can also use the explicit alias:

npx --yes latticeai@latest hermes install --id <project-id>

For Hermes, Lattice downloads the official installer, verifies the reviewed script's SHA-256, pins the reviewed upstream commit, installs a persistent local profile distribution, applies any approved user and memory seed files, and runs Hermes configuration, doctor, and profile checks. Provider and channel credentials are entered only in the official Hermes setup flow; they are not accepted in the Lattice manifest, command, logs, or receipt.

Useful recovery and preview options:

# Show the complete local plan without downloading, running, or writing anything
latticeai hermes install --id <project-id> --dry-run

# Keep setup for later; the receipt prints an exact resume command
latticeai hermes install --id <project-id> --skip-setup --skip-model-check --skip-gateway-setup

# Resolve a same-name profile without overwriting it
latticeai hermes install --id <project-id> --profile-name <alternate-name>

# After reviewing the generated files, explicitly update a same-name profile
latticeai hermes install --id <project-id> --update-existing-profile

Receipts and backups are stored under ~/.lattice/agent-setups/<project-id>/. Lattice rolls back only the files it owns; it does not uninstall Hermes or delete credentials, sessions, learned memory, gateway state, or user-created skills. Hermes Agent is an independent open-source project from Nous Research. Lattice is not affiliated with or endorsed by Nous Research.

Lattice's generated launcher may use --install-token <short-lived-token> instead of a saved CLI login. The token is project-scoped, is never written to credentials or failure reports, and is used only to fetch that install manifest and send back a sanitized status receipt. Receipts contain stage/runtime/release metadata and file counts—not generated content, credentials, command output, errors, local paths, or the token.

Links

• Docs: https://latticeai.app/core
• Source: https://github.com/rmach816/lattice