On the command line: a census of 143 listings

There is no first-party Ada CLI; terminal access exists only by pointing Codex CLI or Gemini CLI at the MCP server to manage the agent.

Source retrieved 2026-10-03

The terminal is the only surface: a globally installed abg/agentbridge command with init, claude, codex, resume, pairs, doctor, budget, logs and kill subcommands.

Source retrieved 2026-10-03

A first-party terminal surface exists: nine agentskit subcommands for scaffolding, one-shot runs, interactive chat and environment diagnosis, plus an Ink terminal chat UI.

Source retrieved 2026-09-09

The `agno` command scaffolds a project, starts and stops it, connects clients and mints service-account tokens.

Source retrieved 2026-09-02

There is a first-party aident CLI that handles install, authentication and updates, and the docs state it exposes the same discovery and execution workflow as MCP.

Source retrieved 2026-10-03

The terminal is the primary and default surface: you launch aider with filenames and talk to it at its own prompt in the shell.

Source retrieved 2026-09-30

A terminal surface exists but not for agent building: the documented CLI belongs to the LLM Gateway developer tooling and covers managing applications, deploying models and monitoring usage.

Source retrieved 2026-09-03

There is no first-party command-line tool. Terminal use exists only because Claude Code can attach to the MCP server, so the CLI experience is another vendor's client speaking to Amplemarket.

Source retrieved 2026-09-10

The terminal is the whole product: a lightweight TUI installed as agy that carries the desktop agent's reasoning and multi-file editing into the shell.

Source retrieved 2026-09-10

There is no first-party CLI tool; terminal use is plain HTTP with cURL, which the vendor lists as a supported client for testing and debugging.

Source retrieved 2026-10-03

A published npm CLI runs counts, searches, exports, campaigns and the inbox from a terminal, and needs no install to try.

Source retrieved 2026-09-26

AudioCodes ships no CLI of its own; terminal use is indirect, by pointing the Claude Code command-line agent at the platform's MCP endpoint with API client credentials.

Source retrieved 2026-09-24

Auggie CLI installs from npm and runs interactively or headless.

Source retrieved 2026-09-02

A built-in Console UI streams a run to the terminal and UserProxyAgent can take console input, but there is no standalone agent CLI; the autogenstudio command only launches the web UI.

Source retrieved 2026-09-02

A published npm CLI drives calls, pathways, numbers, guard rails, evals and releases from a terminal.

Source retrieved 2026-09-11

The adk CLI scaffolds, runs, deploys and debugs agents, and pricing is identical whether you build through the CLI or the visual builder.

Source retrieved 2026-09-02

The comparison table claims terminal-UI support, but no CLI is documented in the API docs or on any product page.

Browse CLI fetches, searches, browses and manages sessions, contexts and Functions from the terminal.

Source retrieved 2026-09-02

A `cartesia` CLI creates, deploys and manages agents, and can chat with agent logic locally.

Source retrieved 2026-09-02

claude -p is documented as the SDK's CLI surface, with JSON and stream-JSON output for scripted callers.

Source retrieved 2026-09-02

The terminal CLI is the primary surface, installed by shell script, Homebrew, WinGet or Linux package managers.

Source retrieved 2026-09-02

A terminal client installed from npm gives both an interactive session and a headless mode triggered by piping, redirection or the JSON flag.

Source retrieved 2026-09-12

A terminal tool reviews local Git changes before commit and emits structured JSON for coding agents, though the CLI carries an Open Beta badge.

Source retrieved 2026-09-15

The terminal is the product's primary surface, installed via installer, npm or Homebrew.

Source retrieved 2026-09-02

A first-class terminal surface covers scaffolding, running, training, testing, replaying and deploying crews and flows, including login against enterprise SSO.

Source retrieved 2026-09-13

A terminal agent with interactive, plan, ask and print modes, sandbox controls and session resume.

Source retrieved 2026-09-02

