Before you start
The following requirements must be met to use the Wherobots CLI in an agentic terminal:Wherobots requirements
Wherobots requirements
- A Wherobots Account within a Community, Professional, or Enterprise Organization. See Create a Wherobots Account.
- While all Organization Editions can use the CLI, certain API features and job creation require a Professional or Enterprise Organization. See Organization Editions for details.
- A Wherobots API key. See API Keys.
Local requirements
Local requirements
- The Wherobots CLI installed and on your
PATH. See Install Wherobots CLI. - Your
WHEROBOTS_API_KEYenvironment variable set. See Configure authentication. - An agentic terminal such as OpenCode, Claude Code, Cursor, or another AI-powered coding tool with terminal access.
- Models such as Claude Opus, GPT Codex, or Gemini 3 Pro for the best results when using natural language commands.
Add agent skills
Agent skills give your agentic terminal domain-specific knowledge about Wherobots so it produces more accurate commands and better interprets results. Without skills, the agent relies only on CLI help text and its general training data. With skills installed, it has structured context about Wherobots workflows, APIs, and best practices — leading to fewer errors, less back-and-forth, and more reliable multi-step operations. Install all Wherobots skills:skills CLI, see the Skills documentation. To see available Wherobots skills, visit the wherobots/agent-skills repository.
Benefits
No syntax to memorize
No syntax to memorize
Describe what you want in plain language. The agentic terminal resolves the correct commands, subcommands, and flags for you.
Multi-step workflows in a single request
Multi-step workflows in a single request
Chain together operations like submitting a job, waiting for completion, and retrieving logs without writing a script.
Built-in error guidance
Built-in error guidance
When a command fails, the agent reads the error, suggests a fix, and can retry automatically.
Example tasks
Once the CLI is installed and your API key is set, just ask. Your agentic terminal translates natural language into the rightwherobots commands, picks the appropriate flags, and interprets the results.
Explore the API
| Terminal Prompt | What you can expect |
|---|---|
| List available CLI commands | Prints the full command tree so you can see every available endpoint. |
| Preview a job submission request | Previews the exact API request without executing it. |
Submit and monitor jobs
| Terminal Prompt | What you can expect |
|---|---|
| Submit a script as a job and stream the logs | Uploads the script, creates a run, and tails the output until completion. |
| Check the status of a recent job | Fetches the most recent run and reports its state. |
| Get resource metrics for a running job | Pulls live CPU and memory metrics for the specified run. |
Debug and triage
| Terminal Prompt | What you can expect |
|---|---|
| List recent failed jobs and summarize errors | Fetches recent failures, parses the structured output, and gives you a readable summary. |
| Retrieve logs from a failed run | Tails the logs for the most recent failure so you can jump straight to the error. |
Automate
| Terminal Prompt | What you can expect |
|---|---|
| List running jobs as JSON | Returns the running jobs in JSON format. |
| Cancel all running jobs in a specific region | Filters runs by region and status, then cancels each one. |
Next steps
Install Wherobots CLI
Install and configure the CLI for terminal-based Wherobots access.
MCP Server
Configure the Wherobots MCP Server for catalog exploration and spatial query generation.

