agents-can-communicate 0.4.2 → 0.4.4

package/README.md

@@ -65,6 +65,12 @@ then restart your clients from the project directory. In Codex, check `/plugins`
 review the current ACC definitions in `/hooks`; changed hooks may need fresh trust.
 [Getting started](docs/GETTING_STARTED.md) covers activation and preserved sandbox settings.
 
+For Codex live delivery on Apple Silicon macOS, installation also configures outgoing
+local socket access on Codex 0.153.4 or newer when using default workspace permissions.
+Custom policies are preserved. If its local service is missing, doctor gives the command
+`codex app-server daemon start`; then open a new Codex session. Doctor reports receiving
+channel state and outgoing permission configuration separately.
+
 Open two sessions and give them ordinary tasks, as above. Look for an agent discovering a
 peer, checking who is changing a file, asking about a shared dependency, or replying to a
 review request.
@@ -73,8 +79,8 @@ Run `acc doctor` from the project if a peer is missing. A directory containing A
 state, commonly your home directory, cannot be used as a workspace; start the client in a
 project directory. See [Troubleshooting](docs/TROUBLESHOOTING.md).
 
-Already using ACC? Follow the [upgrade guide](docs/UPGRADING.md), including the 0.4.0/0.4.1 →
-0.4.2 update and the data-format boundary when moving from 0.3.1.
+Already using ACC? Follow the [upgrade guide](docs/UPGRADING.md), including the 0.4.x →
+0.4.4 update and the data-format boundary when moving from 0.3.1.
 
 ## When messages arrive
 
@@ -136,8 +142,10 @@ One npm package. ACC needs no separate account, model API key, or hosted service
 
 Initial installation enables automatic updates. ACC downloads stable releases in the
 background and waits for active clients and ACC processes to exit before switching the
