CLI

CLI

The Intempt CLI turns a tracking plan into typed code. You describe your events once in intempt.yaml, generate a typed wrapper for your platform, and then check your codebase to see which events are actually called.

Published on npm as @intempt-technologies/cli.

Requirements

Install

npm install -g @intempt-technologies/cli

Quick start

intempt init        # detect the project, write intempt.yaml
intempt generate    # write typed wrappers from intempt.yaml
intempt status      # report which events are instrumented

intempt init detects your framework, language and package manager, then offers three paths:

If intempt.yaml already exists you get three different options instead: evaluate coverage, evolve the plan by adding events, or start fresh.

Credentials

Most of the CLI needs no account. generate, validate, add, remove and status all work offline against your local intempt.yaml.

Two things do need credentials: the AI scan path in init, and any command that talks to the platform API (content generate-* and the registry commands).

Pass a key per command:

intempt content generate-email "spring sale" --api-key YOUR_KEY

Or set it once in your environment:

export INTEMPT_API_KEY=YOUR_KEY

Resolution order is flag, then INTEMPT_API_KEY, then any locally stored credentials.

Org and project

Commands that reach the API need an org and a project. Set the default once:

intempt use --org your-org --project your-project

Omit both flags for an interactive picker. Per-command --org and --project flags override the stored default.

intempt use stores the default against your signed-in account, so it reports "not logged in" if you are working from an API key alone. That is expected. Set the two environment variables directly instead, which every command reads:

export INTEMPT_ORG=your-org
export INTEMPT_PROJECT=your-project

Where to go next