OpenCode has ended its hosted session-sharing feature, changing how developers, consultants and software teams pass AI coding conversations to colleagues or clients. The project says existing share links and sharing commands are unavailable, and sessions can no longer be imported from those URLs, according to its October 15, 2026 release notice.
That dates the release notice, not a verified shutdown time. The notice gives neither a reason for the retirement nor a replacement timetable.
The alternative starts with a retained session
OpenCode's current command-line reference still documents exporting a conversation as a JSON session-data file and importing that file. The practical distinction is whether someone still has the session—not whether they kept its old link.
What you have | Recommended next step |
|---|---|
A retained session | Export a reviewed copy for the recipient; confirm that their installed version can use it. |
Only an old share link | Ask the original sender for a retained session or export. The reviewed sources do not establish recovery from the URL alone. |
For V1 users, the CLI reference and v1.19.1 export source support these illustrative commands. Check your installed version's help and choose a new output filename:
# Sender: replace SESSION_ID with the retained session's ID
opencode export SESSION_ID > session.json
# Recipient: after receiving the reviewed file
opencode import session.jsonThis transfers conversation records, not a complete project. The v1.19.1 import implementation reads those records into the current project; it does not fetch the code repository or recreate the working environment. Compatibility between different versions remains unverified.
Sanitizing a file can remove useful context
The optional --sanitize export flag is not simply a filter for secret-looking strings. In the v1.19.1 source, it replaces ordinary conversation text, tool inputs and completed outputs, and various file fields with redaction markers.
That creates a tradeoff: a heavily redacted file may omit the context needed to continue work, while an unredacted one needs careful review before sharing. Check both what the recipient may see and what they actually need; a short written summary may be enough. The option is not a guarantee that every sensitive field is removed.
Upgrading is a separate decision. The October 15 V2 changelog also records removal of the sharing backend and /share command, so V2 is not a restoration of the retired link service. RohitAI’s October 11 OpenCode 2 migration guide covers plugin and integration checks for readers considering that move.
For teams, the immediate task is to update support instructions and client handoff templates that still ask for session links. Locate any retained conversation before choosing a reviewed file transfer or a concise summary.
Reporting note: This AI-assisted news brief draws on OpenCode’s release notes, documentation and tagged source code checked on October 16, 2026. Transfer recommendations are source-based analysis; no export/import or cross-version tests were performed.