Open an issue on GitHub with what you ran and what happened. This is the preferred way to get help, and others can find the answer later. Search existing issues first.
If you don't have a GitHub account, email allen@unrulysystems.com instead. We answer issues and email within two business days. Report security problems privately, as described in the security policy.
Issues are public. Never post or send your Slack token or the contents of
~/.config/slack-cli/credentials.json. The CLI never prints tokens, so its
output and error messages are safe to share.
The CLI is running on a different machine from your browser, for example over SSH. Run
slack login --paste, approve in the browser, and paste the code the page shows
into the terminal.
Another slack login may still be waiting; stop it and try again, or use
slack login --paste, which does not listen on a port.
missing_scope
Run slack login --write to grant write access. The error names the command to
run when login can grant the scope.
Some workspaces restrict third-party apps; ask a workspace admin to approve it. You can also
create your own Slack app from the project's
app manifest
and set SLACK_CLIENT_ID to its client id.
Each slack login adds a workspace. slack workspaces list shows
them (never the tokens), and slack workspaces use T0123456789 switches the
current one.
slack auth revoke invalidates the token at Slack, slack logout
removes it from your computer, and a workspace admin can remove the app in the workspace's
app settings.