latticeai

latticeai is the public launcher package for Lattice Core.

Use it in an existing repository to add modern agent instructions, verification, drift checks, and security scanning without changing your product architecture.

What Lattice Core adds

• AGENTS.md, docs/rules/codex.md, Cursor project rules, and Claude project settings
• verify, release-check, status, drift, diff, update, and doctor workflows
• security-scan for exposed-secret detection
• prompt recipes and optional CI scaffolding

Quick start

npx latticeai

For a non-interactive setup:

npx latticeai setup --projectType nextjs --preset startup

Core commands

• npx latticeai verify
• npx latticeai release-check
• npx latticeai security-scan
• npx latticeai status
• npx latticeai drift
• npx latticeai diff
• npx latticeai update
• npx latticeai doctor

Architect installs

Lattice Architect uses the same CLI package for project delivery:

npx latticeai create --id <project-id>

For an unlocked OpenClaw build, one command installs the compatible OpenClaw release, launches its official credential and channel setup, applies the generated Lattice configuration, and verifies gateway health:

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

Windows customers can download a double-click installer from their paid Lattice result instead. Model-provider and channel credentials are entered directly into OpenClaw; Lattice does not receive or store them.

For the runtime-neutral Agent Setup Builder, use:

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

The manifest selects OpenClaw or Hermes. Hermes also has an explicit alias:

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

The Hermes flow verifies the reviewed official installer hash and commit, installs the personalized local profile, backs up Lattice-managed targets, and runs Hermes checks. Provider and channel credentials stay in Hermes' official setup. Use --dry-run for a side-effect-free plan, --profile-name <name> for a same-name conflict, or --update-existing-profile only after reviewing the generated profile changes.

Generated launchers can use a short-lived --install-token instead of saving a Lattice CLI login. The token is never persisted or included in failure reports; only sanitized install stage metadata is returned to Lattice.

That flow is separate from Core setup. Core is for bringing agent guardrails and verification into repositories you already have.

Links

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