Guides
Interactive prompts
Let clily ask for missing required values when the command is running in a TTY.
When required values are missing and a TTY is available, clily can prompt the user instead of failing immediately.
That makes it possible to keep strict validation while still supporting interactive workflows.
When prompts are a good fit
- local development commands
- setup or bootstrap flows
- tools used by humans in a terminal
When prompts are a bad fit
- CI pipelines
- non-interactive scripts
- machine-to-machine automation
Hook points
The hook surface includes onPromptSelect, which gives you visibility into which keys were missing before prompting begins.
That can be useful for analytics, custom logging, or adapting surrounding UI behavior.