@ours.network/fleet-claude-code 1.0.5 → 1.1.0-nightly.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ours.network/fleet-claude-code",
-  "version": "1.0.5",
+  "version": "1.1.0-nightly.10",
   "description": "Claude Code plugin for ours-fleet — spawn and oversee fleet agents from inside a session. Bundles the spawn-ours-agent and oversee-agents skills; the ours-fleet CLI (@ours.network/fleet) does the actual work.",
   "license": "FSL-1.1-Apache-2.0",
   "author": "Adapt Framework Solutions Ltd",
@@ -10,8 +10,25 @@
     "url": "git+https://github.com/adapt-toolkit/ours-fleet.git",
     "directory": "integrations/claude-code"
   },
-  "keywords": ["claude", "claude-code", "plugin", "fleet", "agents", "tmux", "spawn", "oversight", "ours"],
-  "files": [".claude-plugin", "skills"],
-  "publishConfig": { "access": "public" },
-  "engines": { "node": ">=20" }
+  "keywords": [
+    "claude",
+    "claude-code",
+    "plugin",
+    "fleet",
+    "agents",
+    "acp",
+    "spawn",
+    "oversight",
+    "ours"
+  ],
+  "files": [
+    ".claude-plugin",
+    "skills"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "engines": {
+    "node": ">=20"
+  }
 }

package/skills/oversee-agents/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oversee-agents
-description: Keep an eye on ours-fleet agents you spawned or were assigned, across tmux or ACP sessions. Inspect state, unstick agents through ours-fleet controls, and escalate consequential choices. Use when the user or your persona/briefing says "keep an eye on X", "oversee agents", "watch agents", or right after spawning an agent.
+description: Keep an eye on ours-fleet agents you spawned or were assigned over ACP sessions. Inspect state, unstick agents through ours-fleet controls, and escalate consequential choices. Use when the user or your persona/briefing says "keep an eye on X", "oversee agents", "watch agents", or right after spawning an agent.
 ---
 
 # Oversee ours-fleet agents
@@ -13,8 +13,7 @@ ours-fleet status <Name>
 ours-fleet peek <Name> [lines]
 ours-fleet logs <Name>
 ours-fleet send <Name> "<text>"
-ours-fleet send <Name> --key <K>      # tmux only
-ours-fleet attach <Name>              # tmux or ACP interactive control
+ours-fleet attach <Name>              # structured interactive control
 ```
 
 ## 1. Determine your assignment
@@ -62,7 +61,7 @@ Once you know the role is alive, classify what the console actually shows:
 
 | Console shows | Action |
 |---|---|
-| Permission prompt or trust dialog | Answer only within already-authorized scope. Use `send --key` for tmux or the `/permit` control shown by ACP `attach`. |
+| Permission prompt or trust dialog | Answer only within already-authorized scope using the `/permit` control shown by `attach`. |
 | A question the agent asked its (absent) user | Answer with what you know of the mission: `ours-fleet send <Name> "<answer>"`. |
 | Crashed to a shell prompt / error text | Investigate (`ours-fleet logs <Name>`); restart a permanent role only once `status` confirms it is offline. |
 | Idle with work still assigned | Nudge: `ours-fleet send <Name> "Status? Continue with <task> or declare BLOCKED."` |

package/skills/spawn-ours-agent/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: spawn-ours-agent
-description: Spawn and configure an ours-fleet agent from Claude Code, using a permanent or temporary lifetime and a tmux or ACP session. Use when the user says "spawn ours agent", "spawn an agent", "create a fleet agent", "start a background agent", or asks for a separate supervised agent.
+description: Spawn and configure an ours-fleet agent from Claude Code, using a permanent or temporary lifetime and an ACP session. Use when the user says "spawn ours agent", "spawn an agent", "create a fleet agent", "start a background agent", or asks for a separate supervised agent.
 ---
 
 # Spawn an ours-fleet agent
@@ -16,7 +16,7 @@ ours-fleet doctor
 ```
 
 `ours-fleet docs` from the INSTALLED CLI is authoritative for supported
-harnesses, session backends, permissions, and flags. This skill ships with a
+harnesses, structured sessions, permissions, and flags. This skill ships with a
 plugin and the CLI is upgraded separately, so where the two differ the installed
 reference wins. Stop at a failed required doctor check.
 
@@ -124,9 +124,7 @@ Permanent, unattended (announce it to yourself if you are its coordinator):
 
 ```sh
 ours-fleet spawn <Name> \
-  --harness claude-code --session <tmux|acp> \
-  --mission "<one-line mission>" \
-  --bio-file /tmp/spawn-bio.md --persona-file /tmp/spawn-persona.md \
+  --brain <BrainId> --role <RoleId> \
   --approval allow --filesystem workspace --unattended deny \
   --isolation-file /tmp/spawn-isolation.yaml \
   [--cwd <dir>] [--coordinator <YourRoleName>]
@@ -136,23 +134,19 @@ Permanent, attended — a human will answer its prompts:
 
 ```sh
 ours-fleet spawn <Name> \
-  --harness claude-code --session <tmux|acp> \
-  --mission "<one-line mission>" \
-  --bio-file /tmp/spawn-bio.md --persona-file /tmp/spawn-persona.md \
+  --brain <BrainId> --role <RoleId> \
   --approval ask --filesystem workspace --unattended wait
 ```
 
-Temporary — add `--temp`; it supports both session backends:
+Temporary — add `--temp`; it uses the same structured session interface:
 
 ```sh
 ours-fleet spawn --temp <Name> \
-  --harness claude-code --session <tmux|acp> \
-  --mission "<one-line mission>" \
-  --bio-file /tmp/spawn-bio.md --persona-file /tmp/spawn-persona.md \
+  --brain <BrainId> --role <RoleId> \
   --approval allow --filesystem workspace --unattended deny
 ```
 
-Pass model, permission, session, and coordinator choices exactly as approved.
+Pass Brain, Role, permission, and coordinator choices exactly as approved.
 Do not persist secrets in fleet YAML.
 
 ## 8. Verify
@@ -169,8 +163,8 @@ settings it translated to; the floor line lists what the role actually grants,
 or names what is missing. A failure there means the role will silently do less
 than its briefing says — fix the permissions rather than starting it.
 
-For ACP, `status` must report `backend: acp`, `alive: true`, and a running/idle
-readiness. For tmux, the pane is authoritative. Confirm the role loaded its
+`status` must report `backend: acp`, `alive: true`, and a running/idle
+readiness. Confirm the role loaded its
 briefing and reached identity binding. Never answer a permission prompt beyond
 the scope already approved by the user.