Skip to content

Commit fa024bd

Browse files
release notes: v0.49.33
Co-authored-by: Alfonso <alfonso-magic-context@users.noreply.github.com>
1 parent 1bd4aae commit fa024bd

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# v0.49.33
2+
3+
This patch stops OpenCode 2 sessions from paying two full prompt-cache writes when their tool list changes.
4+
5+
## Upgrading
6+
7+
- Restart OpenCode after updating. No database migration is needed.
8+
9+
## Fixed
10+
11+
- **A tool-list change cost two full cache writes on OpenCode 2 (#819, thanks @iceteaSA):** when a plugin reload added, removed or renamed tools, the provider lost its cached prompt on the next request, but Magic Context treated that pass as a cache hit. Its history head stayed as it was and its queued drops stayed held, so each session paid a second full write later, when those drops finally landed. On OpenCode 2, a change to the names or descriptions of the tools a session sends now rebuilds the history head once, and the queued drops and cleanup land in that same rebuild.
12+
- **Upgrading:** the first pass after the upgrade records each session's tool list without rebuilding.
13+
- **Schema-only differences:** a change to a tool's schema alone never counts, so it can't cause a rebuild that the provider wouldn't already pay for.
14+
- **Known limits:** a plugin that changes the tool list after Magic Context's hook isn't seen. A tool entry that OpenCode drops before sending can still cause one rebuild when its description changes.
15+
- **OpenCode 1 and Pi:** unchanged. Their tool-list signal is shared by every session in the process, so it still isn't used.

0 commit comments

Comments
 (0)