[mwbrooks]

Changelog

When a command that asks for a secret, such as slack env set, runs without an interactive terminal, the error now suggests running it in a terminal to enter the value with hidden input, before mentioning the flag.

Summary

This pull request changes the suggestion shown when a hidden input prompt can't be shown, for developers and the coding agents running commands for them. Before, the error said to re-run with the value as a flag (--value, --token), which leaves a secret in shell history. A coding agent reading that error would retry with the secret on the command line, and in its transcript.

Suggestion
   Run this command in an interactive terminal to enter the value with hidden input
   The `--value` flag also works, but can leave the value in shell history

The flag still works for scripts and CI. Every other prompt keeps the existing suggestion. This covers the three hidden input prompts: env set, auth revoke, and external-auth add-secret.

Testing

• Ran slack env set OPENAI_API_KEY < /dev/null in a Bolt project and confirmed the new suggestion above.
• Ran slack env set OPENAI_API_KEY in a terminal and confirmed the hidden prompt is unchanged.

Notes

• Follows fix(create-slack-app): ask developers to enter API keys in the CLI's hidden prompt slack-skills-plugin#223, the PR that has the create-slack-app skill hand env set to the developer rather than retry with --value.

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.