OpenCode session sharing removed: what 1.19.0–1.19.2 changed
OpenCode 1.19.1 (2026-10-15) has discontinued session sharing, so old share links no longer work; since 1.19.0 you move to OpenCode 2 yourself with `opencode upgrade --major`, and since 1.19.2 a 1.x install is not offered a 2.x build.
Updated 2026-10-19
Point this tool at the QCode endpoint — one key for Claude, GPT and Chinese models.
- Billed per token — live rates on /models
- Pay by card (Visa / Mastercard / AMEX), Apple Pay, Google Pay or crypto
- Self-service: top up and activate instantly
What changed: sharing removed, explicit upgrade, the 1.x line, QCode config
the wording in 1.19.1
The 1.19.1 release states that session sharing is discontinued: existing share links no longer open, the sharing commands are gone, and importing a session from a share URL is unsupported.
the major upgrade command since 1.19.0
1.19.0 added the explicit major upgrade command. On the command line it is `opencode upgrade --major`, in the interface the 2.0 offer in /update; in the TUI, /update installs updates or upgrades to OpenCode 2, and updates have to be triggered by hand.
the release line note in 1.19.2
1.19.2 states that 1.x checks only the npm opencode-ai latest version, so a 1.x install is never offered a 2.x build as a regular update; the install script refuses 2.x versions as well.
the opencode.json file on the QCode side
Following the QCode docs page OpenCode integration: the config file is ~/.config/opencode/opencode.json and the key is stored in auth.json via opencode auth login; the baseURL of the two providers is https://api.qcode.cc/claude/v1 and https://api.qcode.cc/openai/v1; the model fields are model and small_model. On QCode these models are available: claude-sonnet-5-5, claude-opus-5-5, claude-haiku-5-5, gpt-6.1-sol, gpt-6-sol, gpt-5.6-terra, and the list is on qcode.cc/models. Note: the docs say that using OpenCode requires the direct API request permission first, and that permission is off by default.
Why my share links stopped opening
Since 1.19.1 session sharing has been discontinued, so old share links no longer open. The official wording is that sharing is discontinued, with no mention of a plan to bring it back. After 1.19.2 a 1.x install is not offered a 2.x build either, so in this period the end of sharing and the explicit upgrade show up together.
1.19.0–1.19.2 official releases (checked 2026-10-19; the 1.19.3 change does not touch the two points on this page)
Checked on 2026-10-19 against the official OpenCode releases: 1.19.0 (published 2026-10-11) added the explicit major upgrade command and stopped installing updates automatically; 1.19.1 (published 2026-10-15) discontinued session sharing; 1.19.2 (published 2026-10-16) keeps OpenCode 1 on the 1.x line, and the install script refuses 2.x versions. The releases came one after another, only days apart; 1.19.3 (published 2026-10-16) only covers reasoning options and reasoning variants, so it does not touch session sharing or the upgrade path.
the releases and the dates
1.19.0 is published: it adds the explicit major upgrade command `opencode upgrade --major`; in the TUI, /update installs updates or upgrades to OpenCode 2, and updates are no longer installed automatically.
1.19.1 is published: the official wording is that session sharing is discontinued.
1.19.2 is published: 1.x stays on the 1.x line and is not offered a 2.x build as a regular update; upgrading to OpenCode 2 becomes an explicit step, and the install script refuses 2.x versions.
What the official releases state and what they leave open
Confirmed (word for word in the official releases)
① session sharing is discontinued, the existing share links and sharing commands are gone, and importing sessions from share URLs is no longer supported; ② `opencode upgrade --major` is the command that upgrades to OpenCode 2; ③ the interface command /update installs OpenCode updates or upgrades to OpenCode 2, and updates are no longer installed automatically; ④ OpenCode 1 stays on the 1.x release line, so 1.x installs are never offered a 2.x build as a regular update; ⑤ upgrading to OpenCode 2 remains a separate, explicit choice through the 2.0 offer in /update or `opencode upgrade --major`; ⑥ the install script refuses to install 2.x versions; ⑦ upgrades for installs managed by yarn are fixed; ⑧ 1.x updates are skipped for Homebrew Core installs, which now track OpenCode 2.
What the official releases leave open
The releases do not say: which features OpenCode 2.0 adds, because they only cover the upgrade entry point and the release line; what differs between 1.x and 2.x; and how the costs of moving to 2.0 compare, because no cost comparison is given. The QCode docs only cover how to configure a key; the commercial relationship between OpenCode and QCode is not in the documentation.
Stay on 1.x or move to OpenCode 2
Stay on 1.x
What staying on 1.x means: 1.19.2 states that a 1.x install is never offered a 2.x build as a regular update; since 1.19.0 updates are no longer installed automatically either, you install them with /update yourself. So you are not silently moved, but new releases are yours to look at.
Move to OpenCode 2
What moving to OpenCode 2 means: the official answer is an explicit action — `opencode upgrade --major` on the command line, or the 2.0 offer in /update. A 1.x install is not replaced silently. The releases say nothing about how an upgrade affects local sessions, so copy your session directory first as a precaution.
The checks before and after the upgrade
① Copy the session directory first: the releases say nothing about how an upgrade affects local sessions, so copy the important ones locally as a precaution. ② Check the version and the release line: whether you run 1.x or 2.x, 1.x is not offered a 2.x build as a regular update. ③ Pick one of the two upgrade routes: the command line opencode upgrade --major, or the 2.0 offer in the /update screen. ④ Handle the dead share links: by the official wording the old links are no longer available, so treat them as unusable. ⑤ Check the config: compare the provider and baseURL in ~/.config/opencode/opencode.json with the QCode docs, the key lives in auth.json; the docs were checked against OpenCode v1.19.0, and the releases do not say whether the 2.0 configuration changes. ⑥ Verify after installing: run one session and check that the model name and the baseURL still work.
Configure OpenCode with a QCode key
Following the QCode docs page OpenCode integration: the config file is ~/.config/opencode/opencode.json; the baseURL of the providers is https://api.qcode.cc/claude/v1 and https://api.qcode.cc/openai/v1; the key is stored in auth.json via opencode auth login, and your API key is kept in the file ~/.local/share/opencode/auth.json. The model fields are model and small_model, as the docs show: claude-sonnet-5-5 and claude-opus-5-5 by default, claude-haiku-5-5 for light tasks, gpt-6.1-sol, gpt-6-sol and gpt-5.6-terra for GPT; on QCode these models are available, and the list is on qcode.cc/models. Note: the docs say that using OpenCode requires the direct API request permission first; that permission is off by default, and the same page says how to enable it. The QCode docs were last checked on 2026-10-15 against OpenCode v1.19.0; they do not say whether the configuration is the same under 2.x. QCode is prepaid: top up first, then buy a plan or a Pay-as-you-go Pack, and the purchase is deducted from the balance; 5 concurrent requests, the same models as the personal plans; billed per token, per-model rates are on /models. Not ready for a monthly plan? Pay-as-you-go Packs start at $4 for a one-time quota you use within 7 to 90 days.
Frequently asked questions
Can I still use my OpenCode share links?
No. The release names no replacement, so keep important sessions locally: copy them before you upgrade, because the old share links no longer open and the session directory is yours to back up.
How do I upgrade to OpenCode 2?
The upgrade path is always explicit. On the command line it is `opencode upgrade --major`; in the interface it is the 2.0 offer in /update. Since 1.19.0 updates are no longer installed automatically, this step is yours to make.
Will 1.x be upgraded to 2.x automatically?
No. 1.19.2 says that 1.x only checks the latest npm `opencode-ai` version, so 1.x installs are never offered a 2.x build as a regular update, and the install script refuses to install 2.x versions. So 1.x stays on 1.x, and moving to 2.0 is a choice you make yourself.
Without session sharing, can I still keep sessions?
The official releases say nothing about local sessions; they only state that session sharing is discontinued, and they do not say that local sessions are deleted. Whether your local sessions are still there, check the session directory on your own machine; copy the important one before you upgrade.
How do I configure the QCode key in OpenCode?
Follow the QCode docs page OpenCode integration: the config file is ~/.config/opencode/opencode.json, the baseURL of the providers is https://api.qcode.cc/claude/v1 and https://api.qcode.cc/openai/v1, the key is stored in auth.json via opencode auth login, and model and small_model are filled as the docs show. The model list is on /models. One more thing: the docs say that using OpenCode requires the direct API request permission first, and that permission is off by default.
Should I upgrade to OpenCode 2 now?
What the official releases give across these versions is mechanism: the end of session sharing and how the upgrade path from 1.x to 2.x works. There is no feature list for 2.0 and no cost comparison, so the official side gives no verdict on whether to move; run through the steps above first, in particular backing up the session directory and checking whether you are on 1.x.
Sources
Official wording: the official OpenCode release pages (github.com/anomalyco/opencode/releases, the repository was formerly sst/opencode and the old address redirects; fetched and checked on 2026-10-19: v1.19.0 published 2026-10-11, v1.19.1 published 2026-10-15, v1.19.2 published 2026-10-16, v1.19.3 published 2026-10-16). On the QCode side: the pages OpenCode integration and Endpoints and API paths on docs.qcode.cc (fetched and checked 2026-10-19), and the Pay-as-you-go Pack page on qcode.cc in five languages (fetched and checked 2026-10-19).
Keep running OpenCode with a QCode key
Not ready for a monthly plan? Pay-as-you-go Packs start at $4 for a one-time quota you use within 7 to 90 days.
Related reading
Pay-as-you-go Packs
One-time quota packs valid for 7–90 days, no subscription; extra packs add to the same key
OpenCode Guide
Complete guide to OpenCode open-source AI coding assistant
OpenCode Zen vs Go: differences and how to choose
Zen is pay-as-you-go, Go is $10 or $40 a month: prices, models, limits and how to choose, checked 2026-10-15.
Crypto payment guide
Nine coins, 56 networks, zero platform fee for AI coding API credits.
This page was checked on 2026-10-19 against the official OpenCode releases; version behaviour changes with the version, later versions may adjust it, so the official releases are the reference. Model availability on the QCode side is listed on /models.