@sma1lboy/kobe 0.6.4 → 0.6.5

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/README.md +27 -22
  2. package/dist/cli/index.js +5185 -4467
  3. package/package.json +3 -2
package/README.md CHANGED
@@ -203,24 +203,33 @@ kobe daemon stop # tell the daemon to drain and exit
203
203
  > was removed in favor of the single-bin surface (KOB-136); any script with
204
204
  > `kobed restart` needs a one-time rename to `kobe daemon restart`.
205
205
 
206
- ### `kobe api <verb>` — five shell verbs
206
+ ### `kobe api <verb>` — six shell verbs
207
207
 
208
- Each call is a short-lived process: open the daemon socket, do one RPC, print
209
- JSON to stdout, exit. Any tool with a `Bash` capability (Claude Code, Codex,
210
- Cursor, a custom agent) can drive it.
208
+ Each call is a short-lived process: connect to (or auto-start) the daemon, do
209
+ the work, print JSON to stdout, exit. Any tool with a `Bash` capability (Claude
210
+ Code, Codex, Cursor, a custom agent) can drive it.
211
211
 
212
212
  | verb | flags | what it does |
213
213
  |---|---|---|
214
- | `spawn-task` | `--repo PATH --prompt TEXT [--title T] [--base-branch B]` | Create a new task + worktree + chat session. |
215
- | `create-tab` | `--task-id ID [--title T]` | Open an extra chat tab on an existing task. |
216
- | `send` | `--task-id ID --prompt TEXT [--tab-id TID]` | Resume the task's session with a new prompt. |
217
- | `get-task` | `--task-id ID` | Read task metadata (status, branch, worktree, tabs). |
218
- | `get-tab` | `--task-id ID --tab-id TID` | Read a single tab off the task. |
214
+ | `spawn-task` | `--repo PATH [--prompt TEXT] [--title T] [--base-branch B] [--vendor V]` | Create one task + worktree. With `--prompt`, also start the engine in tmux and deliver the prompt. |
215
+ | `fan-out` | `--repo PATH --prompt TEXT [--count N \| --agents claude:2,codex:1] [--base-branch B]` | Spawn N tasks of the same prompt in one call (per-engine counts optional). Returns `{count, tasks[]}`. Capped at 10. |
216
+ | `send` | `[--task-id ID] --prompt TEXT` | Paste a prompt into a task's engine pane (bracketed paste, then Enter — multi-line stays one turn). Defaults to the active task; prefer `--task-id` for unattended fan-out. |
217
+ | `get-task` | `--task-id ID` | Read task metadata; `.running` is true when the tmux session is live. |
218
+ | `collect` | `--task-ids a,b,c \| --repo PATH` | Read-only aggregation snapshot: per task, branch + `.running` + uncommitted `.changes` ({added, deleted}) for comparing attempts. |
219
+ | `list` | — | List all tasks. |
220
+
221
+ `spawn-task --prompt` and `send` also return `.engineReady` — `false` means a freshly-started engine didn't confirm it was ready before the prompt was pasted (delivered best-effort).
219
222
 
220
223
  Output is one JSON object on stdout, `\n` terminated, exit 0. Errors land on
221
224
  stderr as `{"error":{"message":"...","code":"..."}}` with a non-zero exit.
222
225
  Add `--pretty` for human inspection.
223
226
 
227
+ v0.6 is tmux-native — a task's chat history lives in its tmux session, not in
228
+ the daemon — so `send` types the prompt into the engine pane and there is no
229
+ verb that reads the reply back. Results are reviewed in the TUI. (The v0.5
230
+ `create-tab` / `get-tab` verbs are gone; extra chat tabs are tmux windows
231
+ opened from inside the TUI.)
232
+
224
233
  Fan-out from a shell:
225
234
 
226
235
  ```bash
@@ -229,19 +238,17 @@ T2=$(kobe api spawn-task --repo "$PWD" --prompt "Approach B: event sourcing" |
229
238
  T3=$(kobe api spawn-task --repo "$PWD" --prompt "Approach C: reducer pattern" | jq -r .taskId)
230
239
 
231
240
  # Tell the user three tasks are running — they'll appear in the sidebar.
232
- echo "Spawned $T1 $T2 $T3"
241
+ echo "Spawned $T1 $T2 $T3 — open the kobe TUI to watch them"
233
242
 
234
- # Poll until each settles.
243
+ # Confirm each session came up.
235
244
  for ID in $T1 $T2 $T3; do
236
- until [ "$(kobe api get-task --task-id "$ID" | jq -r .task.status)" = "idle" ]; do
237
- sleep 10
238
- done
245
+ kobe api get-task --task-id "$ID" | jq -r '"\(.task.id) running=\(.running)"'
239
246
  done
240
247
  ```
241
248
 
242
- If the daemon isn't running, `kobe api ...` exits 2 with
243
- `{"error":{"code":"BAD_DAEMON",...}}` on stderr. Start it with
244
- `kobe daemon start` (or just launch the TUI).
249
+ `kobe api ...` auto-starts the daemon, so there is nothing to launch first. If
250
+ the daemon cannot be reached or started, it exits 2 with
251
+ `{"error":{"code":"BAD_DAEMON",...}}` on stderr.
245
252
 
246
253
  ### Install the agent skill
247
254
 
@@ -262,12 +269,10 @@ After install, Claude Code automatically picks up the skill on its next launch.
262
269
  For project-level overrides, copy the file to `<repo>/.claude/skills/kobe/SKILL.md`
263
270
  and customise — Claude Code's discovery order is project > user > none.
264
271
 
265
- `kobe diagnose` reports whether the skill is installed, which is the
266
- fastest way to confirm.
272
+ To confirm it installed, check that `~/.claude/skills/kobe/SKILL.md` exists.
267
273
 
268
- > `kobe skill install` is deprecated as of v0.6 — use the `npx skills`
269
- > command above. `kobe skill uninstall` still works for cleaning up an
270
- > older copy.
274
+ > The old built-in `kobe skill install` / `kobe diagnose` commands were
275
+ > removed in v0.6 use the `npx skills` command above to manage the skill.
271
276
 
272
277
  ## Coming later
273
278