The dg CLI covers transcription, synthesis, text analysis and account management; its own getting-started enumeration and command reference contain no voice-agent command, while the agentic-tools page claims the CLI reaches voice agents. Both statements are recorded in notes.

Source retrieved 2026-09-02

Devin CLI is a local terminal agent working on your own files, installed by curl script, Homebrew cask or Windows installer.

Source retrieved 2026-09-02

Devin Desktop installs a devin-desktop shell command for opening files, and its local agent shares the harness with Devin CLI, but the terminal agent is a separate product.

Source retrieved 2026-09-03

Official difyctl CLI runs workspace apps from a terminal with OAuth sign-in and JSON output.

Source retrieved 2026-09-02

A published npm CLI opens an interactive terminal chat with filesystem access, and takes single non-interactive messages that return JSON on stdout.

Source retrieved 2026-09-09

A standalone CLI authenticates by OAuth and pushes, pulls and diffs agent, tool and test configurations held as files in version control.

Source retrieved 2026-09-02

There is no first-party Elicit CLI product; the vendor publishes a CLI tool among its API integration examples, so terminal use means running that sample against the Pro-and-above API.

Source retrieved 2026-09-14

A published npm CLI covers the whole API with JSON output and exit codes built for agents, but it rides on API access, which the plan table grants only from Ultra upward.

Source retrieved 2026-10-03

The Droid CLI installs via curl, Homebrew, npm or PowerShell and runs in any repository.

Source retrieved 2026-09-02

A published CLI logs in with an API key and runs scrape, search and interact commands from the terminal, alongside agent skills.

Source retrieved 2026-09-24

A published npm CLI covers the whole REST surface from a terminal, authenticating with an API key, so scripts and shell pipelines are a first-class path.

Source retrieved 2026-09-14

Gemini CLI is included with both editions and shares its daily request quota with IDE agent mode; it is preinstalled in Cloud Shell.

Source retrieved 2026-09-02

Claw exposes a browser terminal on its cloud machine and GenTeam is joined by pasting a connect command into a terminal, but Genspark ships no command-line client that drives its agents.

Source retrieved 2026-09-15

Copilot CLI is included on every plan, including Free, and can commit locally or on GitHub and delegate to coding agents.

Source retrieved 2026-09-02

No Glean CLI of its own; a plug-in exposes Glean tools inside terminal coding agents such as Claude Code, Codex, Gemini CLI and OpenCode.

Source retrieved 2026-09-02

A terminal surface is first-class: an interactive run command with session save, resume and replay flags in the Python CLI, and an embedded launcher for Go binaries.

Source retrieved 2026-09-15

The CLI is a first-class surface with session, run, review, recipe, schedule, serve and terminal-integration commands, and shares provider and extension configuration with the desktop app.

Source retrieved 2026-09-16

A documented cli.py takes the query, report type and tone as arguments and writes the finished report to an outputs directory.

Source retrieved 2026-09-16

A first-party CLI runs agents, calls MCP tools, searches Company Brain and manages skills and artifacts from the terminal, and is included on both plans.

Source retrieved 2026-09-30

A Python CLI installs, initialises and health-checks Guard, and remains the documented alternative to the desktop app.

Source retrieved 2026-09-29

A headless command-line server is half of every download and runs on the machine holding the code; the same binary carries CLI subcommands for scaffolding, validating and linking extensions.

Source retrieved 2026-09-17

The terminal is the primary surface, installed by a shell command on Linux, macOS and Windows, with interactive sessions, slash commands and shell passthrough.

Source retrieved 2026-09-18

Standalone CLI installed from npm, with sandboxed auto mode.

Source retrieved 2026-09-02

Several terminal surfaces exist: the LangGraph CLI for local dev servers, a Sandbox CLI on every plan, a LangSmith CLI for issues, and the dcode terminal coding agent.

Source retrieved 2026-09-18

