@ours.network/fleet 0.11.0 → 0.11.1

package/dist/cli.js

@@ -197,6 +197,8 @@ cOpt(program.command('config').description('validate + print the merged plan (no
                 console.log(`  watch:    ${w.watch.join(', ')}`);
                 if (w.promptFile)
                     console.log(`  focus:    ${w.promptFile}`);
+                if (w.isolation)
+                    console.log(`  isolation: ${JSON.stringify(w.isolation)}`);
             }
         }
     }

package/dist/docs.d.ts

@@ -4,7 +4,7 @@
  * Keep this concise enough to place directly in an agent context. Unlike
  * Commander's per-command help, this describes how the pieces compose.
  */
-export declare const AI_DOCS = "# ours-fleet reference\n\nours-fleet runs persistent or temporary, identity-bound AI roles. A role selects\na harness independently from its session backend:\n\n- harness: `claude-code` or `codex`\n- session: `tmux` (default) or `acp`\n- lifetime: permanent (supervised, restartable) or `spawn --temp`\n\n## Discover and validate\n\n```sh\nours-fleet docs                         # this complete reference (`man` is an alias)\nours-fleet help <command>               # exact flags for one command\nours-fleet config [-c FILE]             # validate and print the merged plan; no changes\nours-fleet doctor [-c FILE] [--harness codex|claude-code]\n```\n\nDefault configuration is `~/fleet.yaml` plus sorted `~/fleet.d/*.yaml` role\ndrop-ins. An explicit `-c FILE` replaces `~/fleet.yaml`; fleet.d still adds\nroles. Validate with `config` and `doctor` before starting or restarting.\n\n## Lifecycle and console commands\n\n```sh\nours-fleet init\nours-fleet up|down [Name...]\nours-fleet restart [Name...]            # preserve/resume harness context\nours-fleet force-restart [Name...]      # fresh context; briefing is reloaded\nours-fleet ls\nours-fleet status|peek|attach|logs Name\nours-fleet logs -f Name\nours-fleet send Name \"prompt\"\nours-fleet send Name --key Enter        # tmux only\nours-fleet rm Name\nours-fleet watchdog-report <name> [run-id] [--list] [--json]\nours-fleet watchdog-run <name>\n```\n\n`peek`, `attach`, and text `send` work with tmux and ACP. ACP attachment\nalso accepts `/permit <permission-id> <option-id>`, `/interrupt`, and\n`/detach`. Raw `--key` input is tmux-only.\n\n## Local web console\n\nThe npm package includes the web console; installed users do not clone the repo\nor run `npm run build`:\n\n```sh\nnpm i -g @ours.network/fleet\nours-fleet init\nours-fleet doctor\nours-fleet web                         # install/update service, start, pair browser\n```\n\nThe normal command uses stable `http://127.0.0.1:49271/`, installs an\nowner-level systemd user service (Linux) or LaunchAgent (macOS), and opens a\nfive-minute one-use pairing link in the local browser. After pairing, bookmark\nthe plain URL or install the PWA. To pair a new, signed-out, or revoked browser,\nrun `ours-fleet web open`.\n\n```sh\nours-fleet web status\nours-fleet web start|stop|restart\nours-fleet web open\nours-fleet web revoke-all              # revoke every browser and active session\nours-fleet web uninstall\nours-fleet web serve --port 0 --no-open # isolated foreground/testing mode\n```\n\nThe console is intentionally IPv4-loopback-only. It has no LAN/Internet host,\nproxy, TLS, or remote-access mode. Do not expose port 49271 through a reverse\nproxy. Browser credentials are HttpOnly/SameSite, and `revoke-all` invalidates\nall trusted devices. Role creation offers harness-scoped known-model choices\nwhile still accepting a typed model ID; blank explicitly uses the selected\nharness's own default.\n\n## Spawn\n\n```sh\nours-fleet spawn [--temp] Name \\\n  --harness codex|claude-code --session tmux|acp \\\n  --mission \"one line\" --cwd /absolute/path --identity Identity \\\n  --coordinator Coordinator --model MODEL \\\n  --approval ask|allow|deny \\\n  --filesystem read-only|workspace|unrestricted \\\n  --unattended deny|wait \\\n  --bio-file /path/bio.md --persona-file /path/persona.md\n```\n\nPermanent spawn writes `~/fleet.d/Name.yaml` and starts a supervised role.\n`--temp` writes ephemeral state, starts a detached supervisor, and removes the\nrole after exit/reboot. Both lifetimes support `--session acp`.\n\nCodex-specific spawn flags: `--sandbox`, `--permission-mode`, `--launcher`,\n`--profile`, `--search`, repeatable `--codex-config key=value`, repeatable\n`--add-dir`, and legacy `--monitor` (consent for the native Codex monitor,\nnot the `monitor.mode` wake-owner selector). Run `ours-fleet help spawn` for\nexact values.\n\n## fleet.yaml\n\n```yaml\nvars:\n  work_root: /home/me/work\nstart_stagger_ms: 0\ndefaults:\n  harness: codex\n  session: acp\n  model: gpt-model-id\n  permissions:\n    approval: ask\n    filesystem: workspace\n    unattended: deny\n  monitor:\n    mode: fleet                          # fleet (default) | native\nroles:\n  Coordinator:\n    harness: codex\n    session: acp\n    identity: Coordinator\n    cwd: ${work_root}/project\n    mission: Coordinate work and delegate implementation.\n    model: gpt-model-id\n    permissions:\n      approval: ask\n      filesystem: workspace\n      unattended: deny\n    session_options:                    # advanced overrides; normally omit\n      # acp:\n      #   command: [/custom/codex-acp, --flag]\n      tmux:\n        boot_grace_ms: 10000\n    monitor:\n      mode: fleet                        # fleet supervisor | native harness monitor\n      interrupt: false                    # true cancels active work before every configured wake\n      wake_sources: [message_received, file_received, local_contact_request, pending_message]\n      batch_ms: 2000\n      inject: notification\n      turn_fail_threshold: 3\n    harness_options:\n      launcher: auto\n      sandbox: workspace-write\n      approval: on-request\n      search: false\n      profile: fleet\n      add_dirs: [/data/shared]\n      config:\n        model_reasoning_effort: high\n    bio: Public role card and when peers should engage it.\n    persona: Local operating contract, boundaries, and escalation policy.\n    briefing_file: /absolute/custom-briefing.md\n    coordinator: AnotherCoordinator\n    env:\n      KEY: value\n    oversee:\n      - { role: Worker, interval: 5m }\nwatchdogs:\n  nightwatch:                       # [A-Za-z0-9_-], must not collide with a role name\n    coordinator: FleetCoordinator   # required \u2014 where alerts go\n    # everything below is optional\n    enabled: true                   # default true; false = configured but never scheduled\n    interval: 10m                   # default 10m; 30s | 10m | 2h, minimum 1m\n    watch: [Alice, CodexReviewer]   # default: every role in the merged config\n    harness: claude-code            # default: defaults.harness\n    model: claude-fable-5           # default: same resolution rule roles use (resolveRoleModel)\n    session: acp                    # default: defaults.session\n    identity: Watchdog-nightwatch   # default: Watchdog-<name>\n    timeout: 5m                     # default 5m; a run past this is killed and recorded as error\n    keep_reports: 50                # default 50 reports retained per watchdog\n    alert_cooldown: 60m             # default 60m before the same finding alerts again\n    prompt_file: /abs/extra.md      # optional extra focus, APPENDED to the fixed contract\n```\n\nA watchdog observes and reports; it never restarts, stops, spawns, or removes a\nrole, answers a pending permission, edits a workspace, or approves anything on\nthe owner's behalf. `watchdogs:` may appear only in the base config\n(`~/fleet.yaml` or `-c FILE`), not in `~/fleet.d/*.yaml` drop-ins.\n\nRole values override defaults. `${name}` substitutes entries from `vars`.\nOther role fields include `max_tokens`, `autocompact_pct`, and `isolation`.\nUse README.md for the complete isolation policy and resource-cap schema.\n\n## Permissions\n\nPrefer the harness-neutral `permissions` block:\n\n- `approval: ask|allow|deny`: whether actions may request or receive approval\n- `filesystem: read-only|workspace|unrestricted`: filesystem intent\n- `unattended: deny|wait`: what ACP does when no console can answer a request\n\nThe backend translates this common intent. Harness-native settings in\n`harness_options` take precedence where supplied. Do not choose\n`allow`/`unrestricted`, Codex `never`/`danger-full-access`, or Claude\n`bypassPermissions` without explicit authorization.\n\n### Creation-time isolation\n\n`ours-fleet spawn --isolation-file <path>` supplies a role's sandbox policy at\ncreation, so the FIRST launch is already confined \u2014 a role that only gains\n`isolation:` on a later `up` ran unsandboxed until then.\n\nThe file holds exactly the `isolation:` mapping documented above and nothing\nelse \u2014 the same schema, validated by the same code, so a policy written here\ncannot mean something different from the identical block in fleet.yaml:\n\n```yaml\nnetwork: deny\nfs:\n  read: [/opt/reference]\nresources:\n  mem: 2G\n```\n\nInvalid files are rejected before anything is created: no config, no state\ndirectory, no identity reservation. Works for both permanent and `--temp` roles.\n\n### Never-prompt failure\n\nThe failure this section exists to prevent leaves no error message anywhere.\n\nAn unattended role has no console. When the harness needs a permission decision\nthere is nobody to ask, so the request is refused INSIDE the harness \u2014 no\nprompt, no error, no log line. The agent simply does less than its briefing told\nit to, reports success, and nothing distinguishes that from having done the\nwork. Two settings produce it:\n\n1. a permission mode that suppresses the prompt without granting the action\n   (Claude `dontAsk`, which is why neutral `allow` maps to\n   `bypassPermissions` instead); and\n2. `unattended: deny`, which refuses every request that reaches it.\n\n**Automatic decisions are now recorded.** Every permission request decided\nwithout a human emits a completed event into\n`~/.ours-fleet/agents/<Name>/.session-events.jsonl` carrying the decision,\nwhether policy or a person made it, the policy that produced it\n(`permissions.unattended=deny` vs `permissions.approval=deny`/`=allow`),\nthe reason, and the option selected. `ours-fleet peek` and `attach` render\nthem. Automatic denial asks for a one-shot rejection, never a standing one, so a\nsingle unattended refusal cannot disable a tool for the rest of the session.\n\nA role that can auto-deny logs one line at startup saying so.\n\nTo detect an under-permissioned role BEFORE it runs, use the capability floor\nbelow: `ours-fleet doctor` fails such a role rather than letting it discover\nthe problem silently at work.\n\n### The unattended capability floor\n\nAn unattended role has no console, so a permission request cannot be answered \u2014\nit is refused, silently, inside the harness. The agent then does less than it\nwas told to and reports no error. To make that visible before launch,\n`ours-fleet config` and `ours-fleet doctor` resolve each role's neutral\npermissions through its harness and check the result against a fixed floor:\n\n- `read-state` \u2014 read its briefing, ROUTINES.md, and WORKLOG.md\n- `write-state` \u2014 append its WORKLOG and its own state files\n- `messaging` \u2014 bind its identity, send and receive ours mail\n- `monitor` \u2014 arm and observe its mail monitor\n- `workspace-edit` \u2014 edit and test files in its working directory\n- `status-commands` \u2014 run the inspection commands its briefing prescribes\n\n`doctor` reports this per role as `unattended floor: <Role>`. A role with\n`unattended: deny` that cannot meet the floor FAILS doctor, because it will\ndeny those requests with nobody to see it; with `unattended: wait` it warns,\nbecause a human can still attach and answer.\n\nSecurity meaning: `approval: allow` maps to Claude's `bypassPermissions`,\nwhich genuinely permits the actions the role was authorized to take \u2014\n`dontAsk` only suppresses the prompt while still refusing the action. Nothing\nother than an explicit `allow` is elevated: `ask` stays on Claude's default\nmode and `deny` maps to `plan`. `allow` is therefore a real grant and\nrequires explicit authorization; per-role `isolation:` remains the outer\nboundary that a permission mode cannot cross.\n\nSee also: `spawn --approval/--filesystem/--unattended` set this intent at\ncreation, and `ours-fleet config` prints each role's neutral settings, their\nnative translation, and any warning \u2014 the same text `doctor` reports.\n\nClaude `harness_options`: `permission_mode` (default, acceptEdits, plan,\ndontAsk, bypassPermissions), `plugins`, `mem_palace`, and\n`mem_palace_midsession_autosave`.\n\nCodex `harness_options`: `launcher` (auto, ours-codex, codex), `sandbox`\n(read-only, workspace-write, danger-full-access), `approval` or\n`permission_mode` (untrusted, on-request, never), `profile`, `search`,\n`config`, `add_dirs`, and `monitor`.\n\n## ACP adapters\n\nThe maintained `@agentclientprotocol/codex-acp` and\n`@agentclientprotocol/claude-agent-acp` runtimes are bundled automatically as\noptional ours-fleet dependencies. The supervisor resolves their executable\nentrypoints internally, so default ACP roles do not depend on global PATH.\nThe maintained Claude adapter requires Node 22; tmux and Codex ACP continue to\nwork on the ours-fleet core minimum of Node 20.\n\nOverride an adapter only when necessary with `session_options.acp.command`\n(string or argv list). If optional dependencies were deliberately omitted,\nours-fleet falls back to a compatible globally installed `codex-acp` or\n`claude-agent-acp`. `ours-fleet doctor -c FILE` verifies the resolved adapter.\n\n## Reliable mail wake\n\n`monitor.mode` selects exactly one wake owner:\n\n- `fleet` (default): the ours-fleet supervisor consumes body-free daemon\n  events and advances its durable cursor only after delivery is accepted. ACP\n  uses live steering when supported and falls back to structured\n  `session/prompt`; tmux uses verified console injection.\n- `native`: ours-fleet starts no supervisor monitor; the generated briefing\n  instructs Claude Code or Codex to arm its harness-native wake mechanism.\n\nSet `monitor.interrupt: true` in fleet mode to cancel active work before every\nconfigured wake. The policy is content-blind because the supervisor cannot\ninspect encrypted message bodies. Message bodies are released only when the\nrole calls the ours `get_messages` tool.\n\nLegacy `monitor.enabled: true|false` remains accepted as an alias for\n`mode: fleet|native`; use `mode` in new configuration. Codex's separate\n`harness_options.monitor: true` is native-monitor consent, not monitor-owner\nselection.\nInspect `ours-fleet status Name`, `peek Name`, role logs, and\n`~/.ours-fleet/agents/Name/.monitor-status` when diagnosing delivery.\n\n## Stable config and YAML migration\n\n`ours-fleet config --json` emits schemaVersion 1 resolved plans. Environment\nvalues and mission/persona/bio bodies are withheld; environment keys are sorted\nand values are marked redacted. Additive fields may appear in schema 1, while a\nremoval or semantic reuse requires a new schema version.\n\nYAML parsing always rejects duplicate keys. The current default\n`--yaml-mode compat` warns with file/line/column for anchors, aliases, explicit\ntags, non-scalar keys, and multiple documents. Use `--yaml-mode strict` in CI\nnow; strict becomes the next-major default and compat is the temporary migration\nescape hatch.\n\n## Bounded worklogs, auth proxy, and model recovery\n\nAn optional `worklog: { max_kb, keep_tail_kb, max_archives }` policy rotates a\nstable snapshot at fleet-owned lifecycle points. Concurrent changes defer\nrotation. Archives remain beside WORKLOG.md with the same sensitive-state\nboundary; retention deletes only recognized fleet archive names.\n\n`auth_proxy: { kind: anthropic, base_url, required, health_url }` is Claude-only\nand loopback-only. Fleet injects only ANTHROPIC_BASE_URL and doctor rejects\ncredential env keys. The privileged reference companion is\n`contrib/anthropic-auth-proxy.mjs`; deploy it separately as a dedicated account\nwith a 0600 token file and per-role listener access. Fleet never installs it or\nreads its credential.\n\n`model_chain` is an ordered authorization list and its first entry must equal\n`model`. Only sustained high-confidence entitlement/quota 429 evidence advances\none entry. Transient 429, overload, auth, policy, and unknown errors never\ndown-shift. Runtime state is atomic in .model-recovery.json; exhaustion is\nfail-closed and held down. Change the declared chain/model and restart to\nreconcile explicitly; no chain preserves detection-only behavior.\n";
+export declare const AI_DOCS = "# ours-fleet reference\n\nours-fleet runs persistent or temporary, identity-bound AI roles. A role selects\na harness independently from its session backend:\n\n- harness: `claude-code` or `codex`\n- session: `tmux` (default) or `acp`\n- lifetime: permanent (supervised, restartable) or `spawn --temp`\n\n## Discover and validate\n\n```sh\nours-fleet docs                         # this complete reference (`man` is an alias)\nours-fleet help <command>               # exact flags for one command\nours-fleet config [-c FILE]             # validate and print the merged plan; no changes\nours-fleet doctor [-c FILE] [--harness codex|claude-code]\n```\n\nDefault configuration is `~/fleet.yaml` plus sorted `~/fleet.d/*.yaml` role\ndrop-ins. An explicit `-c FILE` replaces `~/fleet.yaml`; fleet.d still adds\nroles. Validate with `config` and `doctor` before starting or restarting.\n\n## Lifecycle and console commands\n\n```sh\nours-fleet init\nours-fleet up|down [Name...]\nours-fleet restart [Name...]            # preserve/resume harness context\nours-fleet force-restart [Name...]      # fresh context; briefing is reloaded\nours-fleet ls\nours-fleet status|peek|attach|logs Name\nours-fleet logs -f Name\nours-fleet send Name \"prompt\"\nours-fleet send Name --key Enter        # tmux only\nours-fleet rm Name\nours-fleet watchdog-report <name> [run-id] [--list] [--json]\nours-fleet watchdog-run <name>\n```\n\n`peek`, `attach`, and text `send` work with tmux and ACP. ACP attachment\nalso accepts `/permit <permission-id> <option-id>`, `/interrupt`, and\n`/detach`. Raw `--key` input is tmux-only.\n\n## Local web console\n\nThe npm package includes the web console; installed users do not clone the repo\nor run `npm run build`:\n\n```sh\nnpm i -g @ours.network/fleet\nours-fleet init\nours-fleet doctor\nours-fleet web                         # install/update service, start, pair browser\n```\n\nThe normal command uses stable `http://127.0.0.1:49271/`, installs an\nowner-level systemd user service (Linux) or LaunchAgent (macOS), and opens a\nfive-minute one-use pairing link in the local browser. After pairing, bookmark\nthe plain URL or install the PWA. To pair a new, signed-out, or revoked browser,\nrun `ours-fleet web open`.\n\n```sh\nours-fleet web status\nours-fleet web start|stop|restart\nours-fleet web open\nours-fleet web revoke-all              # revoke every browser and active session\nours-fleet web uninstall\nours-fleet web serve --port 0 --no-open # isolated foreground/testing mode\n```\n\nThe console is intentionally IPv4-loopback-only. It has no LAN/Internet host,\nproxy, TLS, or remote-access mode. Do not expose port 49271 through a reverse\nproxy. Browser credentials are HttpOnly/SameSite, and `revoke-all` invalidates\nall trusted devices. Role creation offers harness-scoped known-model choices\nwhile still accepting a typed model ID; blank explicitly uses the selected\nharness's own default.\n\n## Spawn\n\n```sh\nours-fleet spawn [--temp] Name \\\n  --harness codex|claude-code --session tmux|acp \\\n  --mission \"one line\" --cwd /absolute/path --identity Identity \\\n  --coordinator Coordinator --model MODEL \\\n  --approval ask|allow|deny \\\n  --filesystem read-only|workspace|unrestricted \\\n  --unattended deny|wait \\\n  --bio-file /path/bio.md --persona-file /path/persona.md\n```\n\nPermanent spawn writes `~/fleet.d/Name.yaml` and starts a supervised role.\n`--temp` writes ephemeral state, starts a detached supervisor, and removes the\nrole after exit/reboot. Both lifetimes support `--session acp`.\n\nCodex-specific spawn flags: `--sandbox`, `--permission-mode`, `--launcher`,\n`--profile`, `--search`, repeatable `--codex-config key=value`, repeatable\n`--add-dir`, and legacy `--monitor` (consent for the native Codex monitor,\nnot the `monitor.mode` wake-owner selector). Run `ours-fleet help spawn` for\nexact values.\n\n## fleet.yaml\n\n```yaml\nvars:\n  work_root: /home/me/work\nstart_stagger_ms: 0\ndefaults:\n  harness: codex\n  session: acp\n  model: gpt-model-id\n  permissions:\n    approval: ask\n    filesystem: workspace\n    unattended: deny\n  monitor:\n    mode: fleet                          # fleet (default) | native\nroles:\n  Coordinator:\n    harness: codex\n    session: acp\n    identity: Coordinator\n    cwd: ${work_root}/project\n    mission: Coordinate work and delegate implementation.\n    model: gpt-model-id\n    permissions:\n      approval: ask\n      filesystem: workspace\n      unattended: deny\n    session_options:                    # advanced overrides; normally omit\n      # acp:\n      #   command: [/custom/codex-acp, --flag]\n      tmux:\n        boot_grace_ms: 10000\n    monitor:\n      mode: fleet                        # fleet supervisor | native harness monitor\n      interrupt: false                    # true cancels active work before every configured wake\n      wake_sources: [message_received, file_received, local_contact_request, pending_message]\n      batch_ms: 2000\n      inject: notification\n      turn_fail_threshold: 3\n    harness_options:\n      launcher: auto\n      sandbox: workspace-write\n      approval: on-request\n      search: false\n      profile: fleet\n      add_dirs: [/data/shared]\n      config:\n        model_reasoning_effort: high\n    bio: Public role card and when peers should engage it.\n    persona: Local operating contract, boundaries, and escalation policy.\n    briefing_file: /absolute/custom-briefing.md\n    coordinator: AnotherCoordinator\n    env:\n      KEY: value\n    oversee:\n      - { role: Worker, interval: 5m }\nwatchdogs:\n  nightwatch:                       # [A-Za-z0-9_-], must not collide with a role name\n    coordinator: FleetCoordinator   # required \u2014 where alerts go\n    # everything below is optional\n    enabled: true                   # default true; false = configured but never scheduled\n    interval: 10m                   # default 10m; 30s | 10m | 2h, minimum 1m\n    watch: [Alice, CodexReviewer]   # explicit lists are exact; omit for configured + live temp roles\n    harness: claude-code            # default: defaults.harness\n    model: claude-fable-5           # default: same resolution rule roles use (resolveRoleModel)\n    session: acp                    # default: defaults.session\n    identity: Watchdog-nightwatch   # default: Watchdog-<name>\n    timeout: 5m                     # default 5m; a run past this is killed and recorded as error\n    keep_reports: 50                # default 50 reports retained per watchdog\n    alert_cooldown: 60m             # default 60m before the same finding alerts again\n    prompt_file: /abs/extra.md      # optional extra focus, APPENDED to the fixed contract\n    isolation:                      # optional; omitted means no OS sandbox, like an ordinary role\n      backend: bubblewrap           # when present, the ordinary role isolation schema applies\n      network: broker\n      fs: { read: [/opt/watch-data] }\n```\n\nA watchdog observes and reports; it never restarts, stops, spawns, or removes a\nrole, answers a pending permission, edits a workspace, or approves anything on\nthe owner's behalf. `watchdogs:` may appear only in the base config\n(`~/fleet.yaml` or `-c FILE`), not in `~/fleet.d/*.yaml` drop-ins.\nWatchdogs are not isolated by default. An explicit watchdog `isolation:` block\nuses the same policy schema as a role and is applied unchanged; declare every\nextra filesystem access required by a custom prompt there.\nWhen `watch:` is omitted, each run watches the configured roles plus temporary\nfleet roles that are live when the run starts. An explicit `watch:` list is\nnever augmented.\n\nRole values override defaults. `${name}` substitutes entries from `vars`.\nOther role fields include `max_tokens`, `autocompact_pct`, and `isolation`.\nUse README.md for the complete isolation policy and resource-cap schema.\n\n## Permissions\n\nPrefer the harness-neutral `permissions` block:\n\n- `approval: ask|allow|deny`: whether actions may request or receive approval\n- `filesystem: read-only|workspace|unrestricted`: filesystem intent\n- `unattended: deny|wait`: what ACP does when no console can answer a request\n\nThe backend translates this common intent. Harness-native settings in\n`harness_options` take precedence where supplied. Do not choose\n`allow`/`unrestricted`, Codex `never`/`danger-full-access`, or Claude\n`bypassPermissions` without explicit authorization.\n\n### Creation-time isolation\n\n`ours-fleet spawn --isolation-file <path>` supplies a role's sandbox policy at\ncreation, so the FIRST launch is already confined \u2014 a role that only gains\n`isolation:` on a later `up` ran unsandboxed until then.\n\nThe file holds exactly the `isolation:` mapping documented above and nothing\nelse \u2014 the same schema, validated by the same code, so a policy written here\ncannot mean something different from the identical block in fleet.yaml:\n\n```yaml\nnetwork: deny\nfs:\n  read: [/opt/reference]\nresources:\n  mem: 2G\n```\n\nInvalid files are rejected before anything is created: no config, no state\ndirectory, no identity reservation. Works for both permanent and `--temp` roles.\n\n### Never-prompt failure\n\nThe failure this section exists to prevent leaves no error message anywhere.\n\nAn unattended role has no console. When the harness needs a permission decision\nthere is nobody to ask, so the request is refused INSIDE the harness \u2014 no\nprompt, no error, no log line. The agent simply does less than its briefing told\nit to, reports success, and nothing distinguishes that from having done the\nwork. Two settings produce it:\n\n1. a permission mode that suppresses the prompt without granting the action\n   (Claude `dontAsk`, which is why neutral `allow` maps to\n   `bypassPermissions` instead); and\n2. `unattended: deny`, which refuses every request that reaches it.\n\n**Automatic decisions are now recorded.** Every permission request decided\nwithout a human emits a completed event into\n`~/.ours-fleet/agents/<Name>/.session-events.jsonl` carrying the decision,\nwhether policy or a person made it, the policy that produced it\n(`permissions.unattended=deny` vs `permissions.approval=deny`/`=allow`),\nthe reason, and the option selected. `ours-fleet peek` and `attach` render\nthem. Automatic denial asks for a one-shot rejection, never a standing one, so a\nsingle unattended refusal cannot disable a tool for the rest of the session.\n\nA role that can auto-deny logs one line at startup saying so.\n\nTo detect an under-permissioned role BEFORE it runs, use the capability floor\nbelow: `ours-fleet doctor` fails such a role rather than letting it discover\nthe problem silently at work.\n\n### The unattended capability floor\n\nAn unattended role has no console, so a permission request cannot be answered \u2014\nit is refused, silently, inside the harness. The agent then does less than it\nwas told to and reports no error. To make that visible before launch,\n`ours-fleet config` and `ours-fleet doctor` resolve each role's neutral\npermissions through its harness and check the result against a fixed floor:\n\n- `read-state` \u2014 read its briefing, ROUTINES.md, and WORKLOG.md\n- `write-state` \u2014 append its WORKLOG and its own state files\n- `messaging` \u2014 bind its identity, send and receive ours mail\n- `monitor` \u2014 arm and observe its mail monitor\n- `workspace-edit` \u2014 edit and test files in its working directory\n- `status-commands` \u2014 run the inspection commands its briefing prescribes\n\n`doctor` reports this per role as `unattended floor: <Role>`. A role with\n`unattended: deny` that cannot meet the floor FAILS doctor, because it will\ndeny those requests with nobody to see it; with `unattended: wait` it warns,\nbecause a human can still attach and answer.\n\nSecurity meaning: `approval: allow` maps to Claude's `bypassPermissions`,\nwhich genuinely permits the actions the role was authorized to take \u2014\n`dontAsk` only suppresses the prompt while still refusing the action. Nothing\nother than an explicit `allow` is elevated: `ask` stays on Claude's default\nmode and `deny` maps to `plan`. `allow` is therefore a real grant and\nrequires explicit authorization; per-role `isolation:` remains the outer\nboundary that a permission mode cannot cross.\n\nSee also: `spawn --approval/--filesystem/--unattended` set this intent at\ncreation, and `ours-fleet config` prints each role's neutral settings, their\nnative translation, and any warning \u2014 the same text `doctor` reports.\n\nClaude `harness_options`: `permission_mode` (default, acceptEdits, plan,\ndontAsk, bypassPermissions), `plugins`, `mem_palace`, and\n`mem_palace_midsession_autosave`.\n\nCodex `harness_options`: `launcher` (auto, ours-codex, codex), `sandbox`\n(read-only, workspace-write, danger-full-access), `approval` or\n`permission_mode` (untrusted, on-request, never), `profile`, `search`,\n`config`, `add_dirs`, and `monitor`.\n\n## ACP adapters\n\nThe maintained `@agentclientprotocol/codex-acp` and\n`@agentclientprotocol/claude-agent-acp` runtimes are bundled automatically as\noptional ours-fleet dependencies. The supervisor resolves their executable\nentrypoints internally, so default ACP roles do not depend on global PATH.\nThe maintained Claude adapter requires Node 22; tmux and Codex ACP continue to\nwork on the ours-fleet core minimum of Node 20.\n\nOverride an adapter only when necessary with `session_options.acp.command`\n(string or argv list). If optional dependencies were deliberately omitted,\nours-fleet falls back to a compatible globally installed `codex-acp` or\n`claude-agent-acp`. `ours-fleet doctor -c FILE` verifies the resolved adapter.\n\n## Reliable mail wake\n\n`monitor.mode` selects exactly one wake owner:\n\n- `fleet` (default): the ours-fleet supervisor consumes body-free daemon\n  events and advances its durable cursor only after delivery is accepted. ACP\n  uses live steering when supported and falls back to structured\n  `session/prompt`; tmux uses verified console injection.\n- `native`: ours-fleet starts no supervisor monitor; the generated briefing\n  instructs Claude Code or Codex to arm its harness-native wake mechanism.\n\nSet `monitor.interrupt: true` in fleet mode to cancel active work before every\nconfigured wake. The policy is content-blind because the supervisor cannot\ninspect encrypted message bodies. Message bodies are released only when the\nrole calls the ours `get_messages` tool.\n\nLegacy `monitor.enabled: true|false` remains accepted as an alias for\n`mode: fleet|native`; use `mode` in new configuration. Codex's separate\n`harness_options.monitor: true` is native-monitor consent, not monitor-owner\nselection.\nInspect `ours-fleet status Name`, `peek Name`, role logs, and\n`~/.ours-fleet/agents/Name/.monitor-status` when diagnosing delivery.\n\n## Stable config and YAML migration\n\n`ours-fleet config --json` emits schemaVersion 1 resolved plans. Environment\nvalues and mission/persona/bio bodies are withheld; environment keys are sorted\nand values are marked redacted. Additive fields may appear in schema 1, while a\nremoval or semantic reuse requires a new schema version.\n\nYAML parsing always rejects duplicate keys. The current default\n`--yaml-mode compat` warns with file/line/column for anchors, aliases, explicit\ntags, non-scalar keys, and multiple documents. Use `--yaml-mode strict` in CI\nnow; strict becomes the next-major default and compat is the temporary migration\nescape hatch.\n\n## Bounded worklogs, auth proxy, and model recovery\n\nAn optional `worklog: { max_kb, keep_tail_kb, max_archives }` policy rotates a\nstable snapshot at fleet-owned lifecycle points. Concurrent changes defer\nrotation. Archives remain beside WORKLOG.md with the same sensitive-state\nboundary; retention deletes only recognized fleet archive names.\n\n`auth_proxy: { kind: anthropic, base_url, required, health_url }` is Claude-only\nand loopback-only. Fleet injects only ANTHROPIC_BASE_URL and doctor rejects\ncredential env keys. The privileged reference companion is\n`contrib/anthropic-auth-proxy.mjs`; deploy it separately as a dedicated account\nwith a 0600 token file and per-role listener access. Fleet never installs it or\nreads its credential.\n\n`model_chain` is an ordered authorization list and its first entry must equal\n`model`. Only sustained high-confidence entitlement/quota 429 evidence advances\none entry. Transient 429, overload, auth, policy, and unknown errors never\ndown-shift. Runtime state is atomic in .model-recovery.json; exhaustion is\nfail-closed and held down. Change the declared chain/model and restart to\nreconcile explicitly; no chain preserves detection-only behavior.\n";
 /**
  * What every shipped spawn-skill variant must say, and must not say (7.1).
  *

package/dist/docs.js

@@ -167,7 +167,7 @@ watchdogs:
     # everything below is optional
     enabled: true                   # default true; false = configured but never scheduled
     interval: 10m                   # default 10m; 30s | 10m | 2h, minimum 1m
-    watch: [Alice, CodexReviewer]   # default: every role in the merged config
+    watch: [Alice, CodexReviewer]   # explicit lists are exact; omit for configured + live temp roles
     harness: claude-code            # default: defaults.harness
     model: claude-fable-5           # default: same resolution rule roles use (resolveRoleModel)
     session: acp                    # default: defaults.session
@@ -176,12 +176,22 @@ watchdogs:
     keep_reports: 50                # default 50 reports retained per watchdog
     alert_cooldown: 60m             # default 60m before the same finding alerts again
     prompt_file: /abs/extra.md      # optional extra focus, APPENDED to the fixed contract
+    isolation:                      # optional; omitted means no OS sandbox, like an ordinary role
+      backend: bubblewrap           # when present, the ordinary role isolation schema applies
+      network: broker
+      fs: { read: [/opt/watch-data] }
 \`\`\`
 
 A watchdog observes and reports; it never restarts, stops, spawns, or removes a
 role, answers a pending permission, edits a workspace, or approves anything on
 the owner's behalf. \`watchdogs:\` may appear only in the base config
 (\`~/fleet.yaml\` or \`-c FILE\`), not in \`~/fleet.d/*.yaml\` drop-ins.
+Watchdogs are not isolated by default. An explicit watchdog \`isolation:\` block
+uses the same policy schema as a role and is applied unchanged; declare every
+extra filesystem access required by a custom prompt there.
+When \`watch:\` is omitted, each run watches the configured roles plus temporary
+fleet roles that are live when the run starts. An explicit \`watch:\` list is
+never augmented.
 
 Role values override defaults. \`\${name}\` substitutes entries from \`vars\`.
 Other role fields include \`max_tokens\`, \`autocompact_pct\`, and \`isolation\`.

package/dist/harness/codex.js

@@ -44,6 +44,17 @@ function sandboxMode(role) {
         throw new Error(`invalid harness_options.sandbox "${s}"; allowed: ${SANDBOX_MODES.join(', ')}`);
     return s;
 }
+/** codex-acp exposes the same sandbox postures as named ACP agent modes. */
+function acpAgentMode(role) {
+    const sandbox = sandboxMode(role);
+    if (sandbox === 'read-only')
+        return 'read-only';
+    if (sandbox === 'workspace-write')
+        return 'agent';
+    if (sandbox === 'danger-full-access')
+        return 'agent-full-access';
+    return undefined;
+}
 /** Resolve & validate the per-role approval policy, throwing on an unknown value. */
 function approvalPolicy(role) {
     const o = role.harness_options;
@@ -215,7 +226,11 @@ export function makeCodexAdapter(exec = realExec) {
                 : typeof configured === 'string'
                     ? ['sh', '-c', configured]
                     : bundledAcpAgent('@agentclientprotocol/codex-acp', 'codex-acp', 'codex-acp');
-            return { argv, env: prep.env };
+            const initialMode = acpAgentMode(role);
+            return {
+                argv,
+                env: initialMode ? { ...prep.env, INITIAL_AGENT_MODE: initialMode } : prep.env,
+            };
         },
         isolationPaths(role, _dirs) {
             const codexHome = join(home(), '.codex');

package/dist/isolation/policy.js

@@ -168,6 +168,11 @@ export function resolveIsolation(cfg, ctx) {
     }
     for (const dir of ctx.additionalWriteDirs ?? [])
         addRw(dir);
+    // The selected harness/session command may live outside the system allowlist
+    // (for example Node and a bundled ACP adapter under ~/.local). The runner
+    // resolves its exact executable/package closure; keep every such bind RO.
+    for (const path of ctx.runtimeReadPaths ?? [])
+        addRo(path);
     // Declared fs extras.
     for (const p of cfg.fs?.write ?? [])
         addRw(p);

package/dist/isolation/runtime.d.ts

@@ -0,0 +1,16 @@
+export interface LaunchRuntime {
+    /** Launch argv with a PATH-resolved command, so the mounted executable is the one invoked. */
+    argv: string[];
+    /** Exact executable and package roots required by the launch, mounted read-only. */
+    readPaths: string[];
+}
+export interface LaunchRuntimeOptions {
+    path?: string;
+    nodeExecutable?: string;
+}
+/**
+ * Resolve the concrete runtime closure for an already-selected harness launch.
+ * System roots are already present in every isolation policy; everything else
+ * is returned as an exact read-only executable or npm package-root bind.
+ */
+export declare function resolveLaunchRuntime(argv: string[], options?: LaunchRuntimeOptions): LaunchRuntime;

package/dist/isolation/runtime.js

@@ -0,0 +1,136 @@
+import { accessSync, closeSync, constants, existsSync, openSync, readFileSync, readSync, realpathSync, } from 'node:fs';
+import { createRequire } from 'node:module';
+import { delimiter, dirname, isAbsolute, join, resolve, sep } from 'node:path';
+const SYSTEM_ROOTS = ['/usr', '/bin', '/sbin', '/lib', '/lib64', '/etc'];
+const inside = (path, root) => path === root || path.startsWith(root + sep);
+function canonical(path) {
+    try {
+        return realpathSync.native(path);
+    }
+    catch {
+        return resolve(path);
+    }
+}
+function commandPath(command, pathValue) {
+    const candidates = isAbsolute(command) || command.includes(sep)
+        ? [resolve(command)]
+        : pathValue.split(delimiter).filter(Boolean).map(dir => resolve(dir, command));
+    for (const candidate of candidates) {
+        try {
+            accessSync(candidate, constants.X_OK);
+            return canonical(candidate);
+        }
+        catch { /* keep searching PATH */ }
+    }
+    return undefined;
+}
+function packageRoot(path) {
+    let dir = existsSync(path) ? dirname(path) : path;
+    for (;;) {
+        const manifest = join(dir, 'package.json');
+        if (existsSync(manifest))
+            return dir;
+        const parent = dirname(dir);
+        if (parent === dir)
+            return undefined;
+        dir = parent;
+    }
+}
+function dependencyManifest(manifestPath, name) {
+    const localRequire = createRequire(manifestPath);
+    try {
+        return localRequire.resolve(`${name}/package.json`);
+    }
+    catch {
+        // Some packages do not export package.json. Their main entry still gives us
+        // a point from which to find the owning package root.
+        try {
+            const entry = localRequire.resolve(name);
+            const root = packageRoot(entry);
+            return root ? join(root, 'package.json') : undefined;
+        }
+        catch {
+            return undefined;
+        }
+    }
+}
+function addPackageClosure(root, paths, seen) {
+    const canonicalRoot = canonical(root);
+    if (seen.has(canonicalRoot))
+        return;
+    seen.add(canonicalRoot);
+    paths.add(canonicalRoot);
+    const manifestPath = join(canonicalRoot, 'package.json');
+    try {
+        const manifest = JSON.parse(readFileSync(manifestPath, 'utf8'));
+        const names = new Set([
+            ...Object.keys(manifest.dependencies ?? {}),
+            ...Object.keys(manifest.optionalDependencies ?? {}),
+            ...Object.keys(manifest.peerDependencies ?? {}),
+        ]);
+        for (const name of names) {
+            const dependency = dependencyManifest(manifestPath, name);
+            if (dependency)
+                addPackageClosure(dirname(dependency), paths, seen);
+        }
+    }
+    catch { /* a malformed/unreadable manifest cannot contribute a closure */ }
+}
+function isNodeScript(path) {
+    let fd;
+    try {
+        fd = openSync(path, 'r');
+        const bytes = Buffer.alloc(128);
+        const count = readSync(fd, bytes, 0, bytes.length, 0);
+        return /^#!.*\bnode\b/.test(bytes.subarray(0, count).toString('utf8'));
+    }
+    catch {
+        return false;
+    }
+    finally {
+        if (fd !== undefined)
+            closeSync(fd);
+    }
+}
+/**
+ * Resolve the concrete runtime closure for an already-selected harness launch.
+ * System roots are already present in every isolation policy; everything else
+ * is returned as an exact read-only executable or npm package-root bind.
+ */
+export function resolveLaunchRuntime(argv, options = {}) {
+    if (!argv.length)
+        return { argv: [], readPaths: [] };
+    const nodeExecutable = canonical(options.nodeExecutable ?? process.execPath);
+    const executable = commandPath(argv[0], options.path ?? process.env.PATH ?? '');
+    const resolvedArgv = executable ? [executable, ...argv.slice(1)] : [...argv];
+    const paths = new Set();
+    const packages = new Set();
+    const consider = (path) => {
+        if (!isAbsolute(path) || !existsSync(path))
+            return;
+        const real = canonical(path);
+        const root = packageRoot(real);
+        if (root)
+            addPackageClosure(root, paths, packages);
+        else
+            paths.add(real);
+        if (real === nodeExecutable || isNodeScript(real))
+            paths.add(nodeExecutable);
+    };
+    if (executable)
+        consider(executable);
+    // A direct Node launch's first existing absolute non-option argument is its
+    // module entrypoint. Other absolute arguments are harness inputs/settings,
+    // not runtime code, and already follow the ordinary filesystem policy.
+    if (executable === nodeExecutable) {
+        const entrypointIndex = argv.findIndex((arg, index) => index > 0 && !arg.startsWith('-') && isAbsolute(arg) && existsSync(arg));
+        if (entrypointIndex !== -1) {
+            resolvedArgv[entrypointIndex] = canonical(argv[entrypointIndex]);
+            consider(resolvedArgv[entrypointIndex]);
+        }
+    }
+    return {
+        argv: resolvedArgv,
+        readPaths: [...paths].filter(path => !SYSTEM_ROOTS.some(root => inside(path, root))),
+    };
+}

package/dist/isolation/types.d.ts

@@ -63,6 +63,8 @@ export interface WrapContext {
      * them for itself or for its peers.
      */
     harnessSharedPaths?: string[];
+    /** Exact launcher/interpreter/module closure required by the selected command. */
+    runtimeReadPaths?: string[];
     brokerEndpoint?: string;
 }
 /**

package/dist/resolved-plan.js

@@ -26,6 +26,7 @@ export function resolvedPlan(cfg) {
             harness: w.harness, session: w.session, model: w.model ?? null,
             identity: w.identity, timeoutMs: w.timeoutMs, keepReports: w.keepReports,
             alertCooldownMs: w.alertCooldownMs, promptFile: w.promptFile ?? null,
+            isolation: w.isolation ?? null,
         })),
     };
 }

package/dist/runner.js

@@ -11,6 +11,7 @@ import { realExec, shq } from './exec.js';
 import { resolveIsolation } from './isolation/policy.js';
 import { selectIsolationBackend } from './isolation/registry.js';
 import { resourceArgs, cpuControllerDelegated } from './isolation/resources.js';
+import { resolveLaunchRuntime } from './isolation/runtime.js';
 import { AcpSession } from './session/acp.js';
 import { RoleControlServer } from './session/control.js';
 import { TmuxSession } from './session/tmux.js';
@@ -319,7 +320,7 @@ export async function runOnce(name, opts = {}, partialDeps = {}) {
     const runCwd = role.cwd && existsSync(role.cwd) ? role.cwd : dir;
     const prep = await adapter.prepareSession(role, { stateDir: dir, runCwd });
     const sessionBackend = role.session ?? 'tmux';
-    const launch = sessionBackend === 'acp'
+    let launch = sessionBackend === 'acp'
         ? (() => {
             if (!adapter.buildAcpLaunch)
                 throw new Error(`harness '${role.harness}' does not support the ACP session backend`);
@@ -330,10 +331,15 @@ export async function runOnce(name, opts = {}, partialDeps = {}) {
     // env prefix + exit capture in buildPaneCommand stay host-side (see §5.3).
     let wrappedArgv = launch.argv;
     if (role.isolation) {
-        // The SAME context config validation and doctor judged (5.2): a policy
-        // checked against a different mount set than the one that launches is not a
-        // check at all.
-        const ctx = { ...isolationContextFor(role), stateDir: dir, runCwd };
+        // Start with the SAME durable context config validation and doctor judged
+        // (5.2), then add the selected launch's exact runtime closure. Those paths
+        // still pass through resolveIsolation's canonical blocklist enforcement.
+        const runtime = resolveLaunchRuntime(launch.argv);
+        launch = { ...launch, argv: runtime.argv };
+        const ctx = {
+            ...isolationContextFor(role), stateDir: dir, runCwd,
+            runtimeReadPaths: runtime.readPaths,
+        };
         const policy = resolveIsolation(role.isolation, ctx);
         const sel = await selectIsolationBackend(policy, deps.exec); // throws on strict + unavailable
         const degradedMarker = join(dir, '.isolation-degraded');

package/dist/watchdog/config.d.ts

@@ -1,4 +1,5 @@
 import type { FleetConfig, ResolvedRole, SessionBackendId } from '../config.js';
+import type { IsolationConfig } from '../isolation/types.js';
 export interface WatchdogConfig {
     coordinator?: string;
     enabled?: boolean;
@@ -12,6 +13,7 @@ export interface WatchdogConfig {
     keep_reports?: number;
     alert_cooldown?: string;
     prompt_file?: string;
+    isolation?: IsolationConfig;
 }
 export interface ResolvedWatchdog {
     name: string;
@@ -19,6 +21,7 @@ export interface ResolvedWatchdog {
     enabled: boolean;
     intervalMs: number;
     watch: string[];
+    watchExplicit: boolean;
     harness: string;
     session: SessionBackendId;
     model?: string;
@@ -27,6 +30,7 @@ export interface ResolvedWatchdog {
     keepReports: number;
     alertCooldownMs: number;
     promptFile?: string;
+    isolation?: IsolationConfig;
     sourceFile: string;
 }
 export declare const WATCHDOG_DEFAULT_INTERVAL_MS = 600000;

package/dist/watchdog/config.js

@@ -2,9 +2,10 @@ import { existsSync } from 'node:fs';
 import { isAbsolute } from 'node:path';
 import { parseDuration } from '../duration.js';
 import { ConfigError, ROLE_NAME_RE, resolveRoleModel } from '../config.js';
+import { validateIsolationConfig } from '../isolation/policy.js';
 const WATCHDOG_KEYS = [
     'coordinator', 'enabled', 'interval', 'watch', 'harness', 'model', 'session',
-    'identity', 'timeout', 'keep_reports', 'alert_cooldown', 'prompt_file',
+    'identity', 'timeout', 'keep_reports', 'alert_cooldown', 'prompt_file', 'isolation',
 ];
 export const WATCHDOG_DEFAULT_INTERVAL_MS = 600_000;
 export const WATCHDOG_MIN_INTERVAL_MS = 60_000;
@@ -69,6 +70,11 @@ export function resolveWatchdogs(baseDoc, baseFile, roles, vars, defaults) {
             if (!existsSync(w.prompt_file))
                 throw new ConfigError(`${where}: prompt_file not found: ${w.prompt_file}`);
         }
+        if (w.isolation !== undefined) {
+            const problems = validateIsolationConfig(w.isolation);
+            if (problems.length)
+                throw new ConfigError(`${where} ${problems.join('; ')}`);
+        }
         const dur = (v, key, fallback, minMs) => {
             if (v === undefined)
                 return fallback;
@@ -88,13 +94,13 @@ export function resolveWatchdogs(baseDoc, baseFile, roles, vars, defaults) {
             name, coordinator: w.coordinator.trim(),
             enabled: w.enabled ?? true,
             intervalMs: dur(w.interval, 'interval', WATCHDOG_DEFAULT_INTERVAL_MS, WATCHDOG_MIN_INTERVAL_MS),
-            watch, harness, session: sessionRaw,
+            watch, watchExplicit: w.watch !== undefined, harness, session: sessionRaw,
             model: resolveRoleModel(w.model, w.harness, defaults),
             identity,
             timeoutMs: dur(w.timeout, 'timeout', WATCHDOG_DEFAULT_TIMEOUT_MS),
             keepReports,
             alertCooldownMs: dur(w.alert_cooldown, 'alert_cooldown', WATCHDOG_DEFAULT_COOLDOWN_MS),
-            promptFile: w.prompt_file, sourceFile: baseFile,
+            promptFile: w.prompt_file, isolation: w.isolation, sourceFile: baseFile,
         });
     }
     return out;

package/dist/watchdog/run.d.ts

@@ -21,6 +21,8 @@ export interface WatchdogRunDeps {
     launchChild?(binPath: string, roleName: string, runDir: string): WatchdogChildHandle;
     /** Pre-loaded config (defaults inheritance). Falls back to `loadConfig()`. */
     cfg?: FleetConfig;
+    /** Live temporary-role discovery override for focused tests. */
+    discoverLiveTemporaryRoles?(): Promise<string[]>;
 }
 export interface WatchdogRunOutcome {
     report: WatchdogReport;

package/dist/watchdog/run.js

@@ -1,4 +1,4 @@
-import { closeSync, existsSync, openSync, readFileSync, rmSync, statSync, writeFileSync, } from 'node:fs';
+import { closeSync, existsSync, openSync, readFileSync, readdirSync, rmSync, statSync, writeFileSync, } from 'node:fs';
 import { spawn as spawnChild, execFile } from 'node:child_process';
 import { join } from 'node:path';
 import { promisify } from 'node:util';
@@ -10,10 +10,12 @@ import { computeDigest, reconcileLedger, readLedger, writeLedger } from './alert
 import { applyRole } from '../ops.js';
 import { daemonIdentityProvisioner, ensureIdentity, } from '../creation.js';
 import { runOnce, START_STAGGER_FILE } from '../runner.js';
-import { agentDir } from '../paths.js';
-import { loadConfig, resolveMonitorConfig, resolveWorklogPolicy, } from '../config.js';
+import { agentDir, tmpRoot } from '../paths.js';
+import { loadConfig, resolveMonitorConfig, resolveWorklogPolicy, ROLE_NAME_RE, } from '../config.js';
 import { getAdapter } from '../harness/registry.js';
 import { redactLogLine } from '../application/log-service.js';
+import { controlRequest, controlSocketPath } from '../session/control.js';
+import { Tmux } from '../tmux.js';
 const execFileAsync = promisify(execFile);
 /** How often the deadline loop polls for a completed report or a dead child. */
 const POLL_MS = 1000;
@@ -92,33 +94,49 @@ function readTail(runDir) {
         return undefined;
     }
 }
-/**
- * The temp role every watchdog-family run (inspection and notifier alike) launches under.
- * `network: 'broker'` keeps ours messaging available; no write binds beyond stateDir/cwd, which
- * resolveIsolation adds itself. ~/fleet.yaml and fleet.d are deliberately NOT bound — they're on
- * the isolation blocklist, and everything either run flavor needs is written into its own dir.
- *
- * Read access is scoped to exactly `wd.watch` (finding #3): a watchdog configured to watch one
- * role must not be able to read every other role's state dir just because they all live under
- * the same agents root. `wd.watch` defaults to every role (watchdog/config.ts's
- * resolveWatchdogs), so a watchdog that watches everything still sees everything — this only
- * narrows visibility for a watchdog scoped to fewer roles. A watched role whose state dir doesn't
- * exist (e.g. a role removed after the watchdog was configured) is simply absent from the
- * bwrap ro-bind-try set — the agent reports it unreachable from status evidence, same as any
- * other missing state dir.
- */
+/** The temp role every watchdog-family run launches under. Isolation is opt-in. */
 function buildWatchdogRole(wd, cfg) {
     return {
         name: wd.identity, sourceFile: '(watchdog)',
         harness: wd.harness, session: wd.session,
         identity: wd.identity, model: wd.model,
-        permissions: { approval: 'allow', filesystem: 'workspace', unattended: 'deny' },
+        // Watchdogs are observe-only by contract, but their sanctioned status commands
+        // must reach host control sockets. Keep approvals/unattended escalation denied
+        // while disabling the harness's native filesystem/network sandbox.
+        permissions: { approval: 'deny', filesystem: 'unrestricted', unattended: 'deny' },
         permissionsDeclared: true,
         monitor: resolveMonitorConfig(cfg.defaults.monitor, undefined),
         worklog: resolveWorklogPolicy(cfg.defaults.worklog, undefined),
-        isolation: { fs: { read: wd.watch.map(r => agentDir(r)) }, network: 'broker' },
+        isolation: wd.isolation,
     };
 }
+/** Discover temporary sessions that are live now, not merely stale dirs on disk. */
+async function discoverLiveTemporaryRoles() {
+    let names;
+    try {
+        names = readdirSync(tmpRoot(), { withFileTypes: true })
+            .filter(entry => entry.isDirectory() && !entry.isSymbolicLink() && ROLE_NAME_RE.test(entry.name))
+            .map(entry => entry.name);
+    }
+    catch {
+        return [];
+    }
+    const tmux = new Tmux();
+    const live = await Promise.all(names.map(async (name) => {
+        const dir = agentDir(name, true);
+        const [acpAlive, tmuxAlive] = await Promise.all([
+            existsSync(controlSocketPath(dir))
+                ? controlRequest(dir, { command: 'status' }, 2_000)
+                    .then(response => response.ok
+                    && response.result?.alive === true)
+                    .catch(() => false)
+                : Promise.resolve(false),
+            tmux.has(name).catch(() => false),
+        ]);
+        return acpAlive || tmuxAlive ? name : undefined;
+    }));
+    return live.filter((name) => name !== undefined);
+}
 /**
  * Run one watchdog agent end-to-end in a clean-context temp state dir: provision
  * identity, materialize the run's contract (briefing/manifest/role snapshot),
@@ -147,14 +165,20 @@ export async function executeWatchdogRun(wd, deps) {
     try {
         const guarantee = await ensureIdentity(wd.identity, {}, deps.identityProvisioner ?? daemonIdentityProvisioner(), deps.log);
         const cfg = deps.cfg ?? loadConfig();
-        const role = buildWatchdogRole(wd, cfg);
+        const discovered = wd.watchExplicit
+            ? []
+            : await (deps.discoverLiveTemporaryRoles ?? discoverLiveTemporaryRoles)();
+        const watch = [...new Set([...wd.watch, ...discovered])]
+            .filter(name => name !== wd.identity);
+        const runWd = { ...wd, watch };
+        const role = buildWatchdogRole(runWd, cfg);
         const dir = applyRole(role, { temp: true, identityGuarantee: guarantee.state });
         const reportPath = join(dir, 'report.json');
         const manifestPath = join(dir, 'watch.json');
         const promptFocus = wd.promptFile ? readFileSync(wd.promptFile, 'utf8') : undefined;
         // applyRole wrote the generic role briefing; the watchdog contract replaces it.
         writeFileSync(join(dir, 'briefing.md'), generateWatchdogBriefing({
-            wd, manifestPath, reportPath,
+            wd: runWd, manifestPath, reportPath,
             vocabulary: getAdapter(wd.harness).vocabulary,
             identityGuarantee: guarantee.state,
             promptFocus,
@@ -163,7 +187,10 @@ export async function executeWatchdogRun(wd, deps) {
         writeFileSync(join(dir, 'role.yaml'), stringify(role));
         const manifest = {
             watchdog: wd.name, run_id: runId, coordinator: wd.coordinator, started_at: startedAt,
-            roles: wd.watch.map(r => ({ name: r, stateDir: agentDir(r) })),
+            roles: runWd.watch.map(r => ({
+                name: r,
+                stateDir: wd.watch.includes(r) ? agentDir(r) : agentDir(r, true),
+            })),
             digest: computeDigest(ledger, wd.alertCooldownMs, now()),
         };
         writeFileSync(manifestPath, JSON.stringify(manifest, null, 2) + '\n');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ours.network/fleet",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "Harness-agnostic fleet of persistent, identity-bound AI agents. Declarative fleet.yaml, tmux or ACP sessions, supervision, and ours.network messaging.",
   "type": "module",
   "license": "FSL-1.1-Apache-2.0",