v0.16.0 makes a workload's page on the mesh screen read like the cluster's own record of it, and puts its logs on it — its own lines, and the lines the node proxy and its waypoint wrote about it, joined by the hub that knows its pods.

The Mesh screen could tell you whether your proxies were healthy and whether your control plane was still pushing config. On a cluster where the mesh runs without sidecars, that is two rows and four numbers. It now reads like a console for the fabric.

v0.14.0 closes the gaps between what v0.12 claimed for an agent and what an operator actually got — and turns the Mesh screen into a console for the fabric underneath your services.

The MCP server that shipped in v0.12 accepted exactly one credential: a personal API token, in a header. That works for a client you run yourself — Claude Code, the CLI — and it cannot work for a hosted one, which has no way to be handed a token you minted. Which is to say it could not serve the client the module's whole warning was written for.

The hub can now act as an OAuth 2.1 authorization server.

A service page could name what calls a service and what it calls. It could not show you the shape of it. Now it draws it.

v0.13.0 draws the connections the service page could only list — and finishes the work of making every image an install pulls clean at the source rather than excused by a registry.

Reading what your models cost is not the same as being able to act on it. This release closes that gap — and it opens by fixing a way of reading those spans that turned out to be wrong.

avuru obs has known a great deal about agents since v0.11 — the model calls your applications make, what they cost, when they cross a budget. Nothing let an agent know anything about your estate. The new MCP module fixes that direction of travel.

v0.12.0 turns AI spend from a number on a screen into something that reaches you — and opens the estate, read-only and on your switch, to an agent that can investigate it.

v0.11.0 adds no collection at all. Every feature in it reads spans avuru obs has been storing since your first five minutes, and asks them questions the product could not previously ask — so an install that upgrades sees its history, not just what arrives next.