Commands and limits

Use the installed protocol-1 CLI as the contract for every Dino operation.

Session preflight

dino version check
dino capabilities
dino workspace list
dino workspace current
dino workspace check
dino account get

If the stable-channel check has a retryable network failure, continue only with capability preflight. Do not infer that an update exists.

Mutation approval

Every operation with readOnly: false requires approval for one exact invocation.

[1] Read current state
        │
        ▼
[2] Show workspace, target, arguments, and effect
        │
        ▼
[3] Obtain explicit approval
        │
        ▼
[4] Add --confirm-mutation <operation> and invoke once

Changed arguments, targets, workspaces, or retries require new approval.

Prompt your AI agent

Recommended

Use the applicable Dino skill for this request: <request>.
Preflight the CLI, workspace, account role, and intended capability.
Use read-only operations to establish the exact current state.
Before each change, show the target, material inputs, side effect, and approval operation.
Wait for explicit approval for one invocation.
Never replace a missing CLI capability with direct HTTP.

Use the Dino CLI directly

dino capabilities
dino <group> <command> --help

Use the JSON default. Do not pass --format.

Roles

Action	Typical role
Create and manage an owned agent	Client or Account Manager, within ownership scope
Place an owner-scoped preview	Client
Create Batch, Drip, or Inbound	Pong Client for self; Account Manager or Ops Admin for an authorized target
Insert Drip contacts or reconcile callbacks	Exact process owner
Assign or clone Experience	Account Manager

Selected limits

Input	Limit
Hard call duration	90–900 seconds
Lens link lifetime at process creation	30–180 days
Batch or Drip process limit	1–255 and within available DID capacity
Bulk Drip insertion	1–500 contacts
Failed-callback acknowledgement	1–100 failure IDs
Agent description	240 characters

Common failures

Result	Response
401	Repair the selected workspace credential without printing it.
403	Stop. The authenticated role lacks the required authority.
404	Treat the resource as missing or outside actor scope.
409	Inspect lifecycle, duplicate-ID, or active-session conflict details.
Validation failure	Fix source and validate again. Do not publish.
Retryable publish failure	Reuse only the original idempotency key.

Gotchas

• A configured directory is not a registered workspace.
• Never use repeated one-command overrides as persistent workspace setup.
• Never scrape human text from a JSON operation result.
• Never guess a flag. Use the installed command help.
• Never place API keys, provider keys, or callback secrets in chat.