v0.0.5

What's Changed

• fix: Let users open conversation history and send messages in #116
• Capability binding status permissions in #114

Full Changelog: v0.0.4...v0.0.5

v0.0.4

What's Changed

• feat(ui): render the chat dock vertically with its own close button by @mattdjenkinson in #113

Full Changelog: v0.0.3...v0.0.4

v0.0.3

Three weeks of work. The headline is that Patch can now be configured from the control plane, but this release carries several user-visible changes alongside it.

Chat

• A flat-SSE chat endpoint alongside A2A, with heartbeats so idle proxies stop cutting long turns.
• Archive and delete conversations, from the CLI and the portal.
• Tool and skill names no longer leak into answers.

Capabilities

• Patch can read what a project is entitled to from that project's own control plane (CapabilityBinding), instead of a file that gives every project everything. The service catalog fills it in from each provider's registration, and Patch writes back what it could actually use.
• Host allow-list settings that could never match — a URL, or a host with a port — now refuse to start rather than silently doing nothing.

Operations

• The apiserver's chat turns are metered.
• Alerts and a runbook for a degraded capability source.
• CAPABILITY_SOURCE names the source explicitly; inferring it from a companion setting is deprecated.

Enabling the control-plane capability source is a separate deployment step; this release only makes it available.

v0.0.2

Fixes the chat dock in the cloud portal and ships Patch as a datumctl plugin.

Fixed

• Conversations no longer cut off mid-answer. A turn that took longer than about ten seconds was terminated by the aggregated API and surfaced in the browser as a connection error. Streamed replies now run for as long as the answer takes.
• The chat dock loads alongside the rest of the portal. Shared frontend libraries are resolved from whatever the host page already provides instead of being pinned to a version the portal may not run.

Added

• datumctl plugin. Talk to Patch from the CLI. This release publishes per-platform archives for Linux, macOS, and Windows.
• Self-registering service catalog entry. The assistant declares its own platform registration, so enabling it for a project no longer depends on a separate manifest maintained elsewhere.

Deploying

The bundle at ghcr.io/milo-os/assistant-kustomize:v0.0.2 pins this release's image. Deployments tracking main-branch prereleases are unaffected by this tag.

v0.0.1

First tagged release of Patch, the assistant service.

Patch answers conversation requests for a project, reads that project's resources, and can now change them — refusing to apply anything the customer was not already shown.

What's in it

• Conversations over A2A, with durable history, project memory, and capability documents that let a service contribute its own tools, knowledge and procedures to every entitled customer's assistant.
• Base platform tools that every project gets without any provider publishing anything: list and read its resources, describe what a kind's fields are, look up where a service is offered to it, and check how much of its allowance is left.
• A change path — validate, plan, apply. A plan returns the exact manifests and a token that stands for them. Apply re-derives that token and refuses any mismatch, so a manifest edited after the plan, a reordered list, a token from another project, or a resource someone else changed in between cannot be applied. A change nobody was shown has no token at all.
• An aggregated API for conversations, registered with Milo.

Deploying

The bundle at ghcr.io/milo-os/assistant-kustomize:v0.0.1 pins this release's image into config/base, so a consumer tracking stable semver gets a concrete image rather than a floating one. Deployments that track main-branch prereleases are unaffected by this tag.

Set PLAN_TOKEN_KEY in any deployment that runs more than one replica or expects a plan to survive a restart. Left unset, each process generates its own key and says so at startup.