
今天早上我打开 opencode,版本号告诉我 1.17.15。我愣了一下——前天刚装的 v1.17.14 怎么就过时了? 仔细一看,v1.17.14 发布时间是 2026-07-07 02:50 BJT,v1.17.15 是 2026-07-07 23:31 BJT。中间只隔了 20 小时 41 分钟。
这不科学。OpenCode 从 v1.17.0 到现在,平均每个版本间隔 2-3 天,长的有 5 天。怎么 v1.17.15 突然就插队了?
我去 GitHub 把 v1.17.14 → v1.17.15 的 commits 和 PR 翻了一遍,6 个 PR、26 个 commits、92 个文件、0 个新功能——这根本不是常规版本,是一次热修补丁(hotfix)。

这次插队的 6 个 PR,全是 bugfix
v1.17.15 的 release notes 一共 6 个 PR,我数了一下分布:
- @arvsrn(Aarav Sareen):4 个(66%)—— 全是 Desktop 端 UI 调整
- @StarpTech:1 个(17%)—— Core 端权限路径解析
- @fengjikui(冯基魁):1 个(17%)—— LLM 错误分类
没有任何新功能,全部是 bugfix。
这跟 v1.17.14 的「181 个 PR、115 个 commits、13 个 contributor、5 天开发周期」完全不是一个量级。v1.17.15 不是迭代,是补丁。

