@neottia/cli

@neottia/cli publishes the neottia command for initializing project configuration, compiling the SDLC lifecycle from that configuration, and installing it into the selected harnesses.

Install

pnpm add --global @neottia/cli

Workflow commands

neottia init [--harness claude-code|opencode|pi]... [--project DIR]
neottia apply [--harness ID]... [--scope project|global] [--project DIR]
neottia doctor [--project DIR] [--json]

init writes the minimal .neottia/config.yml for the selected harnesses. --harness is repeatable and accepts claude-code, opencode, and pi. When the file already exists and no --harness is given, init validates it and leaves every value untouched. See the configuration guide for the generated values.

apply validates the project configuration, compiles the seven lifecycle commands plus the shared operating-protocol skill for every configured harness (or the ones selected with repeatable --harness), resolves exact runtime package versions from the built-in compatibility catalog for the enabled modules, and installs everything in one run. Pi and OpenCode receive native package entries. Claude Code receives project .mcp.json entries that launch the generic MCP packages with exact versions through npx. No plan file is produced. Conflicting files (present but unowned, or modified after a previous install) are not overwritten: each one is reported as a WARN line with its path and reason, skipped, and everything else still installs. The command exits non-zero when files were skipped, prints a remediation summary, and never resolves package versions from a registry during planning.

doctor checks the Repository Store runtime, operating system, architecture, native addon, filesystem type and locality, atomic no-replace publication, hard links, stable identity, and durability barriers. It uses a private temporary area below the selected project and removes that area before it returns. Unsupported tuples fail before the probe creates files. The command also validates the module catalog and each installed harness lifecycle. Use --json for deterministic structured output that omits machine-specific paths.

Advanced manifest commands

neottia plan --manifest manifest.json --output install.plan.json
neottia apply --plan install.plan.json
neottia plan --action update --manifest manifest.json --output update.plan.json
neottia uninstall --receipt .neottia/install/default.receipt.json --output uninstall.plan.json
neottia doctor --manifest manifest.json
neottia recover --receipt .neottia/install/default.receipt.json

These commands drive the release pipeline, where a compiler-produced AssetManifest already exists. plan prints the complete plan and can save the same JSON. apply --plan accepts only a saved plan whose digest and checksums still match. If planning reports conflicts, approve each exact ID with a repeated --approve <id> option and generate the plan again. The CLI has no force option.

Paths

The CLI accepts --project, --home, --xdg-config, and --xdg-state on commands that inspect an installation. Defaults are resolved in the CLI before it calls the distribution library. Harness adapters receive no machine paths.

See the distribution guide for manifest production, ownership rules, configuration, and recovery.