Auto-update from 0.15.x broke #2512

Open
opened 2026-02-16 17:36:03 -05:00 by yindo · 4 comments
Owner

Originally created by @sawy3r on GitHub (Nov 3, 2025).

Description

I didn't realise v1.0.x had been released and got the message on load (I was running v0.15.x) stating latest version downloaded close to enable. So I did that and then got stuck in a crash loop. I was running the npm package.

opencode would launch screen would write briefly then crash and leave my terminal session stuck in bracketed paste mode. Went down the rabbit hole then somehow stumbled on https://github.com/opencode-ai/opencode and saw that was then pointing to Crush (https://github.com/charmbracelet/crush) and had been archived...

I then realised that was an unrelated (seemingly) project, but looks very similar ... started thinking there was an active attack underway. Went back to opencode.ai and then into the repo here. Saw latest release v1.0.x as of sometime today then a bunch of point releases over the course of 24 hours... still weird.

Anyway, it looks like it all checks out, but definitely left me feeling rather concerned.

OpenCode version

0.15.x (can't remember which exact version)

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @sawy3r on GitHub (Nov 3, 2025). ### Description I didn't realise v1.0.x had been released and got the message on load (I was running v0.15.x) stating latest version downloaded close to enable. So I did that and then got stuck in a crash loop. I was running the npm package. opencode would launch screen would write briefly then crash and leave my terminal session stuck in bracketed paste mode. Went down the rabbit hole then somehow stumbled on https://github.com/opencode-ai/opencode and saw that was then pointing to Crush (https://github.com/charmbracelet/crush) and had been archived... I then realised that was an unrelated (seemingly) project, but looks very similar ... started thinking there was an active attack underway. Went back to opencode.ai and then into the repo here. Saw latest release v1.0.x as of sometime today then a bunch of point releases over the course of 24 hours... still weird. Anyway, it looks like it all checks out, but definitely left me feeling rather concerned. ### OpenCode version 0.15.x (can't remember which exact version) ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the opentuibug labels 2026-02-16 17:36:03 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 3, 2025):

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

  • #3267: Another auto-update issue from 0.15.x that causes crashes (Bun segmentation fault on Windows)
  • #3691: Terminal crashes and closes shell tab after exiting OpenCode
  • #1220: Terminal session crashes right after opening OpenCode
  • #3751: Issues after upgrading from 0.15.x to 1.0.x (formatting problems)

Your issue specifically mentions getting stuck in bracketed paste mode and crash loops after auto-updating from 0.15.x to 1.0.x, which shares similar symptoms with these other reports.

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

@github-actions[bot] commented on GitHub (Nov 3, 2025): This issue might be a duplicate of existing issues. Please check: - #3267: Another auto-update issue from 0.15.x that causes crashes (Bun segmentation fault on Windows) - #3691: Terminal crashes and closes shell tab after exiting OpenCode - #1220: Terminal session crashes right after opening OpenCode - #3751: Issues after upgrading from 0.15.x to 1.0.x (formatting problems) Your issue specifically mentions getting stuck in bracketed paste mode and crash loops after auto-updating from 0.15.x to 1.0.x, which shares similar symptoms with these other reports. Feel free to ignore if none of these address your specific case.
Author
Owner

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

Hmm crash loop is worrying but we intentionally aren't auto upgrading from 0.15.x to 1.0 because there are some things still being ironed out, they should all be addressed this week though

@rekram1-node commented on GitHub (Nov 3, 2025): Hmm crash loop is worrying but we intentionally aren't auto upgrading from 0.15.x to 1.0 because there are some things still being ironed out, they should all be addressed this week though
Author
Owner

@sawy3r commented on GitHub (Nov 3, 2025):

Yeah it was quite weird, when I say crash loop, it would crash every time I'd run it, after a varying amount of time each time, sometimes straight away, others after a couple of seconds so I could start typing into the input and then it'd die. I believe it was just updating from whatever I was on from Friday last week, to v0.15.31 if that helps

@sawy3r commented on GitHub (Nov 3, 2025): Yeah it was quite weird, when I say crash loop, it would crash every time I'd run it, after a varying amount of time each time, sometimes straight away, others after a couple of seconds so I could start typing into the input and then it'd die. I believe it was just updating from whatever I was on from Friday last week, to v0.15.31 if that helps
Author
Owner

@wojons commented on GitHub (Nov 3, 2025):

My suggestion for future major releases is that you can push a message down. That says 2.x is avaliable but we are not auto updating but if you wish to upgrade run xyz

@wojons commented on GitHub (Nov 3, 2025): My suggestion for future major releases is that you can push a message down. That says 2.x is avaliable but we are not auto updating but if you wish to upgrade run xyz
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2512