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
Thank you to 1 community contributor:
- @sisyphus-dev-ai:
- Merge pull request #7517 from code-yeongyu/release/v5.0.0-beta.30-source-state