You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature] adding interactive CLI for first time users and easy setup #10
The current CLI requires users to manually provide the names/identifiers of different options during setup, such as the AI agent provider they want to use.
This can make the setup process less intuitive for new users because they first need to know the exact names or available values supported by the application.
For example, instead of being guided through the available AI providers, a user may have to enter something like:
provider=openai
However, a new user may not know which providers are supported or what the expected provider name is.
Proposed Solution
Add an interactive CLI setup mode using a keyboard-navigable selection prompt.
For options with a predefined set of choices, the CLI could display something similar to:
◇ Select an AI provider:
│
│ ○ OpenAI
│ ○ Anthropic
│ ● Google Gemini
│ ○ Groq
│ ○ Other
│
└ Use ↑/↓ to navigate and Enter to select
Users could navigate through the options using the arrow keys and select an option with Enter, similar to the setup experience provided by tools such as Vite.
The interactive mode could be particularly useful for:
AI provider selection
Model selection
Authentication method
Configuration options
Feature toggles
Other inputs where the available choices are known beforehand
Backward Compatibility
The existing CLI arguments should remain available for users who prefer scripting, automation, or non-interactive usage.
For example:
how setup --provider openai
could continue to work, while:
how setup
could launch the interactive setup flow.
Benefits
Makes the initial setup easier for new users.
Removes the need to remember exact provider/option names.
Clearly communicates which options are supported.
Reduces invalid input and configuration errors.
Makes the CLI feel more approachable without sacrificing its scriptability.
This could significantly improve the first-time user experience while keeping the existing CLI interface intact.
Sure @LazyKaddu , go on.
Primarily, the project was intended for comfortable-with-cli peeps but the project's been getting consistent traffic since quite some time. So yeah, it'd be a good addition. I've assigned it to you, so you should be good to go.
One thing, please do write corresponding tests as well.
Activity
LazyKaddu commentedon Oct 4, 2026
Hi @FireHead90544
I would love to work on this feature integration
FireHead90544 commentedon Oct 4, 2026
Sure @LazyKaddu , go on.
Primarily, the project was intended for comfortable-with-cli peeps but the project's been getting consistent traffic since quite some time. So yeah, it'd be a good addition. I've assigned it to you, so you should be good to go.
One thing, please do write corresponding tests as well.
LazyKaddu commentedon Oct 5, 2026
@FireHead90544 i have created a pull request #11 for the implemented feature with test created for new integration and all test passed.