@sma1lboy/kobe 0.8.65 → 0.8.68

package/dist/cli/pty-host-node.mjs

@@ -251,6 +251,7 @@ var DAEMON_CHANNELS = [
   "transcript.activity",
   "session.deliver",
   "tab.open",
+  "tab.close",
   "engine.lifecycle",
   "notice.event",
   "usage.snapshot",

package/dist/skills/kobe/SKILL.md

@@ -3,7 +3,7 @@ name: kobe
 description: Use when controlling kobe tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell.
 ---
 
-<!-- kobe-skill-version: 8 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
+<!-- kobe-skill-version: 11 — bump in lockstep with KOBE_SKILL_VERSION (src/lib/skill-install.ts). -->
 
 # kobe shell control
 
@@ -31,15 +31,17 @@ lifecycle tracking, and an explicit outcome contract.
   child the user cannot see or manage.
 - Following up on a task you started → `send`; waiting on results →
   `await`; comparing → `collect`; reporting your own verdict → `report`.
-- Messaging another task's agent → `send`. Sent from inside a kobe task,
-  the prompt arrives prefixed `[KOBE PEER] from "<title>" (task <id> —
-  reply: …)`, so the receiver knows who is talking and can answer with the
-  baked-in reply command — peer conversations need no coordinator and no
-  human relay. `--plain` skips the prefix when you truly need a verbatim
-  paste. Received a `[KOBE PEER]` message yourself? Reply with its baked-in
-  command, not by asking the user — and if you haven't loaded this skill or
-  `kobe api schema` yet, do that first (the message points there) before
-  improvising verbs.
+- Messaging another task's agent → `send`, and ONLY `send` — never relay
+  through the user, a side file, or a generic peer channel. Sent from
+  inside a kobe task, the prompt arrives prefixed `[KOBE PEER] from
+  "<title>" (task <id> — load the kobe agent skill FIRST …)`, so the
+  receiver knows who is talking, that this skill is required reading, and
+  how to answer — peer conversations need no coordinator and no human
+  relay. That prefix is the contract: do not strip it with `--plain` for
+  coordination messages (`--plain` is only for a verbatim paste the
+  receiver should treat as content, not conversation). Received a
+  `[KOBE PEER]` message yourself? Load this skill first — required, not
+  optional — then reply with the baked-in command, not by asking the user.
 - `dispatch` stays the dispatcher's verb (deliver-only into an
   already-hosted session; never impersonate the user in someone else's
   terminal).
@@ -91,6 +93,30 @@ kobe api list --pretty
 `.running` means the task's canonical Hosted PTY engine session is alive.
 `send` reuses it or auto-starts it when absent.
 
+## Terminal panes
+
+Split the workspace terminal the user is watching (tmux-style) or open a
+separate command tab — the attached TUI performs it, so this is a no-op
+headless:
+
+```bash
+# Split the focused tab; the pane runs the command via `sh -lc` and
+# closes when it exits. Omit --command for an interactive shell.
+kobe api pane-open --command "btop"
+kobe api pane-open --direction down --command "watch -n1 git status -sb"
+kobe api pane-open --placement tab --title logs --command "tail -f app.log"
+
+# Close panes you opened, by their --title (engine panes are never closed).
+kobe api pane-close --title logs
+```
+
+Defaults: the caller's own task (`$KOBE_TASK_ID`, then the active task),
+`--placement split`, `--direction right`. Alternate right/down to build a
+grid; screen size bounds splitting — a split that would shrink any pane
+below the minimum usable size (20×6 cells) falls back to a tab.
+Panes land in the USER'S live workspace — open them when asked (monitors,
+logs, dashboards), don't scatter panes for work `add`/`fan-out` should own.
+
 ## Lifecycle
 
 | Verb | Purpose |