anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 02:36:57 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Improve provider and API key update workflow after initial setup #1104

New Issue
Open
opened 2026-02-16 17:29:28 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 17:29:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @PeterDaveHello on GitHub (Aug 4, 2025).

Originally assigned to: @thdxr on GitHub.

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.

Originally created by @PeterDaveHello on GitHub (Aug 4, 2025). Originally assigned to: @thdxr on GitHub. 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](https://opencode.ai/docs/providers/), 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.
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@jayair commented on GitHub (Aug 8, 2025):

Any thoughts on where you'd want to see this info?

@jayair commented on GitHub (Aug 8, 2025): Any thoughts on where you'd want to see this info?
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@PeterDaveHello commented on GitHub (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 😄

@PeterDaveHello commented on GitHub (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 😄
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@thdxr commented on GitHub (Aug 11, 2025):

does opencode auth list help?

@thdxr commented on GitHub (Aug 11, 2025): does `opencode auth list` help?
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@PeterDaveHello commented on GitHub (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 auth namespace 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 like configure or set-key for these workflows.

Perhaps some small tweaks could help:

  • Adjust "manage credentials" to "manage providers and API keys" in the main help
  • Clarify the dual nature of login (both OAuth and API key workflows)
  • Consider aliases that better reflect the API key use case

Just thoughts on making this great functionality even more discoverable. Also happy to contribute if this direction makes sense!

@PeterDaveHello commented on GitHub (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 `auth` namespace 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 like `configure` or `set-key` for these workflows. Perhaps some small tweaks could help: - Adjust "manage credentials" to "manage providers and API keys" in the main help - Clarify the dual nature of `login` (both OAuth and API key workflows) - Consider aliases that better reflect the API key use case Just thoughts on making this great functionality even more discoverable. Also happy to contribute if this direction makes sense!
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@thdxr commented on GitHub (Aug 12, 2025):

yep makes sense! will think on this

@thdxr commented on GitHub (Aug 12, 2025): yep makes sense! will think on this
yindo commented 2026-02-16 17:29:28 -05:00
Author
Owner
Copy Link
Copy Source

@doanbactam commented on GitHub (Dec 22, 2025):

Bump

@doanbactam commented on GitHub (Dec 22, 2025): Bump
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1104
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?