With MeshAgent 0.34 rooms start faster, recovery is clearer when something fails, MeshAgent Studio handles chat and file workflows more cleanly, and operators get better CLI visibility into queue state and route behavior.
A lot of this release is about removing friction. Kubernetes roompool provisioning is faster, the memory toolkit recovers more gracefully after crashes, Studio does a better job handling connection state, chat output, and file workflows.
MeshAgent 0.34 significantly improves Kubernetes roompool provisioning, which reduces startup time for on-demand rooms.
This release also improves recovery behavior in the memory toolkit. Crashed worker pools now restart automatically, crash diagnostics are logged with more detail, and memory operations retry after recovery.
In practice, this means less friction at startup and less manual cleanup when infrastructure or worker processes fail unexpectedly.
Studio and the Dart UI layer now handle retryable room connection failures more cleanly. Close codes and reasons are surfaced explicitly, `RoomConnectionScope` supports retry and backoff behavior, and the UI can show when the client is retrying. Teams can also provide custom `RoomClient` factories when they need more control over room setup.
MeshAgent 0.34 also improves cross-room file attachment and import flows, sorts file browser entries more cleanly, and adds agent-aware input placeholders. Event rendering is also less noisy, with redundant completed tool calls filtered out, better empty-state customization, and cleaner transcript and voice UI empty states.
MeshAgent Studio now supports editing Markdown files directly, with preview and editor tabs built in. Together, these changes make conversations easier to follow and room files easier to manage.
MeshAgent 0.34 adds billing URL support, an account-management entry using short-id links, an updated profile menu, and a new context menu manager for web widgets such as chat inputs and editors.
On the CLI side, `meshagent room queue list` now lets you inspect room queues in either table or JSON format. Route upserts also preserve service ID annotations, which avoids unnecessary updates when service-managed routes are reconciled.
The account service now ignores invalid service configurations and continues with warnings instead of failing more broadly.
Together, these changes make MeshAgent easier to manage from both the UI and the CLI.
Join our Discord Server to stay up to date with MeshAgent releases, ask questions, and share feedback with our team.
Check out the MeshAgent documentation to start building today!
MeshAgent Studio, SDK, and Server give you everything to build, test, and deploy agentic applications, from development to production.
