@sma1lboy/kobe 0.8.103 → 0.8.104
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/dist/cli/index.js +9 -8
- package/dist/cli/kobe.js +9 -8
- package/dist/cli/rove.js +9 -8
- package/dist/skills/rove/SKILL.md +13 -10
- package/package.json +1 -1
|
@@ -3,13 +3,15 @@ name: rove
|
|
|
3
3
|
description: Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — `rove api send`, never a peer/MCP side channel.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
<!-- rove-skill-version:
|
|
6
|
+
<!-- rove-skill-version: 23 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
|
|
7
7
|
|
|
8
8
|
# Rove shell control
|
|
9
9
|
|
|
10
|
-
Use `rove api` to manage local coding tasks.
|
|
11
|
-
|
|
12
|
-
|
|
10
|
+
Use `rove api` to manage local coding tasks. Managed Tasks created by API
|
|
11
|
+
automation own a git Worktree and branch plus Hosted PTY engine tabs; project
|
|
12
|
+
main and directory Tasks reuse existing directories. API automation works
|
|
13
|
+
without an open TUI; prompted `send`, `add`, and `fan-out` ensure a target
|
|
14
|
+
engine tab.
|
|
13
15
|
|
|
14
16
|
## Inside a Rove session, Rove verbs come first
|
|
15
17
|
|
|
@@ -68,9 +70,9 @@ user asks for Rove by name.
|
|
|
68
70
|
|
|
69
71
|
| Term | What it is | Isolation it gives | Users also say |
|
|
70
72
|
|---|---|---|---|
|
|
71
|
-
| **Task** | one
|
|
72
|
-
| **Worktree** |
|
|
73
|
-
| **Terminal Tab** | one engine
|
|
73
|
+
| **Task** | one tracked workspace record — managed worktree, saved-project main, or existing directory | managed Tasks own files + branch; main/directory Tasks reuse files | "a task", "a new one", "a separate attempt" |
|
|
74
|
+
| **Worktree** | the isolated git working tree a managed Task owns (`.task.worktreePath`) | — | "workspace", "this checkout", "this branch", "here" |
|
|
75
|
+
| **Terminal Tab** | one engine, shell, command, or content surface inside a Task | an engine tab has its own conversation, but every tab uses the SAME Task files | "tab", "chattab", "another chat", "a second agent on this" |
|
|
74
76
|
| **Split** | the tree that divides ONE Terminal Tab into several regions (the `pane-open` verb's unit; a leaf is not called a pane) | none — same session's screen, same files | "split it", "side by side", "put the logs next to it" |
|
|
75
77
|
|
|
76
78
|
Two of those colloquialisms are traps, so read them as INTENT, not as
|
|
@@ -188,7 +190,8 @@ rove api collect --task-ids <id1>,<id2>,<id3> --pretty
|
|
|
188
190
|
rove api list --pretty
|
|
189
191
|
```
|
|
190
192
|
|
|
191
|
-
`.running` means
|
|
193
|
+
`.running` means any hosted engine tab on the task is alive; a live shell,
|
|
194
|
+
command, or content tab alone does not count.
|
|
192
195
|
Omitting BOTH `--task-id` and `--tab` inside a task that has a dispatcher
|
|
193
196
|
targets that dispatcher's tab (see the reply rule above); otherwise the
|
|
194
197
|
target is the active task. Omitting only `--tab` targets a live engine tab
|
|
@@ -278,10 +281,10 @@ explicit count. Give each task a scoped prompt, report returned IDs, then use
|
|
|
278
281
|
poll `send` in a tight loop or use it as casual chat; every call is a full
|
|
279
282
|
engine turn.
|
|
280
283
|
|
|
281
|
-
### Completion flows back through
|
|
284
|
+
### Completion flows back through an engine tab (`send`)
|
|
282
285
|
|
|
283
286
|
Outcomes are explicit, never inferred — and they travel as a MESSAGE to the
|
|
284
|
-
spawning agent's
|
|
287
|
+
spawning agent's engine tab, not as stored state nobody reads.
|
|
285
288
|
|
|
286
289
|
**Worker side** — a task created from inside another Rove task records its
|
|
287
290
|
dispatcher (the creating task + tab); when the work is finished, a bare
|
package/package.json
CHANGED