@ours.network/fleet-codex 0.19.0-nightly.14 → 0.19.0-nightly.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/.codex-plugin/plugin.json +1 -1
  2. package/package.json +1 -1
  3. package/skills/spawn-ours-agent/SKILL.md +11 -5
package/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ours-fleet",
3
- "version": "0.19.0-nightly.14",
3
+ "version": "0.19.0-nightly.15",
4
4
  "description": "Spawn, configure, and oversee ours-fleet roles from OpenAI Codex.",
5
5
  "author": {
6
6
  "name": "Adapt Framework Solutions Ltd",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ours.network/fleet-codex",
3
- "version": "0.19.0-nightly.14",
3
+ "version": "0.19.0-nightly.15",
4
4
  "description": "Native Codex plugin for spawning, configuring, and overseeing ours-fleet agents.",
5
5
  "type": "module",
6
6
  "license": "FSL-1.1-Apache-2.0",
package/skills/spawn-ours-agent/SKILL.md CHANGED
@@ -54,10 +54,16 @@ What this means in practice, on this harness:
54
54
 
55
55
  | Neutral intent | Native settings | Meets the floor? |
56
56
  | --- | --- | --- |
57
- | `--approval allow --filesystem workspace` | `approval=never sandbox=workspace-write` | yes |
58
- | `--approval allow --filesystem read-only` | `approval=never sandbox=read-only` | no — no `write-state`, no `workspace-edit` |
59
- | `--approval ask` | `approval=on-request` | no — `read-state` only |
60
- | `--approval deny` | `approval=on-request` | no — `read-state` only |
57
+ | `--approval allow --filesystem workspace` | ACP: `agent-full-access` / `never` / `danger-full-access`; tmux: `never` / `workspace-write` | yes |
58
+ | `--approval allow --filesystem read-only` | ACP: `agent-full-access` / `never` / `danger-full-access`; tmux: `never` / `read-only` | ACP yes; tmux no |
59
+ | `--approval auto` | ACP: `agent` / `on-request` / `workspace-write` | no — `read-state` only |
60
+ | `--approval ask` or legacy `deny` | conservative prompting mode | no — `read-state` only |
61
+
62
+ Codex ACP mode IDs couple approval and filesystem. Neutral `allow` intentionally
63
+ selects the yolo/`agent-full-access` preset, widening a neutral `workspace` or
64
+ `read-only` filesystem value. Neutral `auto` selects `agent`. An explicit
65
+ `--sandbox` override still wins. Use `--isolation-file` as the outer boundary
66
+ for an ACP role that needs `allow`.
61
67
 
62
68
  ## 3. Choose permissions from the job, not from a default
63
69
 
@@ -77,7 +83,7 @@ user authorizes it, then pick:
77
83
  or get the authorization; do not paper over it with a mode that only hides
78
84
  the prompt.
79
85
 
80
- Never choose `--filesystem unrestricted`, `--sandbox danger-full-access`, or a
86
+ Never choose an explicit `--filesystem unrestricted`, `--sandbox danger-full-access`, or a
81
87
  native `--permission-mode` override without the user asking for it by name and
82
88
  understanding what it grants. `harness_options` wins over the neutral block at
83
89
  launch, so stating intent in both places and disagreeing is how a role runs on