zswarm 0.2.6 → 0.2.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zswarm",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "type": "module",
   "description": "Coordinate CLI agent crews in Zellij panes",
   "engines": {
@@ -23,8 +23,8 @@
     "skills"
   ],
   "dependencies": {
-    "@zswarm/cli": "0.2.6",
-    "@zswarm/mcp": "0.1.16"
+    "@zswarm/cli": "0.2.7",
+    "@zswarm/mcp": "0.1.17"
   },
   "publishConfig": {
     "access": "public"

package/skills/zswarm/references/harness.md

@@ -2,8 +2,9 @@
 
 Verified live against **codex**, **cursor**, **pi**, **opencode**, and **gemini** (`agy`).
 
-- **Read** (`dump`, `tail`, `status`, `wait --for idle`) works on all five.
+- **Read** (`dump`, `tail`, `status`, `wait --for idle`) works on all five verified harnesses.
 - **Send** lands on all five (`codex` auto-detects `submit=double-enter`, others `auto`). The `expect` guard works on all five.
+- **OpenCode's** exit recipe is `/exit` and its ready markers are `Ask anything` / `ctrl+p commands` (verified live on a real pane). **Claude Code** carries a named `claude` profile (busy marker `esc to interrupt`, exit recipe `/exit`, ready marker `? for shortcuts`), defined from its documented UI; it was not verified live on the host that added it. Restart waits for the screen to settle when a profile declares no ready marker, and the other profiles restart with the Ctrl+C fallback.
 - **Replies can take > 60s.** Budget timeouts; a quiet pane is rarely a failed send.
 - **`wait --match` on a redrawing TUI is viewport-and-moment dependent.** Those apps
   own the alternate screen (no scrollback; `--full` is identical). Prefer
@@ -12,10 +13,10 @@ Verified live against **codex**, **cursor**, **pi**, **opencode**, and **gemini*
 
 Reaching zswarm from a harness is separate from driving one:
 
-- **4 of 5 have an MCP client** — they reach zswarm once session and interpreter
+- **5 of 6 have an MCP client** — they reach zswarm once session and interpreter
   path are explicit in the server config.
 - **1 ships no MCP client** — use `@zswarm/cli`, or the generic MCP bridge at
   `packages/pi/extensions/zswarm-mcp.ts` (`ZSWARM_MCP_SERVERS`).
-- **Being a target needs no integration.** All five are drivable with
+- **Being a target needs no integration.** All six are drivable with
   `send` / `dump` / `tail` / `wait` / `status`.
 

package/skills/zswarm/references/ops.md

@@ -13,6 +13,7 @@ MCP: `zswarm({ op, ... })`. CLI: `zswarm <op>`. Same surface.
 | `keys` | `expect` is checked before any input. Key specs (`keys: ["Ctrl c"]`) or literal `chars` (+ `enter`) |
 | `interrupt` | `Esc`; `hard: true` sends `Ctrl c` |
 | `spawn` | New pane (`newTab: true` for a fresh tab) with `command`, `cwd`, `name`, `direction`, `floating`; `tab` = tab name; `worktree` isolates on a branch |
+| `restart` | Restart the agent in its pane in place (same pane id, title, position) with an optional handoff; `to`, `handoffSelf`, `handoff` (inline), `command`, `force`, `timeoutMs`. See [restart](#restart) |
 | `close` | Close a pane |
 | `rename` | Retitle a pane (`to` + `name`) or a tab (`tab` + `name`) |
 | `focus` | Focus a pane; already-focused is a no-op success |
@@ -56,6 +57,38 @@ zswarm({ op: "send", to: "reviewer", body: "…", expect: "Add a follow-up" })
 
 Failure is `expect_missing` and nothing is written.
 
+## restart
+
+Restart the agent already running in a pane, in place: the same pane id, title,
+and position come back with a fresh harness process. Optional handoff first:
+`--handoff-self` asks the running agent to write its handoff to a file and print
+a marker, then waits (bounded) for it; `--handoff-file PATH` (`-` for stdin) reads
+a handoff on the caller, like `--body-file` (MCP `handoff` is inline).
+
+The steps are: exit via the harness profile's exit recipe (Claude Code / OpenCode
+type `/exit`; other profiles fall back to Ctrl+C), then Ctrl+C twice if it did not
+exit; wait until the pane's command has exited (Zellij reports the pane exited, a
+command pane shows its re-run prompt, or a shell prompt returns); relaunch in the
+same pane — a command pane gets ENTER at Zellij's re-run prompt, a shell pane gets
+the profile's launch command or `--command`; wait for readiness — the harness ready
+marker (OpenCode `Ask anything` / `ctrl+p commands`, Claude Code `? for shortcuts`),
+or, for a harness with no declared marker, until the screen stops changing (two
+identical dumps ~1s apart), then a short settle before input; and deliver the
+handoff. A short handoff is pasted; a long one becomes a one-line pointer to the
+file. If the send reports `not-delivered` (positive evidence nothing landed), the
+handoff is resent once after readiness returns; any other non-true submission is
+reported, never resent.
+
+The result lists each step's outcome under `steps`. A failure names the failed
+step in `error.message`, with the step in `error.details.step`. A pane that a
+relay has leased is refused with `pane_leased` unless `--force`.
+
+```text
+zswarm restart --to reviewer --handoff-self
+zswarm restart --to terminal_9 --handoff-file handoff.md --timeout-ms 60000
+zswarm({ op: "restart", to: "reviewer", handoff: "pick up the failing test", force: true })
+```
+
 ## Event bus
 
 `zswarm({ op: "bus", install: true })` once per Zellij session. After that

package/skills/zswarm/references/remote.md

@@ -122,4 +122,7 @@ running and finished relays, `--leases` lists current pane leases,
 keep a remote crew running. A relay leases its target pane until it ends; a
 second relay (or `send --if-idle`) refuses a leased pane with `pane_leased`
 (`--queue` waits, `--force` shares the lease, a stale lease is taken over).
+`relay --if-idle` applies `send --if-idle`'s busy check before the lease
+(`pane_busy` when the harness shows work; `--queue` waits for the pane to
+go idle as well as for the lease; `--force` skips the check).
 See docs/hosts.md in the zswarm repo.