v0.7.2

Fixes

A failed turn could come back twice. When a response died partway through, this plugin told OpenCode not to retry it — replaying would repeat text you had already seen and re-run any tools that had already started. But OpenCode decides retries by reading the error text, and that decision overrides the instruction not to retry. Because the message quoted the provider's own wording, an error that mentioned a rate limit or a server error was read as retryable and the turn ran again.

The same flaw applied to requests the websocket refused as too large. The refusal carried the request's size, and certain sizes read as retryable, which could revive the repeated multi-megabyte resends fixed in 0.7.1.

Both messages are now fixed wording. The details they used to carry — close code, request size, response ids, frame counts, the gap before the failure — are written to the transport log instead.

Better records when a stream dies. Failure lines now carry the response id, whether the request was a continuation, how many frames arrived, how long the silence lasted, and which frame types opened the response. Both session identifiers are on every line, so transport events and request records can be read together.

Maintenance

OpenTUI 0.5.11, Biome 2.5.13, @opencode-ai/plugin 1.18.30, @types/bun 1.4.2, and the Pi package trio at 0.85.1.

Full Changelog: v0.7.1...v0.7.2