IonBin
All pages
Search

The practical field guide

CLI tools.

Give a tool a written command. Get a repeatable result.

Illustrative command · not executed
gh pr list --repo OWNER/REPO --state open --limit 5 --json number,title,url

Replace OWNER/REPO with a repository you can access. The result is JSON containing five or fewer open proposals.

Access & side effects

Makes authenticated GitHub API reads and prints repository metadata. It does not edit, comment on or merge a pull request.

How this interface works

A command-line interface, or CLI, is a way to operate software by typing commands in a terminal. It helps when a task needs to be precise, repeated or included in a script. Some CLIs also let an AI agent read and change a project.

19source-based reviews
14task categories
19evaluation records with limits

Reviewed

A ranked starting point

Start with your task.

How we choose and rank →
Source review

Numbers show our editorial starting order within this collection. Each review explains its place. This is not an adoption leaderboard, performance benchmark or security score. Examples are illustrative. Separate evaluation records show local runtime checks, hosted connection checks and any unavailable coverage.

01Code collaborationCLI

GitHub

GitHub CLI

Review pull requests, inspect checks and manage repository work from the same terminal as your code.

Quick look

Why it’s here

An editorial first stop: the task is clear, read-only examples are useful immediately, and authentication and command effects are documented. This is not an adoption or overall-quality ranking.

Useful for

  • Pull-request review queues
  • Release and workflow inspection
Before use

Installed gh and a terminal

Check: Credential storage fallback

Quick look

GitHub CLI

Local runtime checks

02Coding agentsCLI

Anthropic

Claude Code

Ask an agent to inspect a project, plan a change and work across files with explicit tool permissions.

Quick look

Why it’s here

An editorial starting point for supervised coding: natural-language tasks and documented permission modes make the workflow explainable. No model-performance comparison was run.

Useful for

  • Understanding unfamiliar repositories
  • Preparing scoped implementation plans
Before use

Installed Claude Code on a supported system

Check: Repository content can steer the agent

Quick look

Claude Code

Local runtime checks

03Coding agentsCLI

OpenAI

OpenAI Codex CLI

Inspect, change and test a local codebase with a coding agent whose filesystem access and approvals can be configured.

Quick look

Why it’s here

An editorial alternative for coding tasks with visible execution controls and a public CLI codebase. Position is not a measured comparison with other agents.

Useful for

  • Repository investigation
  • Scoped changes with validation
Before use

Installed Codex CLI

Check: Read access can disclose information

Quick look

OpenAI Codex CLI

Local runtime checks

04Coding agentsCLI

Google

Google Antigravity CLI

Work with Google's coding agents from the terminal, with project context, reviewable changes and configurable tools.

Quick look

Why it’s here

An editorial starting point for Google's current consumer coding-agent path. Documented migration and permission details support inclusion; no effectiveness or market-share ranking was measured.

Useful for

  • Google agent workflows
  • Reviewing project changes in a terminal
Before use

Antigravity CLI installed for the supported platform

Check: Migration carries access decisions

Quick look

Google Antigravity CLI

Local runtime checks

05Development environmentsCLI

Docker

Docker CLI

Build and inspect containers so an application and its dependencies can be run in a defined environment.

Quick look

Why it’s here

An editorial infrastructure starting point: the output is tangible and inspection commands are clear, but daemon and image permissions add setup decisions.

Useful for

  • Local application dependencies
  • Repeatable development environments
Before use

Docker CLI and access to a compatible running daemon

Check: Daemon access is powerful

Quick look

Docker CLI

Local runtime checks

06Cloud developmentCLI

Cloudflare

Cloudflare Wrangler

Develop and manage Cloudflare Workers and related resources with project configuration that can be reviewed in code.

Quick look

Why it’s here

An editorial entry for teams using Cloudflare: clear project configuration and account inspection support repeatability, while platform-specific setup limits general usefulness.

Useful for

  • Workers development
  • Reviewable Cloudflare configuration
