Skip to content

v0.165.0

Choose a tag to compare

@davidfarah-dev davidfarah-dev released this 16 Nov 20:33
c1baecf

Install or update: npm i -g cotal-ai@0.165.0

Restart running Cotal processes and agent sessions to use the new code.

What changed

  • The owner of a Claude agent launched in a permission mode that asks can now approve or deny its permission prompts from another session, while Claude's own dialog keeps working.
  • Correct contract validation for admitted JSON Schema 2020-12 references and evaluated annotations.
  • Agent files now refuse cwd and worktree frontmatter instead of silently ignoring the requested directory.
  • Retain and verify a Linux migration's Node executable beside the existing native package generation, binding both in the maintenance resume document under the root and installation locks.
  • Staged updates now remove abandoned staging folders and finished transactions while keeping all execution generations.
  • Daemon login and setup now report invalid provider URLs as usage refusals without echoing or recording the rejected URL.
  • Keep a manually reinstalled CLI usable when another account's old generation store is unreadable.
  • Read the newest chat messages across a channel family without listing every concrete channel.
  • A channel post that mentions an agent who may not read the channel no longer drops that mention silently.
  • Pin @nats-io/nkeys to 2.0.3.
  • An authenticated seat whose DM durable is gone after a broker outage or restore now says so.
  • A refusal for a missing required property names the property again, for example must have required property 'windowMs'.
  • Add a retained maintenance-lock check and pre-stop controller identity observation for migration hosts.
  • Protect daemon state inside a redirected Cotal home from being used as a project folder.
  • The terminal app can open a managed agent's live terminal in its middle column and type into it.
  • The Claude Code plugin no longer rewrites a cotal_connect call to add the session.
  • Report harness work timestamps across the Claude Code, Codex, Hermes, OpenCode and pi connectors.
  • Pause automatic redelivery after a Codex message has failed three turns.
  • A Jcode seat no longer reports done for a manager turn its model never received.
  • Provider HTTP 4xx readiness refusals now report a client-error category instead of an unknown startup failure.
  • Report a self-update refused before any change as a refusal instead of an unknown outcome.
  • An attached terminal now reports that the agent exited when the agent's own process ends, instead of reporting that it was stopped.
  • Restore named inspection, model-pin audits and helper shutdown for managed static control sessions on their holding manager.
  • Stop unfinished legacy dashboard delete uploads after ten seconds without changing the channel.
