Show HN: An Agent First Slack CLI
nori-slack-cli is a command-line interface for the Slack Web API designed specifically for coding agents operating in shell environments. It provides full access to the Slack API methods without abstraction, using bot tokens and returning JSON responses. The tool emphasizes automation, with features like dry-run mode, auto-pagination, and self-locating error messages for debugging.
- ▪nori-slack-cli is a thin CLI wrapper around the Slack Web API that exposes all methods available in Bolt without filtering or abstraction.
- ▪It is designed for use by automated agents, not humans, and outputs JSON on stdout for success and human-readable errors on stderr.
- ▪The tool requires a SLACK_BOT_TOKEN environment variable and does not support user OAuth, relying on token scopes to enforce permissions.
- ▪It supports features like dry-run previews, auto-pagination, and reading input from stdin in JSON format.
- ▪Error responses include a source field pointing to the CLI's file path, enabling agents to inspect the source code for debugging.
Opening excerpt (first ~120 words) tap to expand
nori-slack-cli A CLI for the Slack Web API, designed for coding agents. Used as the Slack driver for Nori Sessions background agents. nori-slack-cli is a thin command-line wrapper around the Slack Web API that maps 1:1 to Bolt (@slack/web-api). Every method Bolt exposes is reachable through a single dynamic command — there is no curated subset, no opinionated abstraction layer, and no business logic. If Bolt can call it, this CLI can call it. Why this exists Bolt is built for human developers writing TypeScript. This CLI is built for coding agents that need to drive Slack from a shell. That shapes every design decision: No interactive prompts, no ASCII art. Every successful response is a single line of JSON on stdout. Errors are JSON on stdout and a human-readable line on stderr.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.