Skip to main content
The DecimalAI CLI provides command-line access to your workspace.
This page covers the most-used commands. The CLI also ships an evaluators group, the full skills lifecycle (status, pull, install, benchmark, push), compat-check, and regression-check (the CI command — see Regression Check). Run decimalai --help or decimalai <group> --help for the complete list.

Command overview

skills export landed in 0.10.2 — write a skill in your workspace to disk without taking a fork — and skills install is deprecated in its favour. On 0.10.0 and earlier, skills install was the only way registry-skill files reached disk (or skills pull for a keyless, read-only copy). skills install still works and still forks first.

Installation

The CLI is included with the Python SDK:

Authentication

Every command that talks to your workspace accepts --api-key or the DECIMAL_API_KEY environment variable. skills scan (offline) and skills pull (public registry) need no key and take no --api-key:

Setup

decimalai init

Verify your API key, test connectivity, and send a test trace.
Output:

decimalai init <agent-name>

Added in SDK 0.11.0; --framework pydantic-ai in 0.12.0, --framework adk in 0.13.2.
Given the name of an agent you already created in the dashboard, writes a runnable agent.py wired to it — the agent name bound, its skills loaded at run time, a model on one editable line, and one example call.
Output:
The Set: list follows the model: --model anthropic:claude-… on langchain swaps in langchain-anthropic and ANTHROPIC_API_KEY; --framework pydantic-ai defaults the MODEL line to openai:gpt-4o-mini (Pydantic AI requires the provider prefix). The file is yours from the moment it lands — edit it, commit it, rename it. Nothing runs on DecimalAI’s side. The skills are fetched at run time, so changing what is attached in the dashboard changes what the file does without regenerating it. The agent must exist first. Create one at app.decimal.ai/agents/new; an unknown name exits with a suggestion rather than inventing an agent.
Only langchain, openai-agents, pydantic-ai and adk can be scaffolded. One adapter can deliver skills but has no template yet — anthropic (patches a single messages.create(), owns no tool loop) — and is refused with “can deliver skills, but there is no scaffold for it yet”: trace it with the snippet on your agent’s page. llamaindex, claude-agent-sdk, crewai, autogen and otel are refused with the reason: their adapters have no seam to insert a prompt, so a generated file would trace perfectly and deliver none of the agent’s skills — silently. A file that looks like it works but delivers nothing is worse than no file.

Support project with checks

Added in SDK 0.13.5; use 0.13.6 or newer for the corrected billing-review check and printed failure reasons. Requires the Support pack’s required starters, LangChain, and setup checks enabled on the platform.
Start from the Support pack, review the selected skills and create a draft-response agent. Have Python 3.10+, pip and a funded OpenAI API key ready. Use the name and DecimalAI key shown on your agent page.
The install line uses the official PyPI 0.13.6 wheel and verifies its SHA-256 hash. It remains usable while PyPI’s package index catches up with the release. Once the index lists 0.13.6, the equivalent requirement is "decimalai[langchain,evals]==0.13.6". The next steps save the installed versions and official SDK URL in requirements.lock.txt. In a fresh deployment environment, install that file with python -m pip install -r requirements.lock.txt and rerun the checks there. Keep credentials in environment variables; the dependency file contains no keys. Choose a new directory; --project refuses to overwrite an existing project. It writes agent.py, check_agent.py, checks.json, project.json, requirements.txt, .env.example, .gitignore and README.md. The default model is gpt-5.4-2026-03-05. A model judge also uses OpenAI; checks incur provider charges. The two sample tickets test a useful support draft and the boundary against claiming a refund or account deletion without tools. Checks run the same run() function and selected skills used by your service. A pass requires the matching traces to arrive with the expected delivered configuration. Open the printed trace link to inspect it. Independent trace scores, such as token efficiency, are separate from these checks. If trace confirmation is delayed, use python check_agent.py --resume. For a specific attempt, add --check-id <id>. This sends no new model requests. Keep the per-attempt check-results.<id>.json receipt; configuration edits make prior evidence stale and require another check. The generated agent drafts replies only and has no tools. Review replies before sending them to customers. Replace sample policies with your own, add representative checks and follow the generated README to deploy in your own environment. A passing sample check is not a general production certification or a five-minute guarantee.

Demo sandbox

One-command guided demos that seed realistic data into your workspace — see the headline workflows before instrumenting anything. All demo rows are prefixed [Demo] and removable with demo reset.

decimalai demo regression

Seed the “Your agent changed” demo: a v1→v2 agent (model swap, tool rename/removal, prompt rewrite) plus a trace corpus, then run the regression check and print a deep link to the impact report.
Output:
The manifest hashes differ per seed — yours won’t match anyone else’s.

decimalai demo skills

Seed the “Find skills that work” demo: three workspace-scoped skills with deliberately varied effectiveness, plus the stats recompute — so the registry ranks them by real (seeded) data. Visible only to your own workspace; nothing lands in the public registry.

decimalai demo reset

Remove all demo data for the workspace (both demos). Exact-prefix matched on [Demo] , so your own agents and skills are never touched.

Traces

decimalai traces list

List recent traces.

decimalai traces show

Show full detail for a specific trace as JSON.

decimalai traces stats

Show trace statistics for your workspace.

decimalai traces import

Import traces from a JSON or JSONL file.
A JSONL row has no place to name an agent unless you put one there, so the upload needs --agent-name (or an agent_name key on every line). The JSON format carries agent_name inside each trace object, so it does not.

Evaluations

decimalai eval push

Push evaluation scores to a trace.

Skills

decimalai skills list

List all skills in your workspace.

decimalai skills sync

Sync local SKILL.md files to the platform.
The skills directory is a positional argument (default ./skills). Since SDK 0.13.4 the bundle travels with the skill: text files one level under references/, scripts/, templates/ and assets/ beside each SKILL.md are sent as the item’s attachments and mirrored onto the new version (50 files, 500 KB each, text only).

Manifests

decimalai manifests list

List manifests for an agent.

Datasets

decimalai datasets list

List all datasets in the workspace with row counts and version info.

decimalai datasets show

Show version history for a specific dataset.

decimalai datasets pull

Pull a dataset version to a local file. The primary way to get training data onto disk.

decimalai datasets export

Export a dataset version to stdout (for piping) or a file.

decimalai datasets build

Build a new dataset version from traces.

decimalai datasets push-to-hub

Push a dataset to HuggingFace Hub, making it loadable by Axolotl, Unsloth, TRL, and any tool supporting load_dataset().
After pushing, use in training:
Requires pip install huggingface_hub datasets.

Replay

decimalai replay run

Execute a replay batch — re-run stale prompts through your updated agent.
Output:
The CLI exits with code 1 if any replays fail, making it suitable for CI/CD pipelines.

Global Options

All commands that talk to your workspace accept these options: The unauthenticated commands are the exception: skills scan runs entirely offline and takes none of the three, skills pull reads the public registry and takes only --base-url.

Environment Variables