Playbooks · Coding tasks
OpenCode 1 offers the upgrade to OpenCode 2
Written November 20, 2026
OpenCode 1.19.6 offers the upgrade to OpenCode 2: it downloads in the background and installs only when you choose, and your sessions and settings are kept.
What changed
OpenCode 1.19.6, released November 17, adds an upgrade offer inside OpenCode 1 itself. The desktop release now offers the upgrade to OpenCode 2.0 rather than leaving the move to a manual download and install. The shape of the offer is the useful part: OpenCode 2 downloads in the background, and it installs only when you choose. Nothing about the offer forces a restart in the middle of work, and nothing installs on a schedule you did not pick. The decision the offer puts in front of you is not whether the new version arrives on your machine — the download already happens — but when it takes over from the version you are running.
The three choices, and what each one commits you to
The 1.19.6 notes name three choices: Restart to upgrade, Upgrade on quit, or Later. Restart to upgrade is the immediate path: the downloaded OpenCode 2 installs and the app restarts into it, so it suits a natural break between tasks, when no session is mid-run and you want the move finished in one step. Upgrade on quit defers the install to the moment you close the app: you keep working in OpenCode 1 for the rest of the session, and the switch happens on the way out, so the next launch is OpenCode 2. Later is the open-ended deferral: you stay on OpenCode 1 and decide another time. That is the right pick when something below — plugins, in particular — needs attention first, because the offer separates downloading from installing, deferring costs nothing but time.
What carries over, and what needs an update
The notes state that your sessions, projects and settings are kept. That is the fact that makes the timing choice low-stakes: an ongoing session, the projects it belongs to and the configuration you have built up are not discarded by the upgrade, so choosing Restart to upgrade does not mean starting again from a blank install. The one exception the notes name is plugins. Plugins made for OpenCode 1 need an update, so a setup that leans on a plugin should not treat the upgrade as invisible. If a plugin is load-bearing in your daily work, Later or Upgrade on quit buys the time to line up its updated version first; if you use no plugins, or yours are already updated, there is nothing in the release standing between you and the immediate choice. For the step-by-step move itself, see Move OpenCode 1.x to 2.0 without losing config, which covers the migration in full.
Sessions with large image histories
The same release changes how image-heavy sessions behave, whether or not you take the upgrade. Sessions with many images no longer send oversized requests: when the images in a session's history pass 25 MiB, the oldest are replaced with a placeholder. The trade is plain. The request stays small enough to send, and the session continues, but the oldest images stop traveling with the history as images — the placeholder stands where they were. On a long session that has accumulated screenshots and other images step after step, that is the difference between a request that keeps working and one that grows past what can be sent. It also means early images are the first thing a very long session gives up, so an image the later work still depends on is worth keeping outside the session history as well.
When a request body is too large
The second core fix changes a failure into a recovery. A provider error for a request body that is too large now starts compaction and a retry instead of failing the turn. Before this change, that error ended the turn: the request was too big, the provider refused it, and the work stopped there. Now the same error triggers the session to compact itself and try again, which is the response that gives the turn a chance to finish — compaction is exactly the mechanism for shrinking an oversized history into something that can be sent. Together with the image placeholder change, 1.19.6 attacks oversized requests from both ends: image histories are trimmed before they pass 25 MiB, and a body that still arrives too large is compacted and retried rather than dropped.
What to do
Decide on the plugin question first, because it is the only cost the release names. If your plugins are updated or you do not rely on any, Restart to upgrade finishes the move in one step and your sessions, projects and settings come with you. If you are mid-task, Upgrade on quit lets the current session end on OpenCode 1 and starts the next one on OpenCode 2. If a plugin you need has no updated version yet, choose Later and stay on 1.19.6 — which is still worth having on its own, for the image-history limit and the compaction retry, while you wait.
Related playbooks
- OpenCode 2.3.2 stops re-billing the system prompt
- Use Claude Code login inside OpenCode
- OpenCode 2.2.7: Copilot Auto and breaking changes
- OpenCode 2.3.0: subagents move to the background
Sources
Back to: Coding playbooks hub · Also: Move OpenCode 1.x to 2.0 without losing config