Before use

Installed Wrangler and its supported Node.js runtime

Check: Environment names do not guarantee isolation

Quick look

Cloudflare Wrangler

Local runtime checks

07Development environmentsCLI

Astral

uv

Manage Python versions, project dependencies and isolated tools with a single command-line program.

Quick look

Why it’s here

An editorial starting point for Python work: requirements and dependency outputs are explicit. Its value is task-specific; no speed or compatibility benchmark was run.

Useful for

  • Python project setup
  • Dependency inspection
Before use

Installed uv

Check: A package manager installs code

Quick look

uv

Local runtime checks

08Payments developmentCLI

Stripe

Stripe CLI

Inspect Stripe API data and test webhook handling while keeping development activity separate from live payments.

Quick look

Why it’s here

An editorial specialist pick: it solves a concrete webhook-development problem with documented sandbox behavior. It is relevant primarily to Stripe integrations.

Useful for

  • Webhook development
  • Sandbox API inspection
Before use

Installed Stripe CLI

Check: Test and live modes must stay distinct

Quick look

Stripe CLI

Local runtime checks

09Cloud administrationCLI

Amazon Web Services

AWS CLI

Inspect and manage AWS services through explicit commands, account profiles and structured output.

Quick look

Why it’s here

An editorial cloud-administration pick with clear identity and output controls. Broad capabilities require more account and permission setup than the earlier general tools.

Useful for

  • AWS inventory and troubleshooting
  • Repeatable service operations
Before use

AWS CLI version 2 installed for the platform

Check: The wrong profile can target the wrong account

Quick look

AWS CLI

Local runtime checks

10Cloud administrationCLI

Google Cloud

Google Cloud CLI

Inspect Google Cloud projects and manage services with named configurations, explicit targets and structured output.

Quick look

Why it’s here

An editorial starting point for Google Cloud operations: explicit projects and structured output are useful, but service-specific setup and access controls require more preparation.

Useful for

  • Google Cloud inventory
  • Project and identity inspection
Before use

Installed Google Cloud CLI or an authorized Cloud Shell environment

Check: Authentication contexts can differ

Quick look

Google Cloud CLI

Local runtime checks

11Coding agentsCLI

Anomaly

OpenCode

Use a configurable terminal agent to explore code and prepare changes, with model choice and permission settings made explicit.

Quick look

Why it’s here

Adds a configurable terminal-agent option after the original ten entries, with model choice and explicit permission controls as its distinguishing workflow. The pinned v1 evaluation does not rank coding quality or cover v2. The original catalog order is preserved; this is an editorial position, not a measured adoption or security rank.

Useful for

  • Explaining an unfamiliar code path
  • Preparing a small change for human review
Before use

An installed OpenCode version matched to its documentation

Check: Project access becomes model context

Quick look

OpenCode

Local runtime checks

12JSON processingCLI

jq contributors

jq

Filter and reshape JSON in the terminal so API output becomes a small, readable answer or a predictable input for the next step.

Quick look

Why it’s here

Adds a broadly useful JSON transformation step that can turn other CLI outputs into a small, reviewable result. Placed before the more specialized additions for its simple local setup and clear input/output boundary. The original catalog order is preserved; this is an editorial position, not a measured adoption or security rank.

Useful for

  • Extracting a few fields from API responses
  • Checking JSON in scripts
Before use

A jq binary for the operating system

Check: Filter construction can change the program

Quick look

jq

Local runtime checks

13Repository searchCLI

Andrew Gallant and contributors

ripgrep

Search code and text from the terminal, with explicit control over ignored files, hidden files, regular expressions and output format.

Quick look

Why it’s here

Adds repository search alongside JSON processing: a practical way to locate evidence before an agent or developer edits code. Its inclusion rests on a distinct daily task, not a measured speed advantage. The original catalog order is preserved; this is an editorial position, not a measured adoption or security rank.

