For the complete documentation index, see llms.txt. This page is also available as Markdown.

DinoAI CLI

Use the Paradime CLI to interact with DinoAI programmable agents from your terminal. Start interactive chats, send one-shot prompts, resume sessions, and stream agent responses in real time.

  • This feature is available with the Paradime DinoAI plan.

  • Your API keys must have DinoAI Agent capabilities.

  • Programmable agents are defined as YAML files under .dinoai/agents/<name>.yml in your workspace repository.

Talk to a DinoAI Agent

Using the Paradime CLI, you can talk to a DinoAI programmable agent directly from your terminal.

The paradime dinoai command supports two modes:

  • Interactive — drop into a chat-style REPL and have a multi-turn conversation with the agent.

  • One-shot — pass --message (or pipe a message via stdin), wait for the response, and exit.

In both modes, agent messages are streamed to the terminal as they arrive, rendered as markdown.

CLI command

paradime dinoai

Options

Flag
Short
Type
Description

--agent

-a

Optional, TEXT

Named agent under .dinoai/agents/<name>.yml. Omit to use an ad-hoc agent.

--message

-m

Optional, TEXT

Opening message. When provided, runs a single turn and exits (no interactive prompt).

--session

-s

Optional, TEXT

Resume an existing session by ID. The full conversation history is replayed first.

--help

Show CLI command options and exit.

Session lifetime: A DinoAI session pod stays alive for 24 hours after its last activity. Use --session <id> to rejoin within that window — the agent retains full conversation context.

Examples

Open an interactive prompt against a named agent. Each turn is sent to the agent and the streamed response is rendered in your terminal. Press Ctrl-C or submit an empty line to exit.

CLI command

Example output

Aborting and rejoining a run

If a run is taking too long, you can press Ctrl-C at any point. This aborts only the local view — the agent run continues server-side. The CLI prints the session ID and the command needed to rejoin:

You can then re-attach later (within the 24-hour session window) and resume streaming as soon as the agent emits new messages.

Spinner status meanings

While a run is in flight, the CLI shows a single-line spinner labelled with the current run status and elapsed time:

The status field can be one of:

Status
Meaning

QUEUED

The run has been accepted by the backend and is waiting for an agent pod.

RUNNING

The agent is actively processing your message.

WAITING

The previous turn already returned COMPLETED; the backend is still transitioning the run state for your follow-up message.

COMPLETED

Terminal — the agent finished and produced a response.

FAILED

Terminal — the run did not complete successfully. The CLI prints the last error message.

Last updated

Was this helpful?