OpenCode: share the output, not the chat

Short answerOpenCode’s /share shared the session transcript, and OpenCode has since retired session sharing. Overto shares something different: the output. Add Overto as a remote MCP server in opencode.json, sign in, and ask OpenCode to publish the page, doc or site it made.

Sharing the session vs sharing the output

OpenCode’s /share command published a link to the conversation: the prompts, tool calls and replies. That’s useful for showing how an agent worked. A reviewer usually needs the result: the report, the prototype or the spec, open in the browser, with a way to point at the part that’s wrong.

On 15 October 2026 OpenCode retired its session-sharing backend and removed the /share command from its V2 release. If you’re here because a share link stopped working or /share disappeared, that’s why.

What Overto shares instead

• Pages and sites. HTML pages and multi-page static websites, with their assets.
• Docs and files. Markdown documents, other files and audio.
• Comments on the page. Reviewers sign in with Google and comment on a sentence or an element, or draw on an HTML page.
• Versions. Every publish is a new version; the link opens the latest, and older ones stay in history.
• Privacy by default. A page opens only for the people its project allows, unless someone who manages it turns on a public link.

Connect OpenCode to Overto

1. Add the Overto MCP server

   Add Overto to ~/.config/opencode/opencode.json (create the file if it doesn’t exist):

   {
     "$schema": "https://opencode.ai/config.json",
     "mcp": {
       "overto": {
         "type": "remote",
         "url": "https://mcp.overto.work/mcp",
         "enabled": true
       }
     }
   }

   Or put the same mcp block in opencode.json in a project root to add Overto to that project only. Keep the URL unchanged; you choose the workspace when you sign in.

2. Sign in and choose your workspace

   Run opencode mcp auth overto, or just use an Overto tool and OpenCode starts the sign-in itself. opencode mcp list shows the auth status.

   Sign in with Google, choose a workspace, review the requested read, write or administration access and select Authorize. A connection stays signed in for up to seven days.

3. Check access

   Ask OpenCode to call overto_whoami. It reports the workspace you’re connected to, your upload limits and your usage. Before it makes anything visual, it reads your house style with overto_design.

4. Install the Overto skills (recommended)

   Three small instruction files teach OpenCode the Overto workflows: overto works on one artifact, overto-share publishes and revises, and overto-find searches and reviews discussions. They contain no credentials.

   for s in overto overto-share overto-find; do mkdir -p ~/.config/opencode/skills/$s && curl -fsSL https://overto.work/skills/$s/SKILL.md -o ~/.config/opencode/skills/$s/SKILL.md; done

   Restart OpenCode. In the Overto viewer, Copy for agent copies /overto <artifact-id>. In OpenCode, ask in plain words: Use the overto skill on <artifact-id>.

Publish, review and revise from OpenCode

Ask OpenCode, for example: “Publish ./docs/rfc-billing.md to Overto in the Platform project.” It calls overto_publish and returns the link and the version. Each file can be up to 25 MiB on Free, and larger on Enterprise.

When the comments are in, choose Copy for agent in the viewer and give OpenCode the artifact ID. It reads the threads with overto_comment_list, drawings included, publishes the next version on top of the one you reviewed and replies in each thread. See publishing and comments and review.

For a wider view, see how each AI tool shares what it makes.

Sources: OpenCode, MCP servers, Agent Skills, Config and pull request #55716.

Third-party product facts on this page were last checked on 24 October 2026, against each vendor’s own documentation. OpenCode is an open-source project. Overto is an independent product and is not affiliated with or endorsed by OpenCode or its maintainers.