opencode 2.2.4 lets agents publish and update HTML artifacts through artifact tools, and keeps desktop terminals alive across server restarts. Teams running coding agents get shareable AI agentAn AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.Full definition → outputs and sturdier long sessions.
Key takeaways · AI-distilled
OpenCode 2.2.4 makes desktop terminals persistent session PTYs: they survive server restarts with scrollback, keep renamed titles, and stay in sync with the TUI and other windows.
Agents can publish, update and serve HTML or static artifacts once "experimental": { "artifacts": true } is set in opencode.json, through a built-in local provider or plugin storage. The SDK and plugin APIs gained matching artifact calls.
Enabled schedules now run under opencode serve, with multiple server processes coordinated so each schedule fires only once. Schedules remain opt-in through experimental.schedules.
User, project and remote config can now override Console-supplied provider names, limits, variants, settings and headers, and local OpenCode service requests no longer pass through environment-configured proxies.
Terms in this piece · Glossary
AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
