Release: Slack CLI v4.14.0
You can now search and read the Slack developer docs without leaving the CLI, pass tokens on standard input, and more:
- We've updated the
slack docscommands so you can search and read the Slack developer docs without leaving the terminal:- We've added the
slack docs get <page>command, which prints a Slack developer docs page as markdown, returns it as JSON with--output=json, or opens it in a browser with the--output=browserflag. - We've updated the
slack docs searchcommand so that, when a coding agent runs it, text results link to the markdown version of each page. The agent can read the page without parsing HTML. - We've added the
--hide-pinnedflag to theslack docs searchcommand, which leaves out the pages docs.slack.dev pins to the top of some searches. - We've updated the help text for the
slack docscommand to lead with searching the docs, and theslack --helpoutput now shows aslack docs searchexample.
- We've added the
- We've updated how the CLI handles tokens:
- The
--tokenflag now reads the token from standard input when its value is-, which keeps tokens out of shell history and process listings. This works for both the global--tokenflag and theslack auth logincommand. - We've added the
SLACK_USER_TOKENenvironment variable for hook processes, alongside theSLACK_APP_TOKENandSLACK_BOT_TOKENvariables. It's set when you install an app that requests user scopes with theslack run,slack install, orslack deploycommand.
- The
- We've added the
--environmentflag to theslack initcommand to choose whether an existing app added during init is saved aslocalordeployed, matching theslack app linkcommand. - We've added the
features.app_home.agent_tasks_enabledmanifest property, so apps managed with the CLI can turn off the agent Tasks tab. - We've updated the confirmation prompts that
--forcealready skips to suggest the--forceflag when the CLI can't prompt in a non-interactive terminal. An explicit--force=falseflag now answers "no" to these prompts instead of prompting.