It should not be possible to exit opencode while it's silently updating itself to latest release #3332

Open
opened 2026-02-16 17:39:41 -05:00 by yindo · 1 comment
Owner

Originally created by @tiberiuichim on GitHub (Dec 5, 2025).

Description

I started opencode cli, then quit soon after. Next time I tried to start it, the command was not found because it was in the middle of a self-upgrade which it didn't finish. It would be also a good idea to show a toast message when it's self-updating

OpenCode version

1.0.132

Steps to reproduce

  1. Open opencode when there's an update
  2. stop it really soon after (maybe about 1 second delay)
  3. you may or may not end up with opencode missing on your system.

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @tiberiuichim on GitHub (Dec 5, 2025). ### Description I started opencode cli, then quit soon after. Next time I tried to start it, the command was not found because it was in the middle of a self-upgrade which it didn't finish. It would be also a good idea to show a toast message when it's self-updating ### OpenCode version 1.0.132 ### Steps to reproduce 1. Open opencode when there's an update 2. stop it really soon after (maybe about 1 second delay) 3. you may or may not end up with opencode missing on your system. ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the opentuibug labels 2026-02-16 17:39:41 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 5, 2025):

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

  • #4248: [FEATURE]: More transparent automatic version upgrades - Requests better visibility during automatic upgrades
  • #5049: auto update shows the updated file in "Modified Files" section - Related to update notification issues
  • #4450: (related) Request for OSC 9 terminal notifications - Proposes notification system for important events like agent completion
  • #2987: [Bug] All sessions are gone - Related issue where interrupted operations caused data loss (from /compact command)

The core issues appear to be:

  1. Lack of user notification during self-updates (preventing accidental interruption)
  2. No mechanism to prevent exit while critical operations (like upgrades) are in progress
  3. Incomplete update recovery - if the update is interrupted, the installation becomes broken

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

@github-actions[bot] commented on GitHub (Dec 5, 2025): This issue might be a duplicate of existing issues. Please check: - #4248: [FEATURE]: More transparent automatic version upgrades - Requests better visibility during automatic upgrades - #5049: auto update shows the updated file in "Modified Files" section - Related to update notification issues - #4450: (related) Request for OSC 9 terminal notifications - Proposes notification system for important events like agent completion - #2987: [Bug] All sessions are gone - Related issue where interrupted operations caused data loss (from `/compact` command) The core issues appear to be: 1. **Lack of user notification** during self-updates (preventing accidental interruption) 2. **No mechanism to prevent exit** while critical operations (like upgrades) are in progress 3. **Incomplete update recovery** - if the update is interrupted, the installation becomes broken Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3332