[on-hold] feat: recipes in interactive mode will ask for missing required credentials #3339
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change implements automatic secret discovery and interactive collection for recipe execution, addressing the core issue where users running recipes with missing credentials would encounter confusing extension failures. The implementation adds a SecretDiscovery engine that analyses recipe extensions to identify required credentials and a SecretCollector that presents user-friendly prompts to gather missing secrets. When users run recipes interactively, the system now automatically detects missing API keys or tokens, groups them by extension for better UX, and guides users through secure credential setup using the existing keyring infrastructure.
Note:
The secret collection flow is integrated into the session builder and only triggers in interactive mode, ensuring that automated workflows remain unaffected while dramatically improving the first-time user experience for recipe adoption.
This is a CLI-only change and does not affect the UI.