-runtime and refreshing integrations. Restart clients afterward and complete any requested
-hook or plugin trust review.
+runtime and refreshing integrations. When a verified Codex service needs a restart,
+`acc update` asks once, then completes maintenance in a separate process. Open clients
+disconnect; `acc doctor` reports progress and the result. See [update and recovery details](docs/UPGRADING.md#confirmed-client-service-maintenance).
+Restart or resume clients afterward and complete any requested hook or plugin trust review.
 
 For an immediate update:
 

package/bin/acc-maintenance-worker.mjs

@@ -0,0 +1,6 @@
+#!/usr/bin/env node
+import { runMaintenance } from "../node_modules/@agents-can-communicate/cli/src/managed-runtime/maintenance-worker.mjs";
+
+// This private entry has no workspace admission/lease and no inherited stdio.
+// Durable checkpoints remain available to the next acc update after a crash.
+await runMaintenance(process.argv[2], { jobId: process.argv[3] }).catch(() => { process.exitCode = 1; });

package/docs/ARCHITECTURE.md

@@ -15,8 +15,10 @@ flowchart LR
   T -->|reply or acknowledge| C
 ```
 
-ACC never starts, resumes, interrupts, supervises, or terminates the target client. A
-transport that requires owning that lifecycle is outside the product boundary.
+Message delivery never starts, resumes, interrupts, supervises, or terminates the target
+client. A transport that requires owning that lifecycle is outside the product boundary.
+Separately, explicit update maintenance can restart a verified client service after the
+user confirms the disconnection; it does not launch or assign agent tasks.
 
 ## Packages and dependency direction
 
@@ -90,8 +92,8 @@ turn.
 Claude Code Channel has installed-client evidence on 2.1.258 and 2.1.260; Codex
 LocalDaemon has it on 0.152.1 and 0.153.4. Both use a captured platform minimum,
 current probe and exact session handshake. Codex preserves the ordinary client
-launch and verifies its registered thread and workspace; ACC owns no vendor daemon
-lifecycle. Gemini CLI and Kimi Code have exact-version next-turn evidence only;
+launch and verifies its registered thread and workspace; native delivery owns no vendor
+daemon lifecycle. Gemini CLI and Kimi Code have exact-version next-turn evidence only;
 Grok and generic MCP use inbox polling.
 
 ## Storage and workspace identity
@@ -184,7 +186,12 @@ remains fenced and repairs forward, with the old active pointer retained but nor
 workspace admission unavailable until recovery completes. Native bindings cease holding
 after observed SessionEnd cleanup or confirmed process death; the vendor daemon may remain
 running. Unknown PIDs remain holds until lifecycle cleanup. Presence TTL, `acc finish`,
-and delivery off alone do not prove native lifecycle end. ACC never manages the daemon.
+and delivery off alone do not prove native lifecycle end. Normal background updates never
+restart a vendor daemon. An explicitly approved maintenance job can do so through the
+adapter lifecycle port: it waits for idle work, validates exact process identity, stops
+the service under the admission fence, refreshes integrations, and restores and verifies
+the service even after a refresh failure. Checkpoints and the detached worker live outside
+repositories. Approved crash recovery never blindly repeats a stop.
 
 Lock ownership never expires by age. Retained nonempty tombstones prevent delayed observers
 from reclaiming a successor. Under an acquired lock, maintenance removes historical

package/docs/CLI.md

@@ -232,7 +232,7 @@ external AI client. An addressed handoff requires acknowledgement; a room handof
 | `acc doctor` | `--home`, `--repair` |
 | `acc config init` | `--yes`, `--force` |
 | `acc config validate` | — |
-| `acc update` | `--check`, `--auto on\|off`, `--pin VERSION\|none`, `--apply` (alias) |
+| `acc update` | `--check`, `--auto on\|off`, `--pin VERSION\|none`, `--yes`, `--apply` (alias) |
 | `acc help` | — |
 | `acc version` | — |
 
@@ -248,8 +248,8 @@ effective policy off and prints the reason. Claude Code shell activation writes
 zsh PATH block and a shim that `exec`s the real client; `ACC_BYPASS=1` bypasses that
 activation. Codex LocalDaemon delivery uses recorded installation consent without changing
 ordinary launch arguments. Its opt-in remains active when shim variables are absent or
-bypassed; `acc install --adapter codex --delivery off` disables new native offers. ACC never
-starts or stops the vendor daemon. The install summary names each client's requested policy,
+bypassed; `acc install --adapter codex --delivery off` disables new native offers. Installation
+and message delivery do not start or stop the vendor daemon. The install summary names each client's requested policy,
 activation state and verified fallback. `doctor` separates protocol readiness, recorded
 consent and a live channel in the current workspace, with a next step for missing activation.
 A supported version or an installed plugin alone is not an active delivery channel.
@@ -281,8 +281,13 @@ holds. `finish`, presence TTL, and delivery off are not observed native end. Hoo
 wait for network work. `ACC_NO_UPDATE_CHECK=1` disables update networking and background
 scheduling.
 
-`acc update` requests the update immediately; it reports a pending update when a running or
-unidentified client prevents activation. `--check` only checks and cannot be combined with
+`acc update` requests the update immediately. If a verified Codex service blocks activation
+or runs an older version than the installed CLI, it asks once to restart that service.
+After confirmation, a detached worker waits for idle work and other ACC processes, refreshes
+integrations, restarts the service and verifies the result. Open clients disconnect; use
+`acc doctor` for progress and resume the clients afterward. `--yes` supplies explicit
+noninteractive restart consent. Without consent, or with unknown ownership, the update
+remains pending. See [maintenance limits and recovery](UPGRADING.md#confirmed-client-service-maintenance). `--check` only checks and cannot be combined with
 settings changes. `--auto off` disables background updates, and `--auto on` enables them.
 `--pin 0.4.0` holds an exact stable version; `--pin none` follows stable releases. A pin
 cannot downgrade the active runtime. The old `--apply` flag remains accepted.
@@ -290,7 +295,9 @@ cannot downgrade the active runtime. The old `--apply` flag remains accepted.
 Failed downloads keep the working runtime. A failed integration refresh exits with code
 `4`, names the failed adapter and configuration error, and keeps workspace admission closed.
 Fix the reported configuration problem, then run `acc update` to finish it. `acc doctor`
-reports the update policy and pending notice. Native clients may still require hook trust
+reports the update policy and pending notice. During blocked activation, a current launcher
+returns `scope: update` and `workspaceInspection: unavailable_during_update` without opening
+workspace state; `doctor --repair` remains blocked. Native clients may still require hook trust
 or activation review. See [Upgrading](UPGRADING.md) for the initial 0.3.1 transition and
 recovery details.
 

package/docs/CONCEPTS.md

@@ -14,7 +14,8 @@ settings, clients, and checkouts. Neither is automatically in charge. Claude can
 for the endpoint shape; Codex can answer or decline under its own instructions.
 
 This resembles coordination among subagents, but the sessions were opened independently by
-the user. ACC never launches, assigns, supervises, or closes them.
+the user. ACC does not launch, assign or supervise their work. Separately, an explicit
+update can ask to restart a client service; this disconnects clients and requires user consent.
 
 ## Workspace, participant, and session
 

package/docs/CONFIGURATION.md

@@ -139,11 +139,37 @@ reports degraded reachability; it does not rewrite the installed consent.
 
 Codex LocalDaemon delivery separately requires macOS arm64, Codex 0.152.1 or newer, a
 current feature probe, and exact thread, canonical cwd, process, version and protocol
-checks. Its daemon must already be running; ACC never starts or stops it. Codex reads
+checks. Its daemon must already be running; installation and delivery do not start or stop it.
+Explicit update maintenance can restart a verified service after separate confirmation. Codex reads
 consent from the installation record, not a shell-shim variable. Unavailable or ineligible
 sessions retain durable inbox fallback. Use `acc install --adapter codex --delivery off`
 to stop new native offers; bypassing a shim does not disable that recorded opt-in.
 
+### Codex outgoing permissions
+
+Receiving a native message and sending from the agent's sandbox are separate operations.
+On Codex 0.153.4 or newer on macOS arm64, live opt-in also configures outgoing access
+for default workspace permissions. This happens even when the daemon is not yet available.
+Installation, its preview, and the interactive consent question disclose this change.
+
+ACC selects a permission profile named `acc-workspace`, extending `:workspace`. It grants
+write access to the ACC state directory and allows only the local ACC channel directory
+(`/tmp/acc-ch-<uid>`) and the Codex home control socket. The profile enables networking
+through `features.network_proxy = true`, with no external domains allowed. The proxy and
+socket grants must stay together: enabling networking without the proxy changes its scope.
+
+An existing legacy workspace-write configuration is migrated only when its sole writable
+root is ACC's state directory. Custom permission/configuration profiles, additional roots,
+inline settings and uncaptured clients are preserved and reported as unverified. ACC does
+not merge arbitrary security policies or verify overrides in an already running session.
+For a custom policy, grant the same state and socket access through the proxy in the
+client's effective workspace profile; do not combine it with legacy sandbox settings.
+
+Restart Codex after changing permissions. Explicit delivery `off` or uninstall restores
+the previous configuration only while every generated permission component is unchanged.
+If any component was edited or another setting depends on it, ACC preserves the entire
+bundle and reports it for review. Plugin registration can still be removed independently.
+
 ## Override local paths and identity
 
 Nothing in `acc.workspace.json` says where state is stored, and nothing there can — that is

package/docs/GETTING_STARTED.md

@@ -15,7 +15,7 @@ pair or session-bound ACC MCP tools. See [CLI ownership](CLI.md#coordinate-from-
 
 ACC requires macOS or Linux and Node.js 24 or newer.
 
-Already using ACC? Follow the [upgrade guide](UPGRADING.md) for the 0.4.0/0.4.1 → 0.4.2
+Already using ACC? Follow the [upgrade guide](UPGRADING.md) for the 0.4.x → 0.4.4
 update or the data-format boundary when upgrading from 0.3.1.
 
 ```bash
@@ -30,7 +30,9 @@ acc install
 Initial installation also enables automatic updates; reinstalling keeps an explicit opt-out.
 ACC downloads releases in the background and
 refreshes its runtime and skills when active clients have left. Use `acc update` for an
-immediate update, or `acc update --auto off` to disable background updates. See
+immediate update; an eligible Codex service restart asks for one confirmation. ACC then
+handles maintenance and reports progress in `acc doctor`; clients disconnect and can be
+resumed afterward. Use `acc update --auto off` to disable background updates. See
 [update controls](UPGRADING.md#automatic-updates-after-installation).
 
 The installer connects only the supported clients it finds. Open a new terminal and
@@ -39,8 +41,12 @@ printed by the installer. In Codex, use `/plugins` to check ACC is enabled, then
 to review each ACC hook and enable/trust its current definition if needed. Restart the
 session after that review; changed hook definitions may require trust again.
 
-If the installer preserved your existing Codex sandbox settings, verify the named ACC
-state directory is in `sandbox_workspace_write.writable_roots` in the config it identifies.
+For Codex live delivery, follow the outgoing-permission and local-service instructions
+from install/doctor, then start a new session. Default workspace permissions can be
+configured automatically on Codex 0.153.4 or newer on macOS arm64. Custom settings are
+preserved; see [outgoing permissions](CONFIGURATION.md#codex-outgoing-permissions).
+With legacy sandbox settings, the named ACC state directory must also be in
+`sandbox_workspace_write.writable_roots` in the config the installer identifies.
 ACC keeps those user settings unchanged. Installed files alone do not establish that hooks
 are active; `acc doctor` leaves current readiness unverified and directs you to Codex.
 

package/docs/HOW_IT_WORKS.md

@@ -112,7 +112,8 @@ All recipients have the same durable record, but adapters expose different accel
   to an independently opened thread. It is experimental, off by default, and can
   spend tokens. Messages wait for a running turn to finish; a daemon-retained
   thread can receive them after its terminal exits. ACC adds no launch arguments
-  and does not manage the vendor daemon.
+  and does not manage the vendor daemon during message delivery. Separately,
+  [confirmed update maintenance](UPGRADING.md#confirmed-client-service-maintenance) can restart it.
 
 Grok, generic MCP, unsupported versions and uncaptured platforms use inbox polling.
 [Capabilities](CAPABILITIES.md) lists evidence and fallback.

package/docs/PROTOCOL.md

@@ -199,6 +199,10 @@ peer body into diagnostics.
 Receipt `offered` is committed only after the transport accepts bytes. A failed attempt
 leaves the receipt queued.
 
+`transport_permission_denied` means the sender's OS or sandbox refused local transport
+access (`EPERM` or `EACCES`). It is distinct from `recipient_unavailable` and remains a
+failed offer with a queued receipt; raw OS error strings are not persisted.
+
 ## Inbox, reply, and acknowledgement
 
 Without an id, public `inbox` lists bounded summary pages for unresolved messages owned

package/docs/RELEASING.md

@@ -1,7 +1,7 @@
 # Releasing
 
 Use this procedure to build one auditable npm artifact, verify that exact tarball, and keep
-its evidence tied to the commit that supplied its bytes. The package is currently `0.4.2`;
+its evidence tied to the commit that supplied its bytes. The package is currently `0.4.4`;
 the commands derive the version from `package.json` so the filename cannot drift.
 
 ```mermaid

package/docs/SECURITY_MODEL.md

@@ -24,9 +24,10 @@ graph LR
   H["human authority"] --> C
 ```
 
-ACC does not read raw transcripts, relay permission approvals, or start target clients. A
-native delivery path may only offer an attributed peer envelope to an already-running,
-user-owned session.
+ACC does not read raw transcripts or relay permission approvals. A native delivery path
+may only offer an attributed peer envelope to an already-running, user-owned session.
+Confirmed update maintenance is a separate service restart operation; a peer message or
+live-delivery opt-in does not authorize it.
 
 ## Peer-content boundary
 
@@ -79,6 +80,13 @@ consent before offers. A loaded daemon thread can receive messages after its TUI
 exits. Delivery off and uninstall prevent new Codex submissions; a submission
 already accepted by the vendor queue cannot be withdrawn.
 
+On captured Codex/macOS configurations, live opt-in also grants outgoing access to ACC's
+state and local Unix sockets through a deny-by-default network proxy. Custom permission
+policies remain user-owned. Selection, proxy and grants are restored together only while
+unchanged; edited or newly referenced settings remain intact. See
+[Codex outgoing permissions](CONFIGURATION.md#codex-outgoing-permissions). Configuration
+readiness does not prove that an active session's overrides permit a live offer.
+
 ## Claims
 
 CLI claims default to advisory. Guarded enforcement must be requested explicitly and
@@ -115,8 +123,14 @@ author as a software-supply trust boundary; they do not establish that package c
 
 ACC process leases hold activation until confirmed exit. Native bindings hold until observed
 SessionEnd cleanup or confirmed process death; unknown PIDs remain conservative holds.
-`acc finish`, presence TTL, and delivery off do not establish native lifecycle end. ACC does
-not manage the vendor daemon.
+`acc finish`, presence TTL, and delivery off do not establish native lifecycle end.
+Normal installation and message delivery do not manage vendor services. Explicit
+`acc update` maintenance requires one separate confirmation (or `--yes`) for the recorded
+candidate and verified service identity. The detached worker retains that approval for
+recovery, rechecks PID/start time, executable, socket, versions and idle state, and preserves
+unrelated or unidentified process holds. The vendor exposes no atomic turn-drain operation:
+a turn arriving between the final check and stop can be interrupted. See
+[confirmed maintenance](UPGRADING.md#confirmed-client-service-maintenance).
 
 A failed download leaves the active runtime available. A partial integration refresh retains
 the old active pointer but fences normal workspace admission in `activating`; it does not

package/docs/TROUBLESHOOTING.md

@@ -100,6 +100,20 @@ ambiguous recipients or failed identity checks retain durable inbox access.
 An interactive install can save consent in either case. ACC preserves it through a temporary
 outage and does not start the daemon for you.
 
+On a supported Codex CLI, a missing daemon can be started with
+`codex app-server daemon start`; open a new Codex session afterward. Doctor includes this
+command when it detects the missing endpoint.
+
+If a reply stays queued with `transport_permission_denied`, the sender's permissions
+blocked local transport. This is distinct from an unavailable recipient. The message was
+recorded successfully; the error does not mean it was read or acknowledged.
+On Codex 0.153.4 or newer on macOS arm64, rerun `acc install --adapter codex` with existing
+live consent (or add `--delivery actionable` to opt in), then start a new session.
+Doctor's `outgoingDelivery` reports the installed permission configuration separately
+from `nativeDelivery.runtime`: an active receiving channel does not establish outgoing
+access. Custom policies and active-session overrides remain unverified; inspect the config
+path doctor names and follow [outgoing permissions](CONFIGURATION.md#codex-outgoing-permissions).
+
 Check `acc doctor --json` and `acc status --json` while both clients are open. If policy is
 `off`, opt in with `acc install --adapter codex --delivery actionable` (or select another
 adapter). This can spend model tokens. If policy is enabled but runtime is `waiting` and
@@ -153,8 +167,9 @@ definitions need review, and a trusted hook can still be disabled.
 
 `acc doctor` reports installed files separately from hook readiness, which it leaves
 unverified. A saved trust record cannot prove current activation. If installation preserved
-your own sandbox configuration, doctor also names the ACC state directory whose access
-you should check in `sandbox_workspace_write.writable_roots`.
+your own legacy sandbox configuration, doctor also names the ACC state directory whose
+access you should check in `sandbox_workspace_write.writable_roots`. Live delivery requires
+local socket permissions as well; a writable state directory alone is insufficient.
 
 ## Gemini does not guard a write
 
@@ -225,8 +240,11 @@ Run `acc doctor` to see the update policy and pending notice. ACC process leases
 persistent MCP servers, require confirmed process exit. Native bindings clear on observed
 SessionEnd or confirmed process death; a vendor daemon may remain alive after SessionEnd.
 Unknown PIDs remain holds until lifecycle cleanup. Close the relevant client sessions and
-ACC processes; `finish`, presence TTL, and delivery off do not prove native end. ACC never
-manages the daemon or expires safety holds merely by elapsed time.
+ACC processes; `finish`, presence TTL, and delivery off do not prove native end.
+`acc update` can offer a confirmed restart of an eligible Codex service. Unknown or
+unrelated holds still require lifecycle cleanup or confirmed process exit; safety holds
+do not expire merely by elapsed time. See
+[maintenance and recovery](UPGRADING.md#confirmed-client-service-maintenance).
 
 Use `acc update` to retry a failed download or finish an interrupted integration refresh.
 A download failure keeps the working version. A partial integration refresh blocks

package/docs/UPGRADING.md

@@ -1,13 +1,14 @@
-# Upgrading to 0.4.2
+# Upgrading to 0.4.4
 
-## From 0.4.1 or 0.4.0
+## From 0.4.3, 0.4.2, 0.4.1 or 0.4.0
 
-This patch keeps the existing workspace data format. It makes installation and delivery
-diagnostics clearer, records the last native binding attempt per session, and restores
-hook participation after detaching a solo session without restarting the conversation.
-It also includes the 0.4.1 Grok, reinstall-preference and workspace-warning fixes.
+This patch keeps the existing workspace data format. It adds confirmed service maintenance
+to the updater, preserves native delivery setup when readiness probes are unavailable,
+and names the actual processes blocking activation. It includes the previous 0.4.x
+outgoing sandbox permissions, delivery diagnostics, session recovery and integration fixes.
 
-Close participating clients and persistent ACC MCP processes, then run:
+Run the update command; it can offer a confirmed restart for an eligible Codex service.
+Other active clients and persistent ACC MCP processes still need to finish before activation:
 
 ```bash
 acc update
@@ -15,10 +16,15 @@ acc version
 acc doctor
 ```
 
-After publication, `acc version` should report 0.4.2. If a pin keeps an older version,
-select 0.4.2 or clear it first. A managed update refreshes installed integrations and
+After publication, `acc version` should report 0.4.4. If a pin keeps an older version,
+select 0.4.4 or clear it first. A managed update refreshes installed integrations and
 skills; use the npm instructions below for unmanaged or pre-0.4 installations. Start
-clients again and complete any hook/trust review they request.
+clients again and complete any hook/trust review they request. With existing live consent,
+Codex 0.153.4 or newer on macOS arm64 receives local socket permissions when its workspace
+policy is default or contains only ACC's legacy state root. Custom policies are preserved
+and reported as unverified. See [outgoing permissions](CONFIGURATION.md#codex-outgoing-permissions).
+If doctor names a missing local service, run `codex app-server daemon start` before opening
+the new session.
 
 Run `acc doctor` in the project after the new clients have started (or submitted a normal
 turn). Its per-session lines now explain missing launch consent, an unidentified client
@@ -31,13 +37,52 @@ Claude admitted inbound Channels messages. See [delivery troubleshooting](TROUBL
 Upgrading preserves delivery consent. If doctor reports native delivery off and you want
 automatic peer requests, use `acc install --adapter codex --delivery actionable` (or the
 relevant adapter); this can spend model tokens. Codex can save that consent before its
-local service/session becomes available. ACC does not start the vendor daemon, and it
+local service/session becomes available. Installation does not start the vendor daemon; ACC
 keeps durable inbox access when no verified live channel is bound.
 
 In Grok, public status supplies the session's own CLI arguments through the next tool
 hook. Grok still uses explicit inbox reads; this patch adds no external wake or guards.
 Start clients in a project directory, rather than a home directory containing ACC state.
 
+## Confirmed client service maintenance
+
+On macOS arm64, `acc update` can ask once to restart a verified Codex service that blocks
+activation or runs a different version from the installed CLI. The captured maintenance
+contract uses Codex CLI 0.154.0 and its `pid` backend, with compatible commands and protocol
+checked again at runtime. The installed CLI and managed executable must already match;
+ACC does not replace vendor binaries or install an operating-system service.
+
+After confirmation, a detached ACC worker waits up to 15 minutes for idle Codex turns,
+empty queues and other ACC processes to exit. It rechecks the approved candidate, settings,
+PID/start time, executable, socket ownership and versions before stopping the service.
+It refreshes integrations, starts the service again and verifies the result. If refreshing
+integrations fails, it still restores the service and reports the incomplete update.
+A later update worker can resume an already approved recovery without another question.
+`acc doctor --json` exposes `update.maintenance`; ordinary `acc doctor` describes its state.
+A current launcher can use the newer management reader while the old runtime is active.
+When admission is blocked, doctor returns an update-only report without inspecting the
+workspace or repairing it. Older launchers gain this reader after activation, or through
+the one-time launcher bootstrap described below.
+
+Open clients disconnect. Resume them afterward and complete any client-owned hook trust
+review. Codex has no atomic idle-check-and-stop operation: a new turn arriving during the
+final check can be interrupted. ACC does not promise that client UIs reconnect themselves
+or that an interrupted turn continues automatically. Unknown ownership, incompatible
+service layouts and unrelated active processes remain visible blockers.
+
+For an unattended command, `acc update --yes` explicitly consents to the same restart.
+`acc update --check` stays read-only. Background discovery never grants restart consent.
+Changing the candidate or pin before the stop cancels that approval; idle-wait expiration
+also leaves the service untouched. Delivery consent and automatic-update opt-outs survive
+an update even when a native service or feature probe is temporarily unavailable.
+
+An old installation can already be stuck with both a pre-0.4.4 pending runtime and the
+old updater that waits indefinitely. That code cannot discover this fix. Bootstrap the
+new launcher once with `npm install --global agents-can-communicate@0.4.4`, then run
+`acc update`. The new launcher stages its verified runtime and retires only an exactly
+identified obsolete ACC background updater while no integrations are being written.
+This does not terminate an unrelated client or bypass its lifetime hold.
+
 ## From 0.3.1
 
 Upgrade all ACC installations participating in a workspace together, then restart their
@@ -59,7 +104,7 @@ restores access; deleting or editing the record is not a remedy.
 2. Install the released package, then refresh the client integrations:
 
    ```bash
-   npm install --global agents-can-communicate@0.4.2
+   npm install --global agents-can-communicate@0.4.4
    acc version
    acc install
    ```
@@ -99,7 +144,8 @@ confirmed process exit. Native bindings hold until observed client SessionEnd cl
 confirmed process death; the vendor daemon can remain running after that lifecycle event.
 Unknown PIDs remain conservative holds until lifecycle cleanup. `acc finish`, presence TTL,
 and delivery off alone do not prove native end. Close the relevant client sessions and
-persistent ACC processes to release holds; ACC does not manage the vendor daemon.
+persistent ACC processes to release holds, or accept the eligible Codex service maintenance
+offer in `acc update`. Background updates never request fresh restart consent.
 Hooks never wait for a network download. If integration refresh temporarily prevents
 coordination, a hook lets the client continue; its next genuine user turn can restore a
 missing binding.
@@ -109,7 +155,7 @@ acc update                    # download and apply, or report what is keeping it
 acc update --check            # check without installing or changing update settings
 acc update --auto off         # disable background updates
 acc update --auto on          # enable them again
-acc update --pin 0.4.2        # stay on this exact stable version
+acc update --pin 0.4.4        # stay on this exact stable version
 acc update --pin none         # follow stable releases again
 ```
 

package/docs/WHY_ACC.md

@@ -46,7 +46,7 @@ actionable before two sessions collide.
 ## Choose another layer when
 
 Choose a managed runtime if you want the system to create agents, assign execution state,
-select models, spend token budgets, or control process lifecycle. Choose a tracker when
+select models, spend token budgets, or control ongoing agent execution. Choose a tracker when
 you need organizational planning. Choose a hosted service when participants must
 coordinate across machines.
 

package/node_modules/@agents-can-communicate/adapter-claude-code/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agents-can-communicate/adapter-claude-code",
-  "version": "0.4.2",
+  "version": "0.4.4",
   "private": true,
   "type": "module",
   "exports": {

package/node_modules/@agents-can-communicate/adapter-claude-code/src/channel.mjs

@@ -1,8 +1,8 @@
 import { randomBytes, timingSafeEqual } from "node:crypto";
 import { chmodSync, existsSync, mkdirSync, statSync, unlinkSync, writeFileSync } from "node:fs";
 import net from "node:net";
-import os from "node:os";
 import path from "node:path";
+import { channelSocketDirectory } from "@agents-can-communicate/adapter-sdk";
 
 // The production ACC Channel: a stdio MCP server Claude Code spawns, plus a
 // session-scoped Unix endpoint the delivery router reaches. One envelope on the
@@ -39,8 +39,6 @@ const shortId = () => `endpoint_${randomBytes(16).toString("hex")}`;
 // while the registration - discoverable by the hook-resolved pid - stays under
 // the workspace. The registration records the socket's absolute path, so the
 // two are decoupled.
-const defaultSocketDir = () => path.join(os.tmpdir(),
-  `acc-ch-${typeof process.getuid === "function" ? process.getuid() : "u"}`);
 
 /**
  * Compose a Channel over an endpoint directory and injected ACC callbacks.
@@ -49,7 +47,7 @@ const defaultSocketDir = () => path.join(os.tmpdir(),
  * ones backed by the real conversation service; a test supplies fakes. Neither
  * the socket path nor the nonce leaves through a return value or a log line.
  */
-export function createAccChannel({ endpointDir, socketDir = defaultSocketDir(), clientPid,
+export function createAccChannel({ endpointDir, socketDir = channelSocketDirectory(), clientPid,
   protocolContract = PROTOCOL_CONTRACT, modes = CHANNEL_MODES, leaseMs = 60_000, routeReply,
   routeAck, refreshBinding = null, observe = () => {},
   clock = () => new Date().toISOString(), write, now = Date.now }) {

package/node_modules/@agents-can-communicate/adapter-claude-code/src/native-delivery.mjs

@@ -206,7 +206,9 @@ function sendEnvelope({ record, message, binding, connect, timeoutMs, rejected }
     const finish = value => { if (settled) return; settled = true; clearTimeout(timer);
       socket.destroy(); resolve(value); };
     const timer = setTimeout(() => finish(rejected("transport_error")), timeoutMs);
-    socket.once("error", () => finish(rejected("recipient_unavailable")));
+    socket.once("error", error => finish(rejected(
+      ["EPERM", "EACCES"].includes(error.code)
+        ? "transport_permission_denied" : "recipient_unavailable")));
     socket.once("connect", () => {
       socket.write(`${JSON.stringify(envelope)}\n`);
       let buffer = "";

package/node_modules/@agents-can-communicate/adapter-codex/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agents-can-communicate/adapter-codex",
-  "version": "0.4.2",
+  "version": "0.4.4",
   "private": true,
   "type": "module",
   "exports": {

package/node_modules/@agents-can-communicate/adapter-codex/src/adapter.mjs

@@ -2,6 +2,8 @@ import { defineAdapter, projectContext, projectContextResult }
   from "@agents-can-communicate/adapter-sdk";
 import { probeNativeDelivery, planNativeActivation, bindNativeSession, refreshNativeSession, retireNativeSession, offerMessage } from "./native-delivery.mjs";
 import certification from "../certification.json" with { type: "json" };
+import { createCodexMaintenance } from "./maintenance.mjs";
+export { sameMaintenanceIdentity } from "./maintenance.mjs";
 
 import { PROTOCOL_CONTRACT } from "./app-server-client.mjs";
 import { allowOutcome, denyOutcome, injectOutcome, normalizeCodexHook }
@@ -16,8 +18,9 @@ export const CODEX_DELIVERY_FALLBACK = Object.freeze({
   diagnostic: "Codex native delivery requires codex-cli 0.152.1 or newer on darwin-arm64, "
     + "recorded recipient consent and a reachable LocalDaemon session with exact thread, cwd, "
     + "process, version and protocol verification. Embedded or unreachable sessions retain "
-    + "durable messages. ACC does not start, restart or stop the vendor daemon and adds no "
-    + "launch arguments; fallback is exact-certified next-turn delivery or acc inbox",
+    + "durable messages. Native delivery does not start, restart or stop the vendor daemon and adds no "
+    + "launch arguments; fallback is exact-certified next-turn delivery or acc inbox. "
+    + "Explicitly confirmed acc update maintenance has a separate daemon restart check",
 });
 
 /**
@@ -61,6 +64,7 @@ export function createCodexAdapter() {
     },
     probeNativeDelivery, planNativeActivation, bindNativeSession,
     refreshNativeSession, retireNativeSession, offerMessage,
+    ...createCodexMaintenance(),
     startSession: async () => ({ ok: true, changes: [], diagnostics: [] }),
     endSession: async () => ({ ok: true, changes: [], diagnostics: [] }),
     guardWrite: async () => ({ ok: true, changes: [], diagnostics: [] }),