Every change in full
  • The owner of a Claude agent launched in a permission mode that asks can now approve or deny its permission prompts from another session, while Claude's own dialog keeps working.

    The first answer applies, and a denial's note reaches Claude as the reason. The connector holds each prompt on Claude's PermissionRequest hook and keeps one record per prompt in the new cotal_permissions_<space> bucket, which space setup creates and a restore recreates empty. An owner's interactive principal reads the records by binding its own lifecycle's perm_ pull consumer, which a provisioner opens with CotalEndpoint.openPermissionReader; no principal can create a consumer on the bucket. Answers ride the new cotal.<space>.perm.<agentOwner>.<agentActor>.<runtimeId>.<owner>.<actor> rail to the one process that holds the prompt, and only the owner's interactive principals may publish there, so no agent's credential can answer its own prompt or a sibling's. A Yes at the terminal settles only prompts of the scope that ran it, so a background subagent's prompt survives the main thread's turn. CotalEndpoint gains openPermissionHolder, openPermissionReader, watchPermissions and answerPermission, and the approval presence condition can name the held prompt in request. Every Manager status.connectors row now reports permissionRequests, true only on a user-auth mesh, and the Manager cluster advances to revision 50. A static mint refuses to mark a credential interactive, and on an open mesh prompts stay with the terminal. See SPEC §8.2.

  • Correct contract validation for admitted JSON Schema 2020-12 references and evaluated annotations.

    Instance validation now uses json-schema-library 11.6.16, while Ajv retains schema meta-validation.
    The synchronous validator exposes backend-neutral errors instead of Ajv metadata. Generated browser
    contract modules import the shared interpreter and must be regenerated with this release.

  • Agent files now refuse cwd and worktree frontmatter instead of silently ignoring the requested directory.
    Set the directory on the spawn request with --cwd. Other unmodeled scalar hints still round-trip through meta.

  • Retain and verify a Linux migration's Node executable beside the existing native package generation, binding both in the maintenance resume document under the root and installation locks. This adds no public migration or activation command; controller preservation remains unsupported until its complete custody integration is available.

  • Staged updates now remove abandoned staging folders and finished transactions while keeping all execution generations.
    Cleanup runs under the installation's update lock when an update starts, after it succeeds, and when the daemon starts. It skips another account's store and reports removal failures without failing the update.

  • Daemon login and setup now report invalid provider URLs as usage refusals without echoing or recording the rejected URL. Validation runs before account selection or native setup effects, and help consistently describes auth URLs and discovery hostnames.

  • Keep a manually reinstalled CLI usable when another account's old generation store is unreadable.

    A plain start leaves inaccessible retired descriptors untouched and runs the installed version.

  • Read the newest chat messages across a channel family without listing every concrete channel.
    CotalEndpoint.multiChannelHistory(["events.>"], { limit }) uses one broker filter and returns
    the same subject-tagged, stream-ordered rows as the equivalent concrete-channel read.
    The family must be the only filter, and the broker still enforces the caller's existing grants.

  • A channel post that mentions an agent who may not read the channel no longer drops that mention silently. On an authenticated mesh the delivery daemon sends the post's sender a mention notice that names those agents, so the sender can reach them another way. The connectors show it as [mention notice from the delivery daemon], and Hermes runs it in its own notice:mention chat.

  • Pin @nats-io/nkeys to 2.0.3. Its 2.1.0 release no longer exposes the module the credential signer imports, so every fresh install and every update crashed at start with ERR_PACKAGE_PATH_NOT_EXPORTED.

  • An authenticated seat whose DM durable is gone after a broker outage or restore now says so. cotal_reconnect and the connectionIssue in cotal_connection_status name the missing durable and the recovery: restart the session, or respawn it if a manager launched it. Before, reconnect reported a bare "consumer not found" and offered retries that could never bring the durable back, and status gave no reason. The endpoint now fails that rebind with dm-durable-missing. Open-mesh seats still recreate their durable on reconnect.

  • A refusal for a missing required property names the property again, for example must have required property 'windowMs'.

  • Add a retained maintenance-lock check and pre-stop controller identity observation for migration hosts.

    The observation binds the controller operation, member launches, broker configuration and store identity without stopping services or admitting a migration. Controller preservation and restore commands remain unsupported.

  • Protect daemon state inside a redirected Cotal home from being used as a project folder.

    Space creation and startup now treat the daemon record directory and its descendants as control paths, while still allowing project folders beside the home's records.

  • The terminal app can open a managed agent's live terminal in its middle column and type into it.

    openTerminalSession() from @cotal-ai/workspace/attach opens one attach session for a caller that draws the terminal itself. It locates and pins the seat as attachSeat() does, honors expectedTarget, touches no process terminal, does not reconnect, and returns every refusal as a message. Its close() hands the session back to the manager.

  • The Claude Code plugin no longer rewrites a cotal_connect call to add the session. The server uses the one native session it has already bound.

  • Report harness work timestamps across the Claude Code, Codex, Hermes, OpenCode and pi connectors.

    Relay work events into the existing presence activeAt field so roster and operator surfaces can date the last reported work separately from heartbeats. No new wire field or progress verdict is added. Boundary-only hosts report less frequently than streaming hosts, and work age cannot distinguish a slow provider from a hung one.

  • Pause automatic redelivery after a Codex message has failed three turns.

    The first turn and two retries share one budget across broker redelivery while the message remains buffered. Exhausted messages stay unacknowledged and readable with cotal_inbox. The host log and seat status name them, and unrelated messages can still run. A host-process restart starts a new budget. Model output alone never acknowledges a message.

  • A Jcode seat no longer reports done for a manager turn its model never received.

    Jcode acknowledges a message before it checks whether the API connection is still processing an earlier one, and then refuses the busy send with Already processing a message. The acknowledgement marked the send's manager turns as delivered, so a refused turn was never offered again. It settled as done at the seat's next turn boundary, or waited out its deadline when no boundary came. When the refusal answers the connector's latest send, those turns now go back to waiting and are sent again once the running native turn ends. MeshAgent.unsurfaceTurns() hands run turns back this way; a once task's confirmed handoff is unchanged.

  • Provider HTTP 4xx readiness refusals now report a client-error category instead of an unknown startup failure. Existing authentication, payment, permission, rate-limit and model-refusal diagnostics keep their categories, and provider response text stays private.

  • Report a self-update refused before any change as a refusal instead of an unknown outcome.

    The initial execution check preserves its reason and owning install command, states that no changes were made, and exits with the boundary-refusal code. Failures after update work begins keep their existing outcome handling.

  • An attached terminal now reports that the agent exited when the agent's own process ends, instead of reporting that it was stopped.

    The manager ended every live attach session with target-despawn when it freed a seat, and its exit watcher runs before the session sees the process exit, so a natural exit reached the caller as a stop. A seat that exits on its own, including the last exit of a spent restart budget, now ends its sessions with process-exit. A stop, a reap and a failed restart still end them with target-despawn, and a child the manager stops because its parent exited is logged as reaped instead of as exiting on its own. The session also sends the seat's last output before its end frame, which the coalescing buffer used to drop when the exit watcher ended the session first.

  • Restore named inspection, model-pin audits and helper shutdown for managed static control sessions on their holding manager.

    Keep instance reads within the spawner's issued authority, preserve workflow starter ceilings without adding implicit reads to run-spawned helpers, and renew each seat with its original issued scope.

  • Stop unfinished legacy dashboard delete uploads after ten seconds without changing the channel.
    The body deadline returns HTTP 408 and closes the connection even when the caller keeps sending small chunks. The existing 8 KiB limit and read-only service refusal are unchanged.

What's Changed

Full Changelog: v0.164.18...v0.165.0