Should You Upgrade to OpenCode 2? 1.19 Ends Auto-Update and Sharing
The short version: between October 11 and 16, the OpenCode 1.19 series did three things. It stopped installing updates automatically, it shut down session sharing on October 15, and on October 16 it made clear that 1.x installs will not be moved to 2.0 on their own. If you want OpenCode 2, you have to run the command yourself. If you don't, staying on 1.x is fine. Below, I go through the changes based on the official release notes and what to do before upgrading.
Everything here is current as of October 2026 and based on OpenCode's GitHub Releases.
What did each of the three releases change?
| Version | Date | Change |
|---|---|---|
| v1.19.0 | Oct 11 | Adds opencode upgrade --major to upgrade to OpenCode 2; /update in the TUI can install an update or upgrade to 2; updates are no longer installed automatically; allows OpenAI's ultrafast service tier |
| v1.19.1 | Oct 15 | Session sharing stops; existing share links and the share command no longer work, and importing a session from a share URL is no longer supported |
| v1.19.2 | Oct 16 | 1.x installs stay on the 1.x line; upgrading to 2.0 requires an explicit choice (see that release's notes for details) |
The full notes for v1.19.2 are on the Releases page. The September releases also made Cloudflare AI Gateway respect provider timeouts and redacted credentials in debug output. Neither is directly related to this upgrade.
No more auto-updates: how do I update?
Updates now have to be triggered manually, in one of two ways:
- Type
/updatein the TUI and follow the prompts. - Update the same way you originally installed OpenCode; check the official docs for the exact command.
If you only want to stay on 1.x, read the target version in the prompt before confirming, and don't accept the "upgrade to 2" option by reflex.
To check your current version, run opencode --version (confirm the exact flags with opencode --help and the official docs).
Sharing is gone: what happens to my sessions?
The release notes say only that share links and the share command no longer work, and that importing from a share URL is no longer supported. They don't offer a replacement export or migration path, and they don't say what happens to local session data. So I suggest:
- For any conversation you showed a colleague through a share link, copy the parts you need or take screenshots and archive them yourself.
- For where local sessions are stored and how to export them, follow the official docs. Don't guess at directories and start modifying files in bulk.
- Stop citing share links as a long-term ticket or review record.
What should I check before moving to OpenCode 2?
The official release notes don't include a 2.0 change list, so the items below are a general checklist, not an official 2.0 migration guide:
- Back up your config files and any custom provider and model settings, so you can roll back if the upgrade goes wrong.
- Upgrade first on a non-primary machine or a test project, and run a few real tasks.
- Find out whether anyone on your team relies on old share links. Those are dead whether you upgrade or not.
- Check whether your CI or scripts pin a version, so a reinstall doesn't leave you on a version you didn't expect.
- After upgrading, confirm that your endpoint URL, API key, and model selection still work before you start real work.
Whether it's worth upgrading depends on whether you need what 2.0 offers. The v1.19.2 notes say 1.x installs stay on the 1.x line and upgrading requires an explicit choice. If your workflow is stable, waiting a minor release or two costs you nothing.
Model calls fail after the upgrade: how do I troubleshoot?
OpenCode is only a client. Whether you get results also depends on the endpoint, the key, and the upstream service. Work through it in order:
- On cdnping's API status page, check whether the upstream endpoint is healthy, or look at vendor changes to see whether a provider changed pricing or models.
- Then walk through the network layers using the Claude Code connection troubleshooting checklist.
- For how to write a custom endpoint URL, see Configuring custom API endpoints for Claude Code, Codex, and OpenCode.
If you also use Codex, see Codex retires its old default model on October 14, and CLI 0.163 changes. A lot of tooling changed in the same week, so don't assume every problem comes from a single tool.
Want to tidy up how you connect, too?
OpenCode can connect to models from different sources through an endpoint URL plus an API key. Official APIs, cloud-vendor hosting, and aggregation gateways each involve trade-offs; for a comparison, see How to choose an AI API access method.
AGI Plan is a commercial partner of cdnping. It offers a step-by-step OpenCode setup guide, billing in RMB (the Chinese yuan) with no overseas credit card required, and states that it is not an officially authorized channel. Some models are available only outside mainland China; check https://agiplan.dev/models for which models and regions are supported. To learn more, start at https://agiplan.dev/startup. This has nothing to do with whether you upgrade to OpenCode 2, and you don't need to switch services for it.
