OpenCode v1.18.34: signed macOS binaries and session identity headers#
Published by Alex Sorokoletov
Part of the OpenCode Version Tracker series. | OpenCode on GitHub | Releases
Coming from v1.18.33, OpenCode v1.18.34 is a maintenance release with three Core bugfixes: macOS release binaries are now signed with a Developer ID, locally compiled macOS binaries are re-signed so they run reliably on macOS 27 and newer, and model requests now carry namespaced session and parent-session identity headers.[1]
No environment variables or experimental config keys changed in this release. The fixes below are the whole of v1.18.34.
The fixes#
| Fix | What It Does |
|---|---|
| macOS release signing | Release binaries are signed with a Developer ID. |
| macOS 27+ compatibility | Locally compiled macOS binaries are re-signed after the build so they run reliably on macOS 27 and newer. |
| Session identity headers | Model requests carry namespaced headers identifying the session and its parent session. |
| TUI /status plugin names | The /status dialog uses the platform's path separator when extracting plugin names. |
macOS binaries#
Two of the three Core fixes concern how OpenCode's macOS binaries are signed. Release binaries now carry a Developer ID signature.[1] Separately, binaries compiled locally are re-signed after the build so they run reliably on macOS 27 and newer, which the release notes state as the reason for the change.[1]
The re-sign step applies to the self-built path: OpenCode is open source, so users can compile it themselves, and a locally produced binary now gets a signature that macOS 27 accepts. The Developer ID change covers the binaries shipped in a release. Both land on the same terminal-agent build, so a Mac user on a current OS gets a binary that runs without the signature friction that a newer macOS enforces.
Session identity and the TUI#
Model requests now include namespaced headers that carry the session identity and its parent-session identity.[1] The release notes describe the header change without further detail, so what it enables downstream is not stated in this release.
In the terminal UI, one community fix changes how the /status dialog extracts a plugin's name: it now uses the platform's path separator instead of a hardcoded one, so the name resolves correctly on any OS.[1] A documentation correction to GPT 6.1 Sol cache pricing rounds out the release.[1]
What this tells us#
v1.18.34 is a maintenance point release, typical of OpenCode's near-daily cadence: a small batch of fixes between larger feature windows, with the configuration surface untouched. The concentration here is macOS distribution, both the signed release binaries and the re-signed local compiles.
Signing is upkeep that an open-source, self-buildable agent carries directly. OpenCode ships binaries for every platform it supports and also lets users compile their own, so a single macOS signing requirement becomes two shipped fixes: one for the release artifacts and one for the self-built path. The identity-header change sits alongside as a smaller correction to how requests are labeled on their way to a model.
Sources#
- OpenCode releases and changelog, v1.18.34 release notes
All trademarks and software referenced belong to their respective owners.
Previous OpenCode analysis: v1.18.33 (September 28, 2026)
All 5 OpenCode analyses: OpenCode Version Tracker · Official OpenCode changelog
OpenCode reference (v1.18.34)