Useful for

  • Finding code references
  • Checking a renamed setting
Before use

An installed rg binary

Check: Excluded files create blind spots

Quick look

ripgrep

Local runtime checks

14Local data analysisCLI

DuckDB contributors

DuckDB CLI

Run SQL over local files and database tables without setting up a database server, then inspect or export the result.

Quick look

Why it’s here

Adds local SQL analysis for data tasks that need joins or aggregation. It follows the smaller text-processing tools because SQL, file access and extension controls add more setup decisions. The original catalog order is preserved; this is an editorial position, not a measured adoption or security rank.

Useful for

  • Summarizing CSV exports
  • Joining local analytical datasets
Before use

A DuckDB CLI build for your platform

Check: SQL can reach beyond a table

Quick look

DuckDB CLI

Local runtime checks

15Infrastructure planningCLI

HashiCorp, an IBM company

Terraform CLI

Describe infrastructure in configuration files, inspect a proposed plan and manage changes through providers and state.

Quick look

Why it’s here

Adds infrastructure planning and the review of state-dependent changes. It follows the local data tools because providers, backend access and sensitive artifacts require a more deliberate operating context. The original catalog order is preserved; this is an editorial position, not a measured adoption or security rank.

Useful for

  • Reviewing proposed infrastructure changes
  • Checking configuration in a repository
Before use

A Terraform binary matched to the configuration

Check: Plans and state can contain secrets

Quick look

Terraform CLI

Local runtime checks

16Kubernetes operationsCLI

Kubernetes contributors

kubectl

Inspect Kubernetes resources and prepare or apply manifests, with cluster context, namespace and permissions kept explicit.

Quick look

Why it’s here

Adds Kubernetes inspection and manifest preparation, a distinct workflow for readers who already operate clusters. Its placement reflects that specialized prerequisite and does not imply lower quality than general-purpose tools. The original catalog order is preserved; this is an editorial position, not a measured adoption or security rank.

Useful for

  • Inspecting workload state
  • Preparing Kubernetes manifests
Before use

A kubectl binary

Check: Kubeconfig is executable configuration

Quick look

kubectl

Local runtime checks

17CRM developmentCLI

Salesforce

Salesforce CLI

Create and manage Salesforce orgs, deploy metadata and run data commands from a terminal with the sf program.

Quick look

Why it’s here

The standard tool for scripted Salesforce work, with JSON output throughout. Ranked after general-purpose tools because it serves one platform.

Useful for

  • Deploying metadata from version control
  • Scratch org and sandbox management
Before use

Node.js for the npm install, or Salesforce's Windows or macOS installers

Check: Wrong org, real changes

Quick look

Salesforce CLI

Local runtime checks

18Databases and backendCLI

Neon

Neon CLI

Manage Neon Postgres projects, branches, roles and connections from a terminal, with JSON output for scripts and agents.

Quick look

Why it’s here

A capable first-party CLI with JSON output and branch-based workflows. Ranked after the Salesforce CLI because fewer small businesses run their own Postgres.

Useful for

  • Per-feature database branches
  • Schema diffs between branches
Before use

Node.js for npm i -g neon

Check: Deletes are real

Quick look

Neon CLI

Local runtime checks

19Knowledge and documentsCLI

Obsidian

Obsidian CLI

Search, read, create and append to notes in a local Obsidian vault from a terminal or script, through the running desktop app.

Quick look

Why it’s here

First-party CLI for Ion’s top-pick local notes app. Ranked after established developer CLIs because it needs a running desktop app and was not executed in this review.

Useful for

  • Appending to daily notes from scripts
  • Searching a vault with matching lines
Before use

Obsidian desktop app with the 1.12.7+ installer

Check: Wrong vault or file

Quick look

Obsidian CLI

Runtime unavailable

Keep the distinction clear

Looking for an AI connection?

MCP servers expose capabilities to a compatible AI host. Compare the connection and permission model before choosing.

Explore MCP servers →