OpenCode added interactive reports and demos in its October 30, 2026 release, giving developers, consultants and small teams already using the AI coding agent a way to deliver work as a web page. The new artifacts feature lets the agent store, retrieve, update and delete those deliverables.
Who can open the result depends on where it is hosted. The built-in provider serves the report from the OpenCode server. A local link is not an automatically public website.
Version 2.2.4 includes the feature, but it is experimental and disabled by default. To try it, set experimental.artifacts to true in the existing opencode.json configuration, preserving unrelated settings.
When an interactive page is worth it
Consider a hypothetical project report whose reader can filter tasks by team or status. That could suit a review meeting better than a long chat response. If the reader only needs a short explanation or fixed summary, an ordinary document is likely the simpler choice.
The built-in host supports static files, including JavaScript that runs in the browser. It does not provide a backend that runs application code or a database. A filterable page can fit that model; a service that stores customer accounts needs a separate runtime or a suitable custom provider.
Who can open the local link
OpenCode’s current web guide says its normal server listens only on localhost by default—meaning the machine running it—and browser access is password-protected. Sending that address to a colleague does not make your server reachable from their computer.
Two conditions matter: the recipient must be able to reach the running server, and they must have the access that server requires. Artifacts use the ordinary server authorization layer; they are not report-only guest invitations.
Remote access to an existing server can let an authorized colleague view a local artifact without moving it to another host. That is different from publishing a standalone page. The local viewing link still depends on the OpenCode server being available.
When separate hosting makes sense
For your own work, or review by colleagues already authorized to use that server, built-in hosting may be enough. For a client or outside audience who should receive only the finished report, separate hosting with appropriate viewer access is the more suitable arrangement.
OpenCode’s provider extension mechanism lets plugins connect other storage or hosting services to artifact creation and updates. It is not evidence that ready-made cloud integrations or hosting plans are included. Availability, price and service limits need checking for the particular provider you intend to use.
Managed teams considering a hosting plugin should also review their extension permissions; RohitAI’s guide to OpenCode’s access-rule changes covers that separate decision.
Creating and revising a report may incur model charges. OpenCode’s billing guide distinguishes Console usage from usage billed by your own provider. Neither establishes an included allowance for external artifact hosting, so budget for generation and delivery separately.
Keep the approved copy separate
A local artifact’s update replaces its files while keeping the same viewing URL. That is useful for an evolving report, but a link sent for approval may later show different content.
If a colleague or client signs off a version, preserve a separate dated copy of its files and underlying inputs. Use the live link for ongoing revisions, not as the sole record of what was approved.
Before choosing this format, identify who must open the page, confirm their access, and check the page’s controls and calculations in the intended browser. If interaction adds little—or the recipient needs an unchanging document—there is no need to turn the deliverable into a hosted page.