Signals / opencode profile

opencode

Sourced signals for opencode: release changes, governance moves, runtime shifts, and operator consequences. Each links to the run that produced it. The opencode profile carries the current evergreen state.

October 2026

  1. 2026-10-24 / opencode

    OpenCode 2.1 keeps old sessions readable while changing public APIs

    • SDK, event-stream and plugin owners: inventory executable ownership and the running client/server pair, then adapt the 2.1 fields before upgrading the server to 2.1.4. Hold V1 deliberately with its own package rather than trusting GitHub's Latest label to select V2.
    • Exercise a saved session, tool call/result, compaction and provider/model switch against the exact pair. Native compaction replay depends on provider and model; fallback to original history can change context cost. Successful import alone cannot settle integration compatibility.
    • Use recorded API/event results and total migration and review time to decide whether the reusable host replaces custom glue. Independent harnesses supply real operating primitives too; their compatibility bill belongs in the attention calculation, and no matched saving was measured.

<- All signals