opencode upgrade doesnt move to newest version #5375

Activity

1. OpeOginni

   added

   bugSomething isn't workingSomething isn't working

   on Dec 11, 2025
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Dec 11, 2025
3. github-actions commented on Dec 11, 2025

   

   github-actionsBot

   on Dec 11, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • It should not be possible to exit opencode while it's silently updating itself to latest release #5111: It should not be possible to exit opencode while it's silently updating itself to latest release
   • [FEATURE]: More transparent automatic version upgrades #4248: [FEATURE]: More transparent automatic version upgrades
   • Please, change autoupdate to notify by default #4783: Please, change autoupdate to notify by default
   • "Restart to update" always pops up, even after restarting #1233: "Restart to update" always pops up, even after restarting
   • Stuck on version 109 #380: Stuck on version 109

   Feel free to ignore if none of these address your specific case.
4. rekram1-node

   removed

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Dec 13, 2025
5. rekram1-node commented on Dec 13, 2025

   

   rekram1-node

   on Dec 13, 2025

   Contributor

   More actions

   github has had issues lately so i imagine it was something on their end?

   👍React with 👍1Reacted by OpeOginni
6. edlsh commented on Dec 27, 2025

   

   edlsh

   on Dec 27, 2025

   Contributor

   More actions

   npm registry has 5-min CDN caching (cache-control: max-age=300), which could cause stale version fetches. Would adding a Cache-Control: no-cache header for explicit opencode upgrade commands be welcome?
7. rekram1-node commented on Dec 27, 2025

   

   rekram1-node

   on Dec 27, 2025

   Contributor

   More actions

   @edlsh is that actually the issue here? i did notice this weirdness if I downgrade to sufficiently old version then upgrade it will do .142 for some reason, then u can upgrade again from there, this is way past a 5 min cache
8. lmBored commented on Jan 14, 2026

   

   lmBored

   on Jan 14, 2026

   Last edited by lmBored

   More actions

   Homebrew has the same issue with brew, but for brew, it seems that HOMEBREW_NO_AUTO_UPDATE: "1" in installation/index.ts is blocking update.

   Another issue is that opencode upgrade v1.1.xx also doesn't seem to work for brew.

   Edit: Also how do I test this in development? ./packages/opencode/dist/opencode-.../bin/opencode upgrade always detects it was downloaded with bun. I'm not sure how to test with brew
9. rekram1-node commented on Jan 14, 2026

   

   rekram1-node

   on Jan 14, 2026

   Contributor

   More actions

   Wdym not working for brew?
10. lmBored commented on Jan 14, 2026

    

    lmBored

    on Jan 14, 2026

    More actions

    Wdym not working for brew?

    Oops, I was missing context, this is my logs:

    ❯ brew --version
    Homebrew 5.0.10-27-g1610f0a
    
    ❯ brew list --full-name opencode
    anomalyco/tap/opencode
    
    ❯ opencode --version
    1.1.19
    
    ❯ which opencode
    /opt/homebrew/bin/opencode
    
    ❯ opencode upgrade
                                       ▄
      █▀▀█ █▀▀█ █▀▀█ █▀▀▄ █▀▀▀ █▀▀█ █▀▀█ █▀▀█
      █░░█ █░░█ █▀▀▀ █░░█ █░░░ █░░█ █░░█ █▀▀▀
      ▀▀▀▀ █▀▀▀ ▀▀▀▀ ▀  ▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀
    
    ┌  Upgrade
    │
    ●  Using method: brew
    │
    ●  From 1.1.19 → 1.1.20
    │
    ◇  Upgrade complete
    │
    └  Done
    
    ❯ opencode --version
    1.1.19
    

    Perhaps because brew upgrade is not upgrading from the correct tap - anomalyco/tap?

    👍React with 👍2Reacted by rubenschulze and Pamela
11. jd-santos commented on Jan 18, 2026

    

    jd-santos

    on Jan 18, 2026

    More actions

    Is there an answer or workaround here? I'm not able to update beyond 1.1.20 with brew upgrade or opencode upgrade.

    👍React with 👍1Reacted by Ritesh Ranjan
12. lmBored commented on Jan 19, 2026

    

    lmBored

    on Jan 19, 2026

    More actions

    Is there an answer or workaround here? I'm not able to update beyond 1.1.20 with brew upgrade or opencode upgrade.

    Did you tap the correct tap? It should look be this tap: anomalyco/tap/opencode. And brew upgrade opencode works just fine for me
13. ritesh24 commented on Jan 22, 2026

    

    ritesh24

    on Jan 22, 2026

    More actions

    Unable to update from 1.1.20 to 1.1.32
14. ritesh24 commented on Jan 24, 2026

    

    ritesh24

    on Jan 24, 2026

    More actions

    I tried this command in terminal and it worked. May help..

    `brew update

    TAP_DIR="$(brew --repo anomalyco/tap)"
    git -C "$TAP_DIR" pull --rebase

    brew upgrade anomalyco/tap/opencode
    hash -r
    opencode --version`

    👍React with 👍4Reacted by Tom Fitzpatrick, Pratik Thapa, Trym Veiby and Stf-F

    🚀React with 🚀1Reacted by Stf-F
15. 6 remaining items

    Load more
16. BryceRyan

    added a commit that references this issue on Feb 10, 2026

    fix: resolve homebrew upgrade requiring multiple runs (anomalyco#5375) (

    ...

    dc06cf1
17. relaxkeren

    added a commit that references this issue on Feb 15, 2026

    fix: resolve homebrew upgrade requiring multiple runs (anomalyco#5375) (

    ...

    4127e9b
18. schneiderlo

    added a commit that references this issue on Feb 17, 2026

    fix: resolve homebrew upgrade requiring multiple runs (anomalyco#5375) (

    ...

    f4f43d5
19. NeilsC commented on Apr 6, 2026

    

    NeilsC

    on Apr 6, 2026

    More actions

    I was running into this on Linux as well. The root cause was that the old version of opencode was installed in ~/.local/bin, and opencode upgrade was installing the new version in ~/.opencode/bin. Manually deleting the old version fixed the issue.
20. Rwanbt

    added a commit that references this issue on May 5, 2026

    fix: resolve homebrew upgrade requiring multiple runs (anomalyco#5375) (

    ...

    70334bf
21. patriciomg commented on Jun 12, 2026

    

    patriciomg

    on Jun 12, 2026

    More actions

    I had the same problem. The solution was running brew upgrade opencode
    by running: opencode upgrade or opencode upgrade --method brew did not work.
22. Rwanbt

    added a commit that references this issue on Jun 14, 2026

    fix: resolve homebrew upgrade requiring multiple runs (anomalyco#5375) (

    ...

    2bf1ccb
23. MarsQiu007

    added a commit that references this issue on Jul 31, 2026

    fix: resolve homebrew upgrade requiring multiple runs (#5375) (#10118)

    116233e