A first-class CLI ships with the Python package and manages the server, API keys, migrations and superusers, though it is unavailable in the desktop build.

Source retrieved 2026-09-25

langgraph-cli runs the Agent Server locally with langgraph dev, and builds, dockerises and deploys with build, dockerfile and deploy.

Source retrieved 2026-09-02

There is no Lead Scorer CLI of its own; terminal use means connecting the MCP server from Claude Code or Codex, for which the vendor publishes a plugin bundling the OAuth MCP and its skills.

Source retrieved 2026-09-18

The primary surface is a terminal harness installed from npm, with headless mode for automation.

Source retrieved 2026-09-02

The lk CLI creates projects, deploys agents and manages LiveKit Cloud; agents can also be run and talked to locally in console mode.

Source retrieved 2026-09-02

Skills and plugins install into terminal coding agents Claude Code and Codex; a Go CLI (llp) is a documented install path.

Source retrieved 2026-09-02

Through the desktop app the agent drives your machine's command line and the API exposes terminalExecute confirmations, but no Manus CLI client you type commands into is documented.

Source retrieved 2026-09-19

A Mastra CLI builds, starts and dev-serves the project (mastra build, mastra start, mastra dev).

Source retrieved 2026-09-02

A terminal surface exists only as developer tooling: the DevUI command line launches agents from a directory, and the Harness console apps are explicitly samples rather than shipped components.

Source retrieved 2026-09-19

The npm client ships CLI commands to sync types, list agents and run a workflow from a terminal; the agent SDK additionally installs a standalone mindstudio binary that runs any action or an MCP server.

Source retrieved 2026-09-02

The terminal is the primary surface: a native binary with a TUI, slash commands, live approvals and a command palette on macOS, Linux and Windows.

Source retrieved 2026-09-20

Two terminals: n8n CLI over the API from any machine (workflow, execution, credential, project, package, audit commands) and a Server CLI on the host for backups and licences.

Source retrieved 2026-09-02

The only terminal-run component is the local MCP server, installed and diagnosed with npx sub-commands; no CLI exists for building agents or dialling calls on its own.

Source retrieved 2026-09-09

run_demo_loop gives an interactive terminal chat session with streaming and retained history; it is a demo/testing loop, not a packaged CLI binary.

Source retrieved 2026-09-02

An official openai command-line tool exists for the API, but the documented CLI workflows stop at request/response calls; realtime sessions are driven from your own WebSocket, WebRTC or SIP code.

Source retrieved 2026-09-02

A global npm CLI plus a CLI-only installer give a full terminal surface, with subcommands for onboarding, gateway, agents, approvals, backup and MCP.

Source retrieved 2026-09-21

The terminal is the primary surface: a TUI by default, plus scriptable subcommands for one-shot runs and server mode.

Source retrieved 2026-09-21

A terminal CLI is included on every plan including the free local one, with headless and JSON output modes for scripting.

Source retrieved 2026-09-21

A first-party pplx binary runs web search and page-snippet extraction from a terminal and returns JSON for pipelines.

Source retrieved 2026-09-02

A published CLI drives the whole account from a terminal, creating agents, syncing knowledge bases and configuring deployments, and is built for a coding agent to run on your behalf.

Source retrieved 2026-09-09

The poly CLI pulls, branches, validates, pushes and chats against a project from the terminal.

Source retrieved 2026-09-02

The clai command ships with the package and runs an interactive terminal chat against any model, and any agent object can launch the same interface with Agent.to_cli_sync().

Source retrieved 2026-09-21

No first-party CLI of its own, but a published Claude Code plugin bundles the MCP server and skills so agents can be built and managed from a terminal.

Source retrieved 2026-09-22

A full Git command line is available through the workspace Shell, and terminal MCP clients can drive Agent, but there is no local Replit CLI.

Source retrieved 2026-09-22

