# oh-my-openagent v5.0.0-beta.30

- Product: oh-my-openagent (https://whatsnew.fyi/product/oh-my-openagent)
- Vendor: oh-my-openagent
- Date: 2026-08-30
- Version: v5.0.0-beta.30
- Original notes: https://github.com/code-yeongyu/oh-my-openagent/releases/tag/v5.0.0-beta.30
- Permalink: https://whatsnew.fyi/product/oh-my-openagent/releases/v5.0.0-beta.30
- Labels: Pre-release

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Steering a message into a running turn no longer loses the message when the shared interactive host socket drops
- **fixed** — TUI degrades gracefully when the host connection goes away instead of throwing a raw Error: Client not started
- **added** — RpcTransportGoneError type added for typed error handling on transport disconnection
- **added** — onDisconnect notification added for connection state changes
- **fixed** — Session events survive a deferred rebind and are delivered once the client reattaches
- **fixed** — Screen writes are serialized with a bounded backlog, and queued writes and resizes are absorbed or merged cleanly
- **fixed** — Terminal replays no longer split or drop under trim and flush
- **fixed** — Deterministic fail-safe tool admission with preserved structured tool results and lane ownership
- **fixed** — Retry-safe reminders in compaction with a shared admission cap for multipart results
- **fixed** — Context downswitches are admission-checked against the target usable budget
- **fixed** — Equal-budget provider switches now work correctly
- **fixed** — Invalid model selections roll back instead of failing

#### omo-ai v5.0.0-beta.30 (npm 5.0.0-0.beta.30)

This is a hotfix release. Steering a message into a running turn while the shared interactive host socket dropped used to lose the message and throw a raw "Error: Client not started". The underlying fix ships in the engine (senpi PR #1220): a typed RpcTransportGoneError, an onDisconnect notification, and reconnect-or-fallback orchestration. The TUI now degrades gracefully when the host connection goes away, and your steering message isn't lost.

##### Engine (senpi v2026.8.30-3)
- rpc: session events survive a deferred rebind and are delivered once the client reattaches.
- pty and terminal: screen writes are serialized with a bounded backlog, queued writes and resizes are absorbed or merged cleanly, and replays no longer split or drop under trim and flush.
- compaction: a broad correctness pass covering deterministic fail-safe tool admission, preserved structured tool results and lane ownership, retry-safe reminders, and a shared admission cap for multipart results.
- models: context downswitches are admission-checked against the target usable budget, equal-budget provider switches work, and invalid selections roll back.

##### omo-ai changes
No omo-side commits land in this release. It picks up the engine hotfix above, so upgrading is still recommended: the "Client not started" crash path affected the omo TUI directly.


---

###### Commits

- 3abc23c23 Merge pull request #7517 from code-yeongyu/release/v5.0.0-beta.30-source-state

**Thank you to 1 community contributor:**
- @sisyphus-dev-ai:
  - Merge pull request #7517 from code-yeongyu/release/v5.0.0-beta.30-source-state