Repository navigation
[Bug] Session identifier missing in OpenCode Go cache records & unstable cache hit behavior with GLM-5.2 #37598
Description
Description
When using OpenCode WebUI (v1.18.3) with the OpenCode Go provider to call GLM-5.2, I noticed two issues in the OpenCode Go web dashboard:
-
Session identifier missing in cache records: Previously, when a cache hit occurred, the cache record in the OpenCode Go web backend would show which session it belonged to. Recently, this session information is sometimes missing — some cache records have it, some don't.
-
Unstable cache hit behavior: Cache hit rate is inconsistent. Sometimes only 1-2 entries hit cache with a very high rate, but many other times cache is missed entirely. The interval between my two sessions is very short (tens of seconds to ~1 minute), so consecutive cache misses seem unexpected.
Plugins
OpenCode Go provider (built-in)
OpenCode version
v1.18.3
Steps to reproduce
- Launch OpenCode WebUI (v1.18.3) and log in via the OpenCode Go provider
- Configure the model to GLM-5.2
- Start coding sessions and observe the OpenCode Go web backend cache records
- Notice that some cache records are missing the session identifier, and cache hit rate is unstable (frequent misses despite short intervals between sessions)
Screenshot and/or share link
(TBD — will attach if needed)
Operating System
macOS 15.7.7
Terminal
WebUI (browser)
Activity
github-actions commentedon Jul 18, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is specifically about the missing session identifier in cache records (rather than the cache hit rate instability), it may be a distinct issue — please clarify in the linked threads or confirm it is not already covered.
kai-kleinbard-tyto commentedon Jul 30, 2026
Closing — stale issue with insufficient information to reproduce or act on. If this is still relevant, please reopen with the Bug Report template (version, OS, repro steps, logs).
github-actions commentedon Sep 29, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.