Salesforce CLI drives the whole agent lifecycle from a terminal, but the Vibes coding agent itself is distributed only as a VS Code extension and a hosted IDE. There is no standalone Vibes CLI.

Source retrieved 2026-09-03

The documented default connection path is the Codex command-line client, with the graphical Codex app given as the alternative.

Source retrieved 2026-09-25

An install-less npm CLI audits any URL and analyses crawl logs with no account, and drives the REST API with a key once you have one.

Source retrieved 2026-10-03

A `sim` CLI runs workflows, queries tables and reads logs, with a JSON output mode for scripting.

Source retrieved 2026-09-03

There is no SkaleAgents CLI of its own, but terminal clients are documented: Claude Code and Codex are configured and re-authenticated with their own shell commands.

Source retrieved 2026-10-03

The published CLI installs and maintains the self-hosted platform on customer servers; it is an operations tool for on-prem deployments, not a way to drive an agent from a terminal.

Source retrieved 2026-09-09

A Tale CLI exists for deployment and configuration projects, and terminal agents can call the REST and MCP endpoints, but agent runs themselves are driven from the web app.

Source retrieved 2026-10-03

Two terminal surfaces exist: a full resource-level Telnyx CLI and an Agent CLI whose composite commands stand up an assistant on a phone number in one invocation.

Source retrieved 2026-09-09

A CLI ships alongside the SDKs and MCP endpoint and can start a run from a goal.

Source retrieved 2026-09-03

A dedicated CLI drives the low-code agent projects themselves, not just the Python path: it scaffolds, validates, packs, pushes back into the Agent Builder UI, deploys and runs them, and is separate from the coded-agent tool.

Source retrieved 2026-09-03

There is no Undermind CLI of its own; terminal use comes through agent CLIs such as Codex and Claude Code, which you configure with the MCP endpoint.

Source retrieved 2026-09-26

There is no Unify CLI of its own; terminal use happens only by installing the Unify plugin inside Claude Code.

Source retrieved 2026-09-27

The Vapi CLI covers assistants, numbers, calls, campaigns and logs from the terminal.

Source retrieved 2026-09-03

There is a real terminal surface: a vecbase CLI installed by a shell script, with subcommands for update, per-client setup and browser-based auth login.

Source retrieved 2026-09-27

A first-class `vellum` CLI sends messages, tails the event stream and manages processes, and is also how self-hosted runtimes are started and inspected.

Source retrieved 2026-09-27

There is no VeraDial CLI, but developer terminal clients can attach to the read-only MCP server after a manual one-time approval, which gives terminal access to account records only.

Source retrieved 2026-09-22

Claude Code and other MCP-compatible terminal agents can call the three tools; there is no Warmly CLI.

Source retrieved 2026-09-03

Two terminal surfaces: the Warp Terminal app for macOS, Linux and Windows, and a standalone agent CLI that runs in any terminal without the app.

Source retrieved 2026-09-03

There is no Webhound CLI; the terminal surface is borrowed from CLI agents such as Claude Code and Codex that call it over MCP.

Source retrieved 2026-09-27

The terminal is the only interface: you install globally with npm, run wtagent in a project directory and type tasks at a prompt.

Source retrieved 2026-09-21

A CLI is published alongside the language SDKs, and terminal agents such as Claude Code and Gemini CLI connect over Streamable HTTP MCP.

Source retrieved 2026-10-03

The zed CLI opens files and can be driven from scripts, but it launches the editor rather than running an agent headlessly; agent CLIs instead run as Terminal Threads inside Zed.

Source retrieved 2026-09-29

Terminal agents are supported as runtimes — its own Zen CLI plus Claude Code and Codex — but the docs frame them as hosted inside the editor rather than as a standalone Zencoder terminal product.

Source retrieved 2026-09-09

The terminal is the product: a single static binary dropped on your PATH gives an interactive TUI plus one-shot print and streaming invocations.

Source retrieved 2026-09-28