arvsrn 一人扛了 4 个,都是 Desktop UI
@arvsrn(Aarav Sareen)是 OpenCode 团队里专门做 Desktop 端的工程师,这次 v1.17.15 里他 1 个人贡献了 4 个 PR:
- #35081(26 行):macOS Sequoia 标题栏错位修复 —— Sequoia(macOS 15)的标题栏和 traffic light 按钮位置不对,4 行代码调整
- #35087(74 行):模型选择器恢复 model context tooltip —— 之前 v1.17.14 改 UI 时把鼠标悬停的 tooltip 弄丢了
- #35134(5 行):视觉细节调整
- #35152(833 行):把 Cmd+K 菜单对齐 v2 风格 —— 这个最大,833 行新增 + 367 行删除,4 个文件,是 v1.17.15 里唯一的大改
#35152 是这次 v1.17.15 唯一一个值得专门说一下的 PR。其它 5 个都是"修个 bug 就好",但 Cmd+K 命令面板对齐 v2 风格——这是 v1.17.14 引入的 v2 桌面 UI 的一次"补课"。
我猜 v1.17.14 发布的时候,Cmd+K 菜单用的是旧版的样式,跟 v2 桌面 UI 整体风格不一致。社区提了 issue,arvsrn 当天晚上就合进去了。
1 个被忽略但重要的 PR:#35737
@StarpTech 提的 #35737 fix(core): expand home-relative permission paths 是这次最容易被忽略、但对用户最实在的修复。
这个 PR 解决的问题:OpenCode 之前在读配置文件时,如果配置目录在 home 目录下(~/.config/opencode/xxx),权限校验只检查相对路径,不展开 home 目录。这会导致某些 permission 规则没生效。
具体场景:你在 opencode.json 里写了
{ "permission": { "bash": { "~/scripts/*": "allow" } }}v1.17.14 之前,OpenCode 看到 ~/scripts/* 不会展开成 /Users/yourname/scripts/*,所以这个 allow 规则实际上没起作用。在 v1.17.14 升级到 v1.17.15 之后,这个 bug 修了。
如果你之前在 OpenCode 里写过 ~ 开头的 permission 规则并且发现"为什么不生效",升 v1.17.15 之后再试一次。
还有一个 PR:#35671 Z.ai 错误分类
@fengjikui 提的 #35671 fix(llm): classify zai token limit overflow 是关于智谱 AI(Z.ai)的错误处理。
之前 OpenCode 调用智谱的 GLM 模型时,如果触发了 context window 上限,会报一个比较模糊的错误("UnknownError"),用户看到不知道是 token 不够了还是网络问题。v1.17.15 把这个错误专门归类为"Z.ai context-window overflow",前端可以专门提示"上下文太长了,请开启新会话"。
这个 PR 只有 10 行代码,但对智谱 AI 用户是救命的功能——之前不知道为什么突然报错的体验很差。
我升 v1.17.15 之后:踩了个小坑
我上午升级完之后跑 opencode run "hello",报了个 UnknownError。我以为是网络问题,重试几次还是一样。
翻 v1.17.15 的 release notes 找不到相关说明,去 GitHub issues 搜了一下,发现是 opencode-token-monitor 插件和 v1.17.15 不兼容。token-monitor 在新版的 session.idle hook 里拿不到有效的时间戳,导致 session 保存失败。
临时解决方案:opencode plugin remove opencode-token-monitor 卸载掉这个插件,或者等插件作者适配新版本。
这是我升 v1.17.15 唯一遇到的坑。官方核心功能没问题,token-monitor 这种第三方插件在版本切换时偶尔会出岔子。
要不要升级到 v1.17.15?
我的建议:
应该升:
- 用 macOS Sequoia 的 —— #35081 修了你那个标题栏错位
- 用过智谱 GLM 的 —— #35671 让错误信息可读
- 写过
~/xxx路径 permission 规则的 —— #35737 修了路径展开 - 用过 Cmd+K 命令面板的 —— #35152 对齐了 v2 风格
可以不升:
- 只用 CLI/TUI 的 —— Desktop 端 4 个 PR 对你 0 影响
- 所有 permission 规则都写绝对路径的 —— #35737 对你 0 影响
- 用第三方插件(特别是 token-monitor / wakatime / supermemory)的 —— 等插件适配再升,避免兼容性踩坑
总结
OpenCode v1.17.15 是一次"快速补丁",不是"功能更新"。20 小时插队是因为 v1.17.14 发布的 v2 桌面 UI 有 4 个明显的 UI 问题(标题栏 / tooltip / 主题应用 / session tab)和 1 个核心 bug(home 路径权限)。官方选择不等大版本周期,直接 hotfix 推了 v1.17.15。
OpenCode 现在的发布节奏:
- 大版本(3-5 天):带新功能、新架构
- 补丁版(0.5-1 天):修上一个版本的 bug
这是健康的——意味着官方对社区反馈响应很快。比起一些"3 个月一个大版本然后堆 200 个 PR"的工具,OpenCode 这种"小步快跑 + 快速热修"的节奏对用户更友好。
opencode upgrade 升一下,反正不需要重启会话。
This morning I opened opencode, and the version string said 1.17.15. I did a double take — I installed v1.17.14 just two days ago, how was it already outdated? Looking closer, v1.17.14 was released on 2026-07-07 at 02:50 BJT, and v1.17.15 was released at 23:31 BJT on 2026-07-07. That's a gap of only 20 hours and 41 minutes.
That doesn't make sense. From v1.17.0 to now, OpenCode releases have averaged one version every 2-3 days, with the longest gap being 5 days. Why did v1.17.15 suddenly jump the queue?
I went through the commits and PRs for v1.17.14 → v1.17.15 on GitHub: 6 PRs, 26 commits, 92 files, 0 new features — this isn't a regular release, it's a hotfix.
All 6 PRs that jumped the queue were bugfixes.
The v1.17.15 release notes contain 6 PRs total. I counted the distribution:
@arvsrn (Aarav Sareen): 4 (66%) — all Desktop UI adjustments
@StarpTech: 1 (17%) — Core-side permission path resolution
@fengjikui (Feng Jikui): 1 (17%) — LLM error classification
No new features at all, every single one is a bugfix.
This is nowhere near the scale of v1.17.14, which had "181 PRs, 115 commits, 13 contributors, 5-day development cycle." v1.17.15 isn't an iteration, it's a patch.
arvsrn carried 4 of them by himself, all Desktop UI.
@arvsrn (Aarav Sareen) is the OpenCode engineer focused on Desktop. In v1.17.15, he contributed 4 PRs by himself:
#35081 (26 lines): macOS Sequoia title bar misalignment fix — on Sequoia (macOS 15), the title bar and traffic light buttons were mispositioned; a 4-line code adjustment fixes it.
#35087 (74 lines): Model selector restores model context tooltip — v1.17.14's UI redesign accidentally dropped the hover tooltip.
#35134 (5 lines): Visual detail adjustment.
#35152 (833 lines): Aligns the Cmd+K menu with the v2 style — this is the biggest one: 833 lines added + 367 lines deleted, 4 files, and the only major change in v1.17.15.
#35152 is the only PR in v1.17.15 worth calling out specifically. The other 5 are all "just fix the bug and move on," but aligning the Cmd+K command palette with the v2 style — this is a "catch-up lesson" for the v2 desktop UI introduced in v1.17.14.
My guess: when v1.17.14 was released, the Cmd+K menu was still using the old styling, inconsistent with the overall v2 desktop UI. The community filed an issue, and arvsrn merged it that same evening.
One overlooked but important PR: #35737.
#35737 fix(core): expand home-relative permission paths by @StarpTech is the most easily overlooked fix in this release, but also the most practical one for users.
The problem this PR solves: previously, when OpenCode read config files, if the config directory was under the home directory (~/.config/opencode/xxx), the permission check only looked at the relative path and didn't expand the home directory. This caused some permission rules to silently not take effect.
Concrete scenario: you write something like this in opencode.json:
Before v1.17.15, OpenCode would see ~/scripts/* but would not expand it to /Users/yourname/scripts/*, so the allow rule effectively didn't work. After upgrading from v1.17.14 to v1.17.15, this bug is fixed.
If you previously wrote permission rules starting with ~ in OpenCode and wondered "why isn't this working," upgrade to v1.17.15 and try again.
There's one more PR: #35671 — Z.ai error classification.
#35671 fix(llm): classify zai token limit overflow by @fengjikui is about error handling for Zhipu AI (Z.ai).
Previously, when OpenCode called Zhipu's GLM models and hit the context window limit, it would report a vague error ("UnknownError"), leaving users unable to tell whether they ran out of tokens or hit a network issue. v1.17.15 now classifies this error specifically as "Z.ai context-window overflow," so the frontend can show a clear message like "Context is too long, please start a new session."
This PR is only 10 lines of code, but for Zhipu AI users it's a lifesaver — the previous experience of getting random errors without any explanation was terrible.
After upgrading to v1.17.15, I hit a small snag.
After upgrading this morning, I ran opencode run "hello" and got an UnknownError. I thought it was a network issue, retried a few times, and got the same result.
I checked the v1.17.15 release notes and found nothing about it, then searched GitHub issues and discovered that the opencode-token-monitor plugin is incompatible with v1.17.15. token-monitor can't get a valid timestamp in the new version's session.idle hook, causing session saves to fail.
Temporary workaround: run opencode plugin remove opencode-token-monitor to uninstall the plugin, or wait for the plugin author to adapt to the new version.
This is the only issue I ran into with v1.17.15. The official core functionality is fine; third-party plugins like token-monitor occasionally break during version transitions.
Should you upgrade to v1.17.15?
My recommendation:
You should upgrade if:
You use macOS Sequoia — #35081 fixes your title bar misalignment.
You've used Zhipu GLM — #35671 makes error messages readable.
You've written permission rules with ~/xxx paths — #35737 fixes path expansion.
You use the Cmd+K command palette — #35152 aligns it with the v2 style.
You can skip it if:
You only use the CLI/TUI — the 4 Desktop PRs have zero impact on you.
All your permission rules use absolute paths — #35737 has zero impact on you.
You use third-party plugins (especially token-monitor / wakatime / supermemory) — wait for plugin updates before upgrading to avoid compatibility issues.
Summary
OpenCode v1.17.15 is a "quick patch," not a "feature update." The 20-hour queue-jump happened because the v2 desktop UI released in v1.17.14 had 4 obvious UI issues (title bar / tooltip / theme application / session tab) and 1 core bug (home path permissions). The official team decided not to wait for the next major version cycle and pushed v1.17.15 as a direct hotfix.
OpenCode's current release cadence:
Major versions (3-5 days): new features, new architecture.
Patch versions (0.5-1 day): fix bugs from the previous version.
This is healthy — it means the official team responds quickly to community feedback. Compared to tools that ship "one major version every 3 months and then pile in 200 PRs," OpenCode's "small steps, fast iteration + quick hotfixes" rhythm is more user-friendly.
Just run opencode upgrade — no need to restart sessions.