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

[FEATURE]: Notify users of available updates when auto-update is disabled #2997

New Issue
Closed
opened 2026-02-16 17:38:11 -05:00 by yindo · 8 comments
yindo commented 2026-02-16 17:38:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @Ravi-AIML on GitHub (Nov 20, 2025).

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

Problem

When autoupdate: false, users are never notified about new versions.

Proposed Solution

Show a toast notification when a new version is available (even if auto-update is disabled):

  • Message: "New version v{version} available. Run 'opencode upgrade' to update."

Benefit

Users with auto-update disabled can still be informed about updates and choose when to upgrade manually.

Originally created by @Ravi-AIML on GitHub (Nov 20, 2025). ### 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 ## Problem When `autoupdate: false`, users are never notified about new versions. ## Proposed Solution Show a toast notification when a new version is available (even if auto-update is disabled): - Message: "New version v{version} available. Run 'opencode upgrade' to update." ## Benefit Users with auto-update disabled can still be informed about updates and choose when to upgrade manually.
yindo added the help-wanteddiscussiongood first issue labels 2026-02-16 17:38:11 -05:00
yindo closed this issue 2026-02-16 17:38:11 -05:00
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 21, 2025):

Yeah that makes sense, also I think our toasts for updating aren't working for whatever reason

@rekram1-node commented on GitHub (Nov 21, 2025): Yeah that makes sense, also I think our toasts for updating aren't working for whatever reason
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 21, 2025):

Would accept PR here, it is easy to mock updates because you can just emit the mock update event to the bus and the tui and backend will both be aware of it

@rekram1-node commented on GitHub (Nov 21, 2025): Would accept PR here, it is easy to mock updates because you can just emit the mock update event to the bus and the tui and backend will both be aware of it
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@Raviguntakala commented on GitHub (Nov 22, 2025):

Yeah that makes sense, also I think our toasts for updating aren't working for whatever reason

I have fixed the toast message issue and raised PR #4625

@Raviguntakala commented on GitHub (Nov 22, 2025): > Yeah that makes sense, also I think our toasts for updating aren't working for whatever reason I have fixed the toast message issue and raised PR #4625
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@jdanbrown commented on GitHub (Nov 24, 2025):

✋ Actually, I find these toasts really annoying. I set "autoupdate": false and I personally don't want to see the Update available toast every time I start opencode (it's very distracting). I'd rather poll for updates myself, and manage them with my own process.

Also, I'd expect that IT teams managing opencode across a corporate fleet don't want this toast either, since they'll want to slow-roll their own update cadence, which means they'll always be some number of versions behind, by design (e.g. a common line of defense against supply-chain attacks). So their users would just see these toasts 100% of the time and not be able to do anything about them — lose-lose in that case.

If we do think these toasts are useful, maybe add another config flag so users can opt to disable them?

@jdanbrown commented on GitHub (Nov 24, 2025): ✋ Actually, I find these toasts really annoying. I set `"autoupdate": false` and I personally _don't_ want to see the `Update available` toast every time I start opencode (it's very distracting). I'd rather poll for updates myself, and manage them with my own process. Also, I'd expect that IT teams managing opencode across a corporate fleet don't want this toast either, since they'll want to slow-roll their own update cadence, which means they'll _always_ be some number of versions behind, by design (e.g. a common line of defense against supply-chain attacks). So their users would just see these toasts 100% of the time and not be able to do anything about them — lose-lose in that case. If we do think these toasts are useful, maybe add another config flag so users can opt to disable them?
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 24, 2025):

@jdanbrown how about I change it to "notify" where we keep the old behavior but people can opt into getting notified and not upgraded

@rekram1-node commented on GitHub (Nov 24, 2025): @jdanbrown how about I change it to `"notify"` where we keep the old behavior but people can opt into getting notified and not upgraded
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@jdanbrown commented on GitHub (Nov 24, 2025):

Do you mean like "autoupdate": true | false | "notify"? Yep, that would solve my use case.

@jdanbrown commented on GitHub (Nov 24, 2025): Do you mean like `"autoupdate": true | false | "notify"`? Yep, that would solve my use case.
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 24, 2025):

Yessir

@rekram1-node commented on GitHub (Nov 24, 2025): Yessir
yindo commented 2026-02-16 17:38:11 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 24, 2025):

@jdanbrown fixed in next release: https://github.com/sst/opencode/commit/a9a2c23736bafda2d316ce7d667772e3cbe36bd5

@rekram1-node commented on GitHub (Nov 24, 2025): @jdanbrown fixed in next release: https://github.com/sst/opencode/commit/a9a2c23736bafda2d316ce7d667772e3cbe36bd5
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 good first issue help-wanted
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#2997
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?