A curated directory of product CLIs, developer tools, and terminal apps — verified for humans, scripts, and AI agents.
>_$ gws
One command line for Gmail, Drive, Calendar, Sheets, Docs, Chat, Admin, and the rest of Google Workspace.
>_$ lark
The official Lark and Feishu CLI with commands for Messenger, Docs, Base, Sheets, Calendar, Mail, Tasks, and Meetings.
>_$ slack
Create, run, test, and deploy Slack apps from the terminal with the official developer CLI.
>_$ buku
A powerful bookmark manager with search, tags, import, and export.
>_$ m365
A Microsoft 365 community CLI for SharePoint, Teams, Entra, Power Platform, Outlook, and Microsoft Graph.
>_$ glow
Render and browse Markdown beautifully inside the terminal.
>_$ jira
A popular community-built interactive CLI for searching, creating, editing, and transitioning Jira issues.
>_$ ledger
A powerful double-entry accounting system for plain-text journals.
>_$ linear
A popular community CLI for browsing, creating, updating, and opening Linear issues from a repository.
>_$ newsboat
A terminal RSS and Atom feed reader with filters and podcast support.
>_$ notions
A community Notion API client and CLI for reading and writing pages and databases with structured output.
>_$ task
A flexible command-line task manager with filters, projects, and reports.
Common questions about CLI tools, Agent CLIs, and command line automation
A CLI, or command-line interface, lets you control software by typing commands in a terminal instead of clicking through a graphical interface. CLI tools are useful for development, automation, scripts, CI pipelines, and repeatable operations.
An Agent CLI is either a command-line tool for operating an AI agent or a conventional CLI designed to be called reliably by AI agents. Agent-friendly CLIs expose clear commands, non-interactive options, predictable output, and meaningful exit codes so an agent can plan, execute, and verify work.
Yes. AI coding agents can invoke many of these CLIs through a shell to work with repositories, cloud services, databases, productivity apps, and deployment systems. Tools marked Agent-ready are especially suitable for scripted or autonomous use, but authentication and permissions still need to be configured safely.
The best CLI tools for AI agents support non-interactive commands, stable flags, structured or parseable output, standard input and output, documented authentication, and reliable exit codes. These features make results easier for an agent to interpret and verify without manual intervention.
Choose an official CLI when you need first-party support, close alignment with a service API, and predictable updates. A community CLI can be a better fit when it offers a simpler workflow or capabilities the official tool lacks. Review its repository, maintenance activity, permissions, and installation instructions before use.
Use an OS keychain, environment variables, or a dedicated secret store instead of placing API keys in repositories, prompts, or shell history. Give people and AI agents least-privilege access, start in read-only or test environments, and confirm that automated commands support previews, explicit confirmation controls, and reliable exit codes.
