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

[FEATURE]: Reload auth.json if changed #4673

New Issue
Open
opened 2026-02-16 17:44:59 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:44:59 -05:00
Owner
Copy Link
Copy Source

Originally created by @hakan-77 on GitHub (Jan 10, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Why this matters

OpenCode currently does not support dynamic authentication token management. This is a must-have requirement for many enterprise environments. I understand that OpenCode has an Enterprise Edition (EE), but unfortunately that is not an option for some of our air-gapped project requirements.

Request

If the feature discussed in https://github.com/anomalyco/opencode/issues/1302
is not going to be implemented, it would be extremely helpful if OpenCode could at least detect runtime changes to auth.json.

This would be a relatively trivial change to implement, and I’m happy to submit a PR if this approach is aligned with OpenCode’s EE monetization strategy.

While this would not provide full enterprise-grade security (and therefore would not replace EE), it would offer a practical middle ground: programmatic updates to auth.json without requiring users to restart the TUI.

Originally created by @hakan-77 on GitHub (Jan 10, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request **Why this matters** OpenCode currently does not support dynamic authentication token management. This is a *must-have* requirement for many enterprise environments. I understand that OpenCode has an Enterprise Edition (EE), but unfortunately that is not an option for some of our air-gapped project requirements. **Request** If the feature discussed in https://github.com/anomalyco/opencode/issues/1302 is not going to be implemented, it would be extremely helpful if OpenCode could at least detect runtime changes to auth.json. This would be a relatively trivial change to implement, and I’m happy to submit a PR if this approach is aligned with OpenCode’s EE monetization strategy. While this would not provide full enterprise-grade security (and therefore would not replace EE), it would offer a practical middle ground: programmatic updates to auth.json without requiring users to restart the TUI.
yindo added the discussion label 2026-02-16 17:44:59 -05:00
yindo commented 2026-02-16 17:44:59 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 10, 2026):

This issue might be a duplicate of or closely related to existing issues. Please check:

  • #1302: Request to support Dynamic API keys through an apiKeyHelper - directly addresses dynamic token management without restart
  • #5748: Proposal: Provider Auth v2 - comprehensive proposal for encrypted credential vault with multi-account OAuth and same-request rotation
  • #4318: [FEATURE]: Allow storage of secrets in system credential store - related to secure credential management
  • #5391: [FEATURE]: multiple auth profiles per provider - related to managing multiple authentication configurations
  • #6815: [FEATURE]: Add command palette action to reload configuration without restart - similar need to reload config without restarting

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 10, 2026): This issue might be a duplicate of or closely related to existing issues. Please check: - #1302: Request to support Dynamic API keys through an apiKeyHelper - directly addresses dynamic token management without restart - #5748: Proposal: Provider Auth v2 - comprehensive proposal for encrypted credential vault with multi-account OAuth and same-request rotation - #4318: [FEATURE]: Allow storage of secrets in system credential store - related to secure credential management - #5391: [FEATURE]: multiple auth profiles per provider - related to managing multiple authentication configurations - #6815: [FEATURE]: Add command palette action to reload configuration without restart - similar need to reload config without restarting Feel free to ignore if none of these address your specific case.
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 discussion
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#4673
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?