Prerequisites

To author and build a Package

• Node.js 22 or later, which includes npm and npx. Check with:

  node --version

• Access to the npm registry the first time you run a given CLI version, so npx can fetch it. If your network only reaches an internal npm mirror (Verdaccio, Artifactory, Nexus and similar), the mirror needs to carry the @elizon/cli package and the @elizon/cli-* platform packages.

• A supported machine:

  Operating system	Architectures
  macOS	Apple silicon (arm64), Intel (x64)
  Linux	x64, arm64, on glibc or musl (Alpine) distributions
  Windows	x64, arm64

That's all. Authoring (init, schema, validate) and building (build) need no Elizon account, no login and no network connection once the CLI has been fetched.

To sign, install or list Packages

The commands that act on an Organization (sign, install, packages ls, packages bind, target key) also need:

• An Elizon Organization you can sign in to in a browser, reachable from the machine running the CLI. This is the address your team uses for Elizon, whether it's hosted by Elizon or self-hosted.

• A role that allows it:

  Command	Permission needed	Built-in roles that have it
  sign, install, packages bind	package.install	Owner, Admin, Editor
  packages ls	package.view	Owner, Admin, Editor, Normal

  Custom roles can grant or withhold these. See Members and roles.

• A connected device. You connect the CLI once per machine with target add.

A coding agent (optional)

The CLI is built to be driven by a coding agent as well as by hand. init sets up instructions for Claude Code, Codex and Cursor, plus an AGENTS.md any other agent can read. See Author with a coding agent.