feat: Add settings UI for provider, model, and API key configuration#4
Open
vedworks wants to merge 3 commits into
Open
feat: Add settings UI for provider, model, and API key configuration#4vedworks wants to merge 3 commits into
vedworks wants to merge 3 commits into
Conversation
…uration, models, providers, and authentication.
…supporting API keys, OAuth, and device flow for various providers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Add a web-based settings interface that allows users to configure their Ironclaw API keys,
providers, and models directly in the workspace UI, eliminating the need to use the CLI ironclaw
configure command.
What's Changed
Features (MVP)
✅ API key authentication for 14+ providers (OpenAI, Anthropic, Google, xAI, OpenRouter, etc.)
✅ Token-based auth for Anthropic setup tokens
✅ Default model selection
✅ OAuth/device flow support (placeholders for future implementation)
✅ Secure credential handling (no API keys exposed in responses)
✅ Seamless integration with existing CLI configuration
Testing
Files Added
Files Modified
Notes