decimalai command gives you the platform from a terminal. decimalai --help and decimalai <group> --help print what your installed version takes.
Command overview
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, skills verify and skills remove (offline), skills search and skills pull (public registry), and starter support (public project download) need no DecimalAI key and take no --api-key. skills add, install, update, status --remote and migrate take one, and without it work anonymously, with public skills only:
Setup
decimalai starter support
Download a new local Support project without saving an agent into a workspace. The browser builder downloads the same project without installing the SDK.
The project requires Python 3.10+ and your OpenAI API access, uses no pip dependencies, and sends no DecimalAI telemetry. It delivers all the selected skills’ instruction text; it doesn’t use the connected SDK router or execute companion scripts.
--checks makes two sample-task calls and two judge calls using your provider key. See Skill packs for the hosted trial and connected trace paths.
decimalai init
Verify your API key, test connectivity, and send a test trace. It then prints the next commands to try and links to the dashboard and the docs.
With no key it exits 1, since this command checks a key. Skills need neither a key nor an account, so it starts you there:
decimalai init <agent-name>
Given the name of an agent that already exists, 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.
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).
decimalai[adk] and decimalai[pydantic-ai] need Python 3.11+. On 3.10, pip installs an older decimalai release for those extras without saying so, so --framework adk and --framework pydantic-ai print a ! line under the install line.
The agent’s name is written once, as AGENT_NAME = "refund-bot" near the top, and every template passes it to agent_config(AGENT_NAME), which files each run’s trace under it. To point the file at another agent, change that one line.
Every --framework file also runs without DECIMAL_API_KEY: agent_config() then runs keyless. Generated with --base-url, a file sets DECIMAL_BASE_URL before it imports decimalai.
The file is yours, and nothing runs on DecimalAI’s side. Skills are fetched at run time, so changing what is attached in the dashboard changes what the file does. Its header lists the skills attached to the agent, and says that it is also offered every skill its workspace owns, unless that skill’s Offered to setting is Only agents it’s assigned to.
The agent must exist first: create one at app.decimal.ai/agents/new or with decimalai agents create. An unknown name exits with a suggestion.
decimalai agents create
Creates an agent from a terminal, the same call as the dashboard’s create form. The agent exists as soon as the command returns, with no code deployed yet; decimalai init <agent-name> then writes a runnable file for it.
Skill names resolve exactly, never to the nearest search hit, and an unknown one stops the command before anything is created. A skill the server refuses to attach (a plan limit, say) is listed in the output with the reason, and the agent is still created. A pack starter skill that is unavailable right now is listed with a warning and left off. An existing agent name is refused.
decimalai agents apply-pack
Applies a role pack to an agent that already exists, the same change as Start from a pack on the agent’s Prompt & skills page. The pack’s starter prompt becomes the agent’s next prompt version, and its starter skills are added; skills already on the agent stay. It is one setup version on the agent’s Versions page. Your code doesn’t change: agent_config() reads the new prompt and skills on its next run.
- The new prompt version is labelled Applied the Support pack. Fill in its
<blanks>on Prompt & skills; that saves the next version. - Applying the same pack again changes nothing and says Nothing to apply.
- A pinned agent keeps its pin. The starter is saved as a new version but not served, and the command says so.
- A skill DecimalAI refuses (blocked, or past your plan’s skill limit) is left out and named; the rest applies.
- An agent that doesn’t exist is refused, with the
agents create --packcommand to make it instead. An unknown--skillname stops the command before anything changes.
Support project with checks
Requires the Support pack’s required starters, LangChain, and setup checks enabled on the platform.
--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, so checks incur provider charges. In a fresh deployment environment, install requirements.lock.txt and rerun the checks there.
A pass requires the matching traces to arrive with the expected delivered configuration. The Support starter project says what a pass does and doesn’t mean.
If trace confirmation is delayed, use python check_agent.py --resume, with --check-id <id> for a specific attempt. 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, so review replies before sending them. Replace the sample policies with your own, and follow the generated README to deploy.
Demo sandbox
One-command guided demos that seed realistic data into your workspace, so you can see the headline workflows before instrumenting anything. Demo names start with[Demo] , and demo reset removes them.
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.
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 seeded data. Nothing lands in the public registry.
decimalai demo reset
Remove all demo data for the workspace (both demos). It matches the demos’ exact names, so an agent or skill of yours whose name merely starts with [Demo] is left alone.
Global options
All commands that talk to your workspace accept these options:
The exceptions are in Authentication: of those,
skills pull and starter support still accept --base-url. The skills-on-disk commands also take --directory DIR, the project root.