Developer Resources

A Package is a portable, signed bundle of AI objects (Agents, Teams, Workflows, Tools, Skills, Knowledge Bases, and voice and phone configuration) that installs into an Elizon Organization as one unit. You write it as plain files in a folder, check it with the Elizon CLI, and ship it as a single .pkg file.

npx @elizon/cli init

That one command is all the setup there is. The CLI runs through npx, with nothing to install globally and no account needed to start.

What's in this section

Elizon CLI

Prerequisites, running the CLI, connecting it to your Organization, and a reference page for every command.

Features & Specs

The Package model, the manifest field by field, Slots, triggers, signing, and what happens when a Package is installed.

Guides & Walkthroughs

From an empty folder to an installed Package, authoring with Claude Code or Codex, CI/CD, and walkthroughs of the three demo Packages.

The shape of the work

Author, offline

init scaffolds a project. You (or your coding agent) edit elizon.yaml and the component files, then run validate until it passes. None of this needs an account or a network connection.

Build, offline

build assembles an unsigned .pkg. Two builds of the same sources produce identical bytes.

Sign, against your Organization

target add connects the CLI to your Elizon Organization through a browser approval. sign then signs the artifact with your Organization's key, which never leaves your Organization.

Install, from Studio or the CLI

An operator installs the signed .pkg, either through the install wizard in Studio → Packages or with install. Either way they supply their own models, accounts and documents, because a Package never carries any.

Who does what

You are…	Start here
A developer building a Package	Your first Package
Using Claude Code, Codex or Cursor to build one	Author with a coding agent
An operator installing a Package someone sent you	Installing a Package
Automating builds and installs	CI/CD