Repository navigation
Improve provider and API key update workflow after initial setup #1597
Description
After the initial provider and API key setup guided by the application, updating or reconfiguring provider credentials later is not straightforward unless users have already read the documentation or have been shown how to do it. There is no clear indication or workflow in the CLI or TUI for changing providers or API keys after the initial configuration, and the interface does not make these options discoverable. This core workflow is only described in external documentation, such as Providers Documentation, and is not accessible from within the app itself.
Suggestions:
- Provide a clear and accessible way to update or reconfigure provider and API key settings directly from both CLI and TUI, without requiring users to search external documentation or fully reinitialize the application.
- Consider adding dedicated commands, menu options, or prompts that guide users through updating provider credentials or API keys from within the application interface.
- Clearly document this workflow in-app so instructions are easily found when switching providers or refreshing API keys.
Addressing this would make the experience smoother and more intuitive for users who need to manage multiple LLM providers or rotate credentials. I believe improvements in this area would benefit both new and experienced users.
Looking forward to feedback and suggestions from the community and maintainers on potential approaches.
Activity
jayair commentedon Aug 8, 2025
Any thoughts on where you'd want to see this info?
PeterDaveHello commentedon Aug 11, 2025
Putting it in the help info will should be good enough, and I can send a pull request for it if it's something acceptable 😄
thdxr commentedon Aug 12, 2025
does
opencode auth listhelp?PeterDaveHello commentedon Aug 12, 2025
@thdxr Thanks for pointing out
opencode auth! The functionality is definitely there.I think the discoverability challenge might be semantic. For multi-provider platforms like opencode, when looking to add or switch providers, the
authnamespace might not be the first place to check, even though it handles exactly that.Additionally,
login [url]might not immediately suggest API key configuration to users familiar with direct key-setting workflows. Many AI tools use "provider" terminology and more explicit commands likeconfigureorset-keyfor these workflows.Perhaps some small tweaks could help:
login(both OAuth and API key workflows)Just thoughts on making this great functionality even more discoverable. Also happy to contribute if this direction makes sense!
thdxr commentedon Aug 12, 2025
yep makes sense! will think on this
doanbactam commentedon Dec 22, 2025
Bump
arniigreat1 commentedon Feb 17, 2026
bump, seems more complicated than should
github-actions commentedon Apr 19, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.