v0.12.2
Agent memory can be imported with the history it came with, workspace resource figures appear on ECS deployments, and the admin Egress screen works on Postgres.
- Importing agent memory can now migrate, taking the other environment’s history with it. Applying a bundle used to keep only its latest state, so the past it carried was discarded — even though moving to a new environment and bringing the history along is the obvious thing to want. Migrating rebases onto the imported lineage, so the history list, diffs and restore all work against it; what was there before is kept and can still be reached.
- Workspace resources — memory, CPU and disk — are measured on ECS deployments. Member details showed dashes for all three: the figures were read as though the Control Plane and the workspace shared a host, which is true of a local Docker deployment and of nothing else. Disk is now the usage and capacity of the filesystem the persistent home sits on.
- The admin Egress screen failed on Postgres deployments, and so did the egress statistics over MCP. SQLite deployments were unaffected.
Upgrade notes
Section titled “Upgrade notes”Nothing to do.