@ours.network/fleet 0.10.3 → 0.10.4

package/dist/config.d.ts

@@ -73,7 +73,8 @@ export interface RoleConfig {
     persona?: string;
     bio?: string;
     briefing_file?: string;
-    model?: string;
+    /** Explicit null means use the selected harness's own default, bypassing fleet defaults. */
+    model?: string | null;
     model_chain?: string[];
     max_tokens?: number;
     autocompact_pct?: number;
@@ -85,7 +86,7 @@ export interface RoleConfig {
     worklog?: WorklogPolicy;
     auth_proxy?: Partial<AuthProxyConfig>;
 }
-export interface ResolvedRole extends RoleConfig {
+export interface ResolvedRole extends Omit<RoleConfig, 'model'> {
     name: string;
     harness: string;
     session: SessionBackendId;
@@ -98,6 +99,7 @@ export interface ResolvedRole extends RoleConfig {
      */
     permissionsDeclared: boolean;
     identity: string;
+    model?: string;
     sourceFile: string;
     monitor: MonitorConfig;
     worklog?: WorklogPolicy;
@@ -115,6 +117,8 @@ export interface FleetConfig {
 }
 export declare class ConfigError extends Error {
 }
+/** Resolve a model without leaking a default that belongs to another harness. */
+export declare function resolveRoleModel(model: string | null | undefined, harness: string | undefined, defaults: Record<string, unknown>): string | undefined;
 /**
  * The runtime facts the isolation resolver needs for a role. Single-sourced so
  * config validation, doctor, and the runner all judge the SAME mount set — a
@@ -122,6 +126,7 @@ export declare class ConfigError extends Error {
  * a check at all.
  */
 export declare function isolationContextFor(role: ResolvedRole): WrapContext;
+export declare const ROLE_NAME_RE: RegExp;
 /** Load ~/fleet.yaml (or an explicit path) merged with ~/fleet.d/*.yaml drop-ins. */
 export declare function loadConfig(configPath?: string, options?: {
     yamlMode?: YamlMode;

package/dist/config.js

@@ -60,6 +60,16 @@ export function validateMonitorConfig(raw) {
 }
 export class ConfigError extends Error {
 }
+/** Resolve a model without leaking a default that belongs to another harness. */
+export function resolveRoleModel(model, harness, defaults) {
+    if (model === null)
+        return undefined;
+    if (typeof model === 'string' && model.trim())
+        return model.trim();
+    const defaultHarness = defaults.harness ?? 'claude-code';
+    const effectiveHarness = harness ?? defaultHarness;
+    return effectiveHarness === defaultHarness ? defaults.model : undefined;
+}
 /**
  * The runtime facts the isolation resolver needs for a role. Single-sourced so
  * config validation, doctor, and the runner all judge the SAME mount set — a
@@ -91,7 +101,7 @@ export function isolationContextFor(role) {
         harnessSharedPaths: split?.shared,
     };
 }
-const NAME_RE = /^[A-Za-z0-9_-]+$/;
+export const ROLE_NAME_RE = /^[A-Za-z0-9_-]+$/;
 const ROLE_KEYS = [
     'harness', 'session', 'session_options', 'permissions', 'identity', 'cwd', 'coordinator', 'mission', 'persona', 'bio',
     'briefing_file', 'model', 'model_chain', 'max_tokens', 'autocompact_pct', 'env', 'oversee', 'harness_options',
@@ -143,7 +153,7 @@ export function loadConfig(configPath, options = {}) {
     const roles = [];
     for (const { file, doc } of docs) {
         for (const [name, raw] of Object.entries((doc.roles ?? {}))) {
-            if (!NAME_RE.test(name))
+            if (!ROLE_NAME_RE.test(name))
                 throw new ConfigError(`${file}: invalid role name '${name}' (allowed: [A-Za-z0-9_-])`);
             const prev = seen.get(name);
             if (prev)
@@ -177,9 +187,13 @@ export function loadConfig(configPath, options = {}) {
             const monitor = resolveMonitorConfig(defaults.monitor, r.monitor, { base, file, name });
             const worklog = resolveWorklogPolicy(defaults.worklog, r.worklog, file, name);
             const authProxy = resolveAuthProxy(defaults.auth_proxy, r.auth_proxy, file, name);
-            const model = r.model ?? defaults.model;
-            const modelChain = resolveModelChain(model, r.model_chain ?? defaults.model_chain, file, name);
             const harness = r.harness ?? defaults.harness ?? 'claude-code';
+            const defaultHarness = defaults.harness ?? 'claude-code';
+            const inheritsModelDefaults = harness === defaultHarness && r.model !== null;
+            const model = resolveRoleModel(r.model, r.harness, defaults);
+            const modelChain = resolveModelChain(model, r.model_chain ?? (inheritsModelDefaults
+                ? defaults.model_chain
+                : undefined), file, name);
             if (authProxy && harness !== 'claude-code')
                 throw new ConfigError(`${file}: role '${name}' auth_proxy is supported only by claude-code`);
             const env = {

package/dist/creation.d.ts

@@ -24,7 +24,10 @@ export interface CreationDeps {
     identityRegistry?: IdentityRegistry;
     /** Verify/create the ours identity. Injectable so tests need no daemon. */
     identityProvisioner?: IdentityProvisioner;
+    /** Descriptive progress around the existing transaction; never a second workflow. */
+    onStage?(stage: CreationCoreStage, evidence?: Record<string, string | boolean>): void;
 }
+export type CreationCoreStage = 'reserving' | 'checking_identity' | 'writing_role' | 'registering_supervisor' | 'starting_temp';
 /**
  * The contract the ours daemon must satisfy for identity names to be reserved
  * atomically across ALL of its clients, not just across fleet processes.
@@ -101,12 +104,15 @@ export interface IdentityProvisioner {
 }
 export type IdentityGuarantee = {
     state: 'verified';
+    evidence: 'verified';
     detail: string;
 } | {
     state: 'created';
+    evidence: 'missing';
     detail: string;
 } | {
     state: 'unverified';
+    evidence: 'missing' | 'unknown';
     detail: string;
 };
 /**
@@ -148,6 +154,9 @@ export interface CreationProvenance {
     createdAt: string;
     lifetime: 'permanent' | 'temporary';
     role: string;
+    /** Additive correlation for non-CLI creation surfaces; never contains request data. */
+    surface?: 'cli' | 'web';
+    creationActionId?: string;
     /** Effective settings, each tagged with where its value came from. */
     settings: Record<string, ProvenanceEntry>;
 }
@@ -170,6 +179,8 @@ export declare function buildProvenance(o: {
     fleetVersion: string;
     now?: Date;
     settings: Record<string, ProvenanceEntry>;
+    surface?: 'cli' | 'web';
+    creationActionId?: string;
 }): CreationProvenance;
 /** Write the provenance record atomically, before the role is started. */
 export declare function writeProvenance(stateDir: string, p: CreationProvenance): void;

package/dist/creation.js

@@ -150,7 +150,10 @@ function readdirSyncSafe(dir) {
  */
 export async function ensureIdentity(name, profile, provisioner, log = () => { }) {
     if (!provisioner)
-        return { state: 'unverified', detail: 'no identity provisioner is configured' };
+        return {
+            state: 'unverified', evidence: 'unknown',
+            detail: 'no identity provisioner is configured',
+        };
     let present;
     try {
         present = await provisioner.exists(name);
@@ -160,18 +163,30 @@ export async function ensureIdentity(name, profile, provisioner, log = () => { }
         log(`identity '${name}': could not be verified (${e.message})`);
     }
     if (present === true)
-        return { state: 'verified', detail: 'the ours daemon reports it exists' };
+        return {
+            state: 'verified', evidence: 'verified',
+            detail: 'the ours daemon reports it exists',
+        };
     if (present === 'unknown')
-        return { state: 'unverified', detail: 'the ours daemon could not be asked' };
+        return {
+            state: 'unverified', evidence: 'unknown',
+            detail: 'the ours daemon could not be asked',
+        };
     if (!provisioner.create) {
         // Loud, and named. The briefing will tell the agent to mint it — which is
         // what actually happens today — but nobody is told it was "predefined".
         log(`identity '${name}' does not exist and this host cannot create one automatically — `
             + `the role will be told to mint it on first boot. Create it in advance to avoid that.`);
-        return { state: 'unverified', detail: 'it does not exist and cannot be created here' };
+        return {
+            state: 'unverified', evidence: 'missing',
+            detail: 'it does not exist and cannot be created here',
+        };
     }
     await provisioner.create(name, profile);
-    return { state: 'created', detail: 'created during spawn, with its bio and persona published' };
+    return {
+        state: 'created', evidence: 'missing',
+        detail: 'created during spawn, with its bio and persona published',
+    };
 }
 /**
  * Ask the running ours daemon whether an identity exists, over the same
@@ -230,6 +245,8 @@ export function buildProvenance(o) {
         createdAt: (o.now ?? new Date()).toISOString(),
         lifetime: o.lifetime,
         role: o.role,
+        surface: o.surface ?? 'cli',
+        creationActionId: o.creationActionId,
         settings: o.settings,
     };
 }

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\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## 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 }\n```\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\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 }\n```\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

@@ -45,6 +45,40 @@ ours-fleet rm Name
 also accepts \`/permit <permission-id> <option-id>\`, \`/interrupt\`, and
 \`/detach\`. Raw \`--key\` input is tmux-only.
 
+## Local web console
+
+The npm package includes the web console; installed users do not clone the repo
+or run \`npm run build\`:
+
+\`\`\`sh
+npm i -g @ours.network/fleet
+ours-fleet init
+ours-fleet doctor
+ours-fleet web                         # install/update service, start, pair browser
+\`\`\`
+
+The normal command uses stable \`http://127.0.0.1:49271/\`, installs an
+owner-level systemd user service (Linux) or LaunchAgent (macOS), and opens a
+five-minute one-use pairing link in the local browser. After pairing, bookmark
+the plain URL or install the PWA. To pair a new, signed-out, or revoked browser,
+run \`ours-fleet web open\`.
+
+\`\`\`sh
+ours-fleet web status
+ours-fleet web start|stop|restart
+ours-fleet web open
+ours-fleet web revoke-all              # revoke every browser and active session
+ours-fleet web uninstall
+ours-fleet web serve --port 0 --no-open # isolated foreground/testing mode
+\`\`\`
+
+The console is intentionally IPv4-loopback-only. It has no LAN/Internet host,
+proxy, TLS, or remote-access mode. Do not expose port 49271 through a reverse
+proxy. Browser credentials are HttpOnly/SameSite, and \`revoke-all\` invalidates
+all trusted devices. Role creation offers harness-scoped known-model choices
+while still accepting a typed model ID; blank explicitly uses the selected
+harness's own default.
+
 ## Spawn
 
 \`\`\`sh

package/dist/index.d.ts

@@ -11,7 +11,16 @@ export { generateBriefing } from './briefing.js';
 export { pickBackend } from './supervisor/index.js';
 export type { SupervisorBackend } from './supervisor/types.js';
 export { up, down, restartRoles, rmRole, applyRole } from './ops.js';
-export { spawnPermanent, spawnTemp } from './spawn.js';
+export { spawnPermanent, spawnTemp, buildRoleConfig, profileValues, validateSpawnOpts, } from './spawn.js';
+export { RoleRepository } from './application/role-repository.js';
+export { FleetQueryService } from './application/fleet-query-service.js';
+export { AcpRoleSessionAdapter, TmuxRoleSessionAdapter } from './application/session-control.js';
+export { RoleCreationService } from './application/role-creation-service.js';
+export { RoleCommandService } from './application/role-command-service.js';
+export { StructuredLogService } from './application/log-service.js';
+export { roleCapabilities } from './application/capabilities.js';
+export { FleetError, normalizeError } from './application/errors.js';
+export type * from './application/types.js';
 export { doctor } from './doctor.js';
 export { runOnce, runTemp } from './runner.js';
 export { Tmux } from './tmux.js';

package/dist/index.js

@@ -7,7 +7,15 @@ export { codexAdapter, makeCodexAdapter } from './harness/codex.js';
 export { generateBriefing } from './briefing.js';
 export { pickBackend } from './supervisor/index.js';
 export { up, down, restartRoles, rmRole, applyRole } from './ops.js';
-export { spawnPermanent, spawnTemp } from './spawn.js';
+export { spawnPermanent, spawnTemp, buildRoleConfig, profileValues, validateSpawnOpts, } from './spawn.js';
+export { RoleRepository } from './application/role-repository.js';
+export { FleetQueryService } from './application/fleet-query-service.js';
+export { AcpRoleSessionAdapter, TmuxRoleSessionAdapter } from './application/session-control.js';
+export { RoleCreationService } from './application/role-creation-service.js';
+export { RoleCommandService } from './application/role-command-service.js';
+export { StructuredLogService } from './application/log-service.js';
+export { roleCapabilities } from './application/capabilities.js';
+export { FleetError, normalizeError } from './application/errors.js';
 export { doctor } from './doctor.js';
 export { runOnce, runTemp } from './runner.js';
 export { Tmux } from './tmux.js';

package/dist/runner.js

@@ -60,8 +60,16 @@ export function recordMonitorOwner(dir, owner) {
  * still sees the real exit code.
  */
 export function buildPaneCommand(launch, roleEnv, exitStatusPath, paneArgv = launch.argv) {
-    const env = { PATH: process.env.PATH ?? '', ...launch.env, ...(roleEnv ?? {}) };
-    const envPfx = 'env ' + Object.entries(env).map(([k, v]) => `${k}=${shq(v)}`).join(' ');
+    const env = {
+        PATH: process.env.PATH ?? '', COLORTERM: 'truecolor', ...launch.env, ...(roleEnv ?? {}),
+    };
+    // Interactive panes should advertise colour even when the supervisor itself
+    // was launched with NO_COLOR. A role may still deliberately opt back in to
+    // NO_COLOR (or replace COLORTERM) through its explicit env block.
+    const unsetNoColor = Object.prototype.hasOwnProperty.call(roleEnv ?? {}, 'NO_COLOR')
+        ? '' : '-u NO_COLOR ';
+    const envPfx = 'env ' + unsetNoColor
+        + Object.entries(env).map(([k, v]) => `${k}=${shq(v)}`).join(' ');
     const cmd = paneArgv.map(shq).join(' ');
     // Write a structured record, not a bare number: the wait status alone cannot
     // say whether the file is missing because the program never exited or because

package/dist/session/control.d.ts

@@ -1,14 +1,16 @@
 import { type Socket } from 'node:net';
 import type { ControlFailureKind, SessionHandle } from './types.js';
 export interface ControlRequest {
-    version: 1;
+    version: 1 | 2;
     id: string;
     token: string;
-    command: 'status' | 'snapshot' | 'submit_prompt' | 'respond_permission' | 'interrupt' | 'follow';
+    command: 'status' | 'snapshot' | 'submit_prompt' | 'respond_permission' | 'interrupt' | 'follow' | 'events_since';
     text?: string;
     permissionId?: string;
     optionId?: string;
     since?: number;
+    /** Existing clients omit this and remain interactive controllers. */
+    controller?: boolean;
 }
 export interface ControlResponse {
     version: 1;

package/dist/session/control.js

@@ -132,6 +132,7 @@ export class RoleControlServer {
         socket.setEncoding('utf8');
         let buffer = '';
         let unsubscribe;
+        let controllerAttached = false;
         socket.on('data', chunk => {
             buffer += chunk;
             if (Buffer.byteLength(buffer) > MAX_LINE_BYTES) {
@@ -146,13 +147,15 @@ export class RoleControlServer {
                 buffer = buffer.slice(newline + 1);
                 if (!line.trim())
                     continue;
-                void this.handle(line, socket).then(stop => {
-                    if (stop) {
+                void this.handle(line, socket).then(follow => {
+                    if (follow) {
                         if (unsubscribe) {
                             unsubscribe();
-                            this.session.setControllerAttached(false);
+                            if (controllerAttached)
+                                this.session.setControllerAttached(false);
                         }
-                        unsubscribe = stop;
+                        unsubscribe = follow.stop;
+                        controllerAttached = follow.controller;
                     }
                 });
             }
@@ -161,7 +164,8 @@ export class RoleControlServer {
             this.sockets.delete(socket);
             if (unsubscribe) {
                 unsubscribe();
-                this.session.setControllerAttached(false);
+                if (controllerAttached)
+                    this.session.setControllerAttached(false);
             }
         });
         socket.on('error', error => this.log(`control socket: ${error.message}`));
@@ -175,7 +179,7 @@ export class RoleControlServer {
             this.write(socket, { version: 1, id: '?', ok: false, error: 'invalid JSON' });
             return;
         }
-        if (request.version !== 1 || typeof request.id !== 'string'
+        if ((request.version !== 1 && request.version !== 2) || typeof request.id !== 'string'
             || !sameToken(this.token, request.token ?? '')) {
             this.write(socket, { version: 1, id: request.id ?? '?', ok: false, error: 'unauthorized' });
             return;
@@ -184,7 +188,13 @@ export class RoleControlServer {
             switch (request.command) {
                 case 'status':
                 case 'snapshot':
-                    this.write(socket, { version: 1, id: request.id, ok: true, result: this.session.snapshot() });
+                    this.write(socket, {
+                        version: 1, id: request.id, ok: true,
+                        result: {
+                            ...this.session.snapshot(), protocolVersion: 2,
+                            features: ['events_since', 'observer_follow', 'retained_range'],
+                        },
+                    });
                     return;
                 case 'submit_prompt': {
                     if (!request.text?.trim())
@@ -217,17 +227,39 @@ export class RoleControlServer {
                     await this.session.interrupt();
                     this.write(socket, { version: 1, id: request.id, ok: true });
                     return;
-                case 'follow': {
+                case 'events_since': {
                     const since = Number.isFinite(request.since) ? Number(request.since) : 0;
+                    const events = this.session.eventsSince(since);
+                    const all = this.session.eventsSince(0);
                     this.write(socket, {
                         version: 1, id: request.id, ok: true,
-                        result: { events: this.session.eventsSince(since), snapshot: this.session.snapshot() },
+                        result: {
+                            events, snapshot: this.session.snapshot(),
+                            firstSeq: all[0]?.seq ?? 0, lastSeq: all.at(-1)?.seq ?? 0,
+                            truncated: Boolean(all[0] && since > 0 && since < all[0].seq - 1),
+                        },
                     });
-                    this.session.setControllerAttached(true);
-                    return this.session.subscribe(event => {
-                        if (!socket.destroyed)
-                            socket.write(JSON.stringify({ version: 1, event }) + '\n');
+                    return;
+                }
+                case 'follow': {
+                    const since = Number.isFinite(request.since) ? Number(request.since) : 0;
+                    const events = this.session.eventsSince(since);
+                    const all = this.session.eventsSince(0);
+                    this.write(socket, {
+                        version: 1, id: request.id, ok: true,
+                        result: {
+                            events, snapshot: this.session.snapshot(),
+                            firstSeq: all[0]?.seq ?? 0, lastSeq: all.at(-1)?.seq ?? 0,
+                            truncated: Boolean(all[0] && since > 0 && since < all[0].seq - 1),
+                        },
                     });
+                    const controller = request.controller !== false;
+                    if (controller)
+                        this.session.setControllerAttached(true);
+                    return { controller, stop: this.session.subscribe(event => {
+                            if (!socket.destroyed)
+                                socket.write(JSON.stringify({ version: 1, event }) + '\n');
+                        }) };
                 }
             }
         }

package/dist/spawn.d.ts

@@ -1,7 +1,9 @@
 import type { IsolationConfig } from './isolation/types.js';
-import { type ApprovalMode, type FilesystemMode, type ResolvedRole, type RoleConfig, type SessionBackendId, type UnattendedMode } from './config.js';
+import { type ApprovalMode, type FilesystemMode, type ResolvedRole, type RoleConfig, type MonitorConfig, type SessionBackendId, type UnattendedMode } from './config.js';
 import { type OpsDeps } from './ops.js';
 import { type CreationDeps, type CreationProvenance } from './creation.js';
+import './harness/claude-code.js';
+import './harness/codex.js';
 /**
  * The provenance record written by the most recent spawn in this process, so
  * the CLI can print the same summary it persisted rather than rebuilding it.
@@ -17,7 +19,8 @@ export interface SpawnOpts {
     identity?: string;
     cwd?: string;
     coordinator?: string;
-    model?: string;
+    /** null explicitly selects the harness default; undefined retains normal fleet inheritance. */
+    model?: string | null;
     permissionMode?: string;
     approval?: ApprovalMode;
     filesystem?: FilesystemMode;
@@ -29,8 +32,16 @@ export interface SpawnOpts {
     codexConfig?: Record<string, string | number | boolean>;
     addDirs?: string[];
     monitor?: boolean;
+    /** Typed external monitor configuration used by trusted creation surfaces. */
+    monitorConfig?: Partial<MonitorConfig>;
     bioFile?: string;
     personaFile?: string;
+    /** Inline profile values for trusted typed callers such as the local web service. */
+    bio?: string;
+    persona?: string;
+    /** Internal, non-sensitive provenance correlation for typed presentation layers. */
+    surface?: 'cli' | 'web';
+    creationActionId?: string;
     /**
      * Path to a file holding exactly the existing `isolation:` mapping — the same
      * schema fleet.yaml uses, not a second policy language. The ONE new operator
@@ -42,6 +53,12 @@ export interface SpawnOpts {
     dryRun?: boolean;
     json?: boolean;
 }
+export declare function profileValues(o: SpawnOpts): {
+    bio?: string;
+    persona?: string;
+};
+/** Pure option-to-role mapping shared by CLI and application services. */
+export declare function buildRoleConfig(o: SpawnOpts, defaultHarness?: string): RoleConfig;
 /**
  * Read and validate an `--isolation-file`. The file is the existing
  * `isolation:` mapping and nothing else — the same schema, the same validator
@@ -52,6 +69,7 @@ export interface SpawnOpts {
  * must fail before any artifact exists.
  */
 export declare function readIsolationFile(path: string): IsolationConfig;
+export declare function validateSpawnOpts(o: SpawnOpts): void;
 /** Read mission text without trimming or newline rewriting. */
 export declare function readMissionFile(path: string): string;
 /** The ours identity a spawn will bind: explicit, else the role name. */