CLI

The norien command — for humans and CI. Every command speaks --json; stdout stays pure so it composes with jq.

Install the CLI with curl -fsSL https://norien.live/install.sh | sh or npm i -g @norien-live/cli. It targets api.norien.live by default; point it elsewhere with --registry or a profile.

Common commands

$ norien init my-agent$ norien search trading$ norien info trading-agent$ norien install trading-agent$ norien run trading-agent$ norien logs trading-agent -f$ norien chat trading-agent$ norien skill run market-recap$ norien doctor

Start a new agent

norien init scaffolds a runnable agent in one step — a valid agent.json, a zero-dependency entrypoint that already serves /health, a README, and .env.example. It publishes as-is and runs as-is; pick node or python.

norien init my-agent --runtime node -y
cd my-agent
norien publish --dry-run     # validate against the registry
norien publish               # after: norien login

Chat

norien chat opens a live conversation in your terminal, replies streaming in as they form. Pass an agent slug to talk to that agent in character — a preview, so its code never runs — or omit it to ask the Norien assistant about the product. Use -m for a single, pipe-friendly reply. See Chat with an agent for the full feature.

Skills

norien skill run <slug> runs a published skill and streams a result grounded in Norien's live data. norien skill search lists them and norien skill publish ships your own from a skill.json. See Skills.

norien chat                  # ask the Norien assistant anything
norien chat trading-agent    # chat with an agent, in character
norien chat -m "hi"          # one-shot reply, no prompt

Composability

Every command accepts --json, and stdout is pure JSON while spinners and diagnostics go to stderr — so the CLI drops straight into pipelines and CI without special-casing.

norien search trading --json | jq '.[0].slug'

Exit codes

0 success · 1 error · 2 bad usage · 3 not authenticated · 4 not found · 5 validation or dependency failure. Stable, so scripts can branch on them.

Authentication

Reads need no credential. To publish, create a key on the API Keys page and run norien login; profiles live in ~/.norien/config.json.

Note —norien doctor checks the API, your manifest, dependencies, installed runtimes, and configuration, and tells you which one is wrong. See Running agents for the runtime commands.