@ours.network/fleet-codex 0.3.7 → 0.4.0
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.
package/README.md
CHANGED
|
@@ -19,6 +19,8 @@ Then ask Codex to “spawn an ours agent”, “create a persistent Codex role
|
|
|
19
19
|
“keep an eye on my fleet agents”.
|
|
20
20
|
|
|
21
21
|
Codex may ask for one-time authorization before individual ours MCP tools run.
|
|
22
|
-
|
|
23
|
-
user explicitly requests it.
|
|
24
|
-
`
|
|
22
|
+
Native Codex mail wake is consent-first: a spawned role receives the legacy
|
|
23
|
+
`--monitor` consent flag only when the user explicitly requests it.
|
|
24
|
+
In fleet YAML, `monitor.mode: fleet|native` separately chooses whether
|
|
25
|
+
ours-fleet or the harness owns wake delivery. `ours-codex` supplies native
|
|
26
|
+
background wake; plain `codex` remains the supported native foreground fallback.
|
package/package.json
CHANGED
|
@@ -99,8 +99,9 @@ Ask only for choices not already supplied:
|
|
|
99
99
|
- **Persona:** local operating contract covering mandate, quality bar,
|
|
100
100
|
boundaries, and escalation. Use the writing-agent-bios skill when available.
|
|
101
101
|
- **Coordinator:** optionally announce readiness to an existing ours identity.
|
|
102
|
-
- **
|
|
103
|
-
after a clear yes. This
|
|
102
|
+
- **Native Codex mail monitoring:** explicitly ask whether to arm it. Pass the
|
|
103
|
+
legacy `--monitor` consent flag only after a clear yes. This is distinct from
|
|
104
|
+
fleet YAML `monitor.mode: fleet|native`, which chooses the wake owner.
|
|
104
105
|
|
|
105
106
|
Codex-native controls, offered when relevant:
|
|
106
107
|
|
|
@@ -163,7 +164,8 @@ ours-fleet spawn Worker --harness codex --launcher auto \
|
|
|
163
164
|
```
|
|
164
165
|
|
|
165
166
|
Add `--temp` for a temporary role; it can also use `--session acp`.
|
|
166
|
-
Pass `--monitor` only after
|
|
167
|
+
Pass the legacy `--monitor` flag only after consent to arm Codex's native
|
|
168
|
+
monitor. It does not select the wake owner; `monitor.mode` does that in YAML.
|
|
167
169
|
Pass model, profile, search, config, and additional directories exactly as
|
|
168
170
|
approved. Do not persist secrets in `--codex-config` or fleet YAML; use the
|
|
169
171
|
role's `env` configuration for environment-based credentials.
|