Repository navigation
v0.88.0
Cotal 0.88.0 is out!
Grab it: npm i cotal-ai@0.88.0
Changes in this release
-
Presence can carry
runtime: { id, startedAt, source: "endpoint-process" }: the OS process holding the mesh connection reports its own start fromperformance.timeOrigin. Each process and lifecycle scope has its own opaque id, stable across status, activity, heartbeats and in-process reconnects. Endpoints in the same process share its start even when their lifecycles register later. The value does not date a separate parent, model harness or lifecycle. Runtime-only changes notify presence observers. Older publishers omit the field, which means unknown. -
On Windows, publishing a process record no longer fails when another handle briefly holds the old pidfile or identity pin open. Windows refused the rename with
EPERM, so a manager could exit right after boot andcotal upreported the control plane degraded (#4168). Each rename of a record now retriesEPERM,EACCESandEBUSYon Windows, as graceful-fs does, with a backoff growing from 0 to 100 ms and at most 10 s of waiting in total. A refusal that lasts longer still throws, and so does any other error or any error on another platform. -
Keep the seat control connection's TLS requirement explicit through a local primitive, preserving the recorded value without a transport default.
-
Add opt-in host-custodied tool-result consent signing and a closed capability-gated admission door. Verify fresh same-owner password proof and current holder and target lifecycles, then record each signed consent id create-only before release. Unknown persistence outcomes return no consent and never retry automatically. Only the auth mint writer receives consent persistence authority. Private result serving remains unavailable.
-
Allow harness-less interactive joins on required-events spaces using the signed-in cli actor and native bearer renewal. Keep required event publishing on harness-hosting launches and preserve user-auth credential and channel boundaries.
-
Managers using a delegated runtime now refuse caller-supplied persona
configoverrides before looking up or reading the requested host path.resolve-agentandspawnreturn the samefailed-preconditionmessage for every path shape. DirectManager.startAgentcalls share the refusal. Select a named catalog persona instead. Locally executing managers and validated resolved-manifest resources retain their behavior.This changes a previously accepted launch option and ships as a pre-1.0 minor release. Upgrade the Manager to apply the guard. No auth-service change is required.
-
Report the answering Manager's host name and running package version in verified status. Export the ManagerStatus type and keep both advisory fields optional for older status payloads.
What's Changed
- feat(auth): issue host-held private tool-result consents by @davidfarah2003 in #4157
- feat(core): publish the process's own start in presence by @davidfarah2003 in #4056
- fix(manager): refuse delegated persona config path overrides by @davidfarah2003 in #4160
- fix(workspace): preserve explicit TLS in the seam census by @davidfarah2003 in #4163
- feat(manager): report answering host and running version in status by @davidfarah2003 in #4161
- test(manager): census the reap callsites by the method each sits in by @davidfarah2003 in #4164
- fix(workspace): retry a Windows record rename refused by a held file by @davidfarah2003 in #4172
- fix(cli): support persistent user-auth join without a harness by @davidfarah2003 in #4171
Full Changelog: v0.87.0...v0.88.0