tmux-ide 2.6.1 → 2.8.0

package/templates/convex.yml

@@ -1,5 +1,7 @@
 name: my-app
 
+before: pnpm install
+
 rows:
   - size: 70%
     panes:

package/templates/default.yml

@@ -1,6 +1,8 @@
 name: my-project
 
-# before: npm install  # optional pre-launch hook
+# before: npm install   # optional pre-launch hook (runs once, before panes start)
+
+# sidebar: true         # inject the fleet nav column (prefix b toggles it live)
 
 rows:
   - size: 70%
@@ -11,10 +13,14 @@ rows:
         command: claude
 
   - panes:
+      # Widget panes render native UI instead of a command:
+      #   type: explorer | changes | preview | config | sidebar
+      - title: Changes
+        type: changes # live git changes — no command, tmux-ide draws it
       - title: Dev Server
         # command: npm run dev
-        # dir: apps/web       # per-pane working directory
-        # env:                 # per-pane environment variables
-        #   PORT: 3000
+        # dir: apps/web          # per-pane working directory
+        # env:                   # per-pane environment variables
+        #   PORT: "3000"
       - title: Shell
-        # focus: true          # give this pane initial focus
+        focus: true # give this pane initial focus

package/templates/go.yml

@@ -1,5 +1,7 @@
 name: my-app
 
+before: go mod download
+
 rows:
   - size: 70%
     panes:
@@ -11,5 +13,7 @@ rows:
   - panes:
       - title: Go
         command: go run .
+      - title: Changes
+        type: changes # live git changes widget
       - title: Shell
         focus: true

package/templates/missions.yml

@@ -1,8 +1,14 @@
 name: project-name
 
+# Ground-truth agent status (working/blocked/done glyphs on the fleet tabs)
+# comes from Claude Code's lifecycle hooks. Wire them once with:
+#   tmux-ide integration install claude
+
 team:
   name: missions
 
+sidebar: true # fleet nav column — jump between agents (toggle: prefix b)
+
 rows:
   - size: 70%
     panes:

package/templates/nextjs.yml

@@ -1,5 +1,7 @@
 name: my-app
 
+before: pnpm install
+
 rows:
   - size: 70%
     panes:
@@ -13,5 +15,7 @@ rows:
   - panes:
       - title: Next.js
         command: pnpm dev
+      - title: Changes
+        type: changes # live git changes widget
       - title: Shell
         focus: true

package/templates/python.yml

@@ -1,5 +1,7 @@
 name: my-app
 
+# before: pip install -r requirements.txt   # or: uv sync / poetry install
+
 rows:
   - size: 70%
     panes:
@@ -11,5 +13,7 @@ rows:
   - panes:
       - title: Server
         # command: uvicorn main:app --reload
+      - title: Changes
+        type: changes # live git changes widget
       - title: Shell
         focus: true

package/templates/skills/backend.md

@@ -25,19 +25,12 @@ You are a backend development specialist.
 
 Your dispatch prompt includes relevant excerpts from the knowledge library (.tmux-ide/library/) and AGENTS.md. Use these for architectural decisions.
 
-## After Completion
+## Reporting
 
-When you finish, the orchestrator will:
+Self-report your state — this drives the fleet status glyphs (see AGENTS.md):
 
-- Notify the lead with your proof and summary
-- Run any configured after-run hooks (e.g., linting)
-- Auto-dispatch the next available task
-- Append your summary to the learnings library
+    tmux set-option -p @agent_state "done:$(date +%s)"   # working|blocked|done|idle
 
-## Completion Protocol
+Then report the result to the lead, and flag anything out of scope:
 
-When done, run:
-tmux-ide task done <TASK_ID> --proof "what changed and how you verified it" --summary "backend outcome"
-
-If you find out-of-scope issues, report them:
-tmux-ide task update <TASK_ID> --discovered-issues "description of issue"
+    tmux-ide send <lead-pane> "what changed, how you verified it, operational concerns"

package/templates/skills/frontend.md

@@ -25,19 +25,12 @@ You are a frontend development specialist.
 
 Your dispatch prompt includes relevant excerpts from the knowledge library (.tmux-ide/library/) and AGENTS.md. Use these for architectural decisions.
 
-## After Completion
+## Reporting
 
-When you finish, the orchestrator will:
+Self-report your state — this drives the fleet status glyphs (see AGENTS.md):
 
-- Notify the lead with your proof and summary
-- Run any configured after-run hooks (e.g., linting)
-- Auto-dispatch the next available task
-- Append your summary to the learnings library
+    tmux set-option -p @agent_state "done:$(date +%s)"   # working|blocked|done|idle
 
-## Completion Protocol
+Then report the result to the lead, and flag anything out of scope:
 
-When done, run:
-tmux-ide task done <TASK_ID> --proof "what changed and how you verified it" --summary "frontend outcome"
-
-If you find out-of-scope issues, report them:
-tmux-ide task update <TASK_ID> --discovered-issues "description of issue"
+    tmux-ide send <lead-pane> "what changed, what you verified, any follow-up risks"

package/templates/skills/general-worker.md

@@ -25,19 +25,12 @@ You are a general-purpose development agent.
 
 You are a general-purpose agent. Your dispatch prompt includes mission, goal, and task context along with relevant library excerpts. Follow the task description closely.
 
-## After Completion
+## Reporting
 
-When you finish, the orchestrator will:
+Self-report your state — this drives the fleet status glyphs (see AGENTS.md):
 
-- Notify the lead with your proof and summary
-- Run any configured after-run hooks (e.g., linting)
-- Auto-dispatch the next available task
-- Append your summary to the learnings library
+    tmux set-option -p @agent_state "done:$(date +%s)"   # working|blocked|done|idle
 
-## Completion Protocol
+Then report the result to the lead, and flag anything out of scope:
 
-When done, run:
-tmux-ide task done <TASK_ID> --proof "what you accomplished" --summary "key learnings for future tasks"
-
-If you discover out-of-scope issues, note them:
-tmux-ide task update <TASK_ID> --discovered-issues "description of issue"
+    tmux-ide send <lead-pane> "what you accomplished, how you verified it, follow-ups"

package/templates/skills/researcher.md

@@ -57,22 +57,17 @@ Surface useful findings early without stalling delivery. Prefer high-signal obse
 
 ## Reporting Protocol
 
-When you finish, record the result on your assigned task:
+Self-report your state — this drives the fleet status glyphs (see AGENTS.md):
 
-`tmux-ide task done <TASK_ID> --proof "findings, evidence, severity, next actions" --summary "short research takeaway"`
+    tmux set-option -p @agent_state "done:$(date +%s)"   # working|blocked|done|idle
 
-Your proof should include:
+Then send your findings to the lead:
+
+    tmux-ide send <lead-pane> "findings, evidence, severity, next actions"
+
+Your report should include:
 
 - What you inspected
 - The most important findings
 - Why they matter
 - The exact next action you recommend
-
-## After Completion
-
-When you finish, the orchestrator will:
-
-- Notify the lead with your proof and summary
-- Run any configured after-run hooks
-- Auto-dispatch the next available task
-- Append your summary to the learnings library

package/templates/skills/reviewer.md

@@ -20,23 +20,14 @@ You are a code review and validation agent.
 3. Run relevant tests or manual checks
 4. Report each assertion's status
 
-## Assertion Reporting
+## Reporting
 
-For each assertion:
-tmux-ide validate assert <ASSERT_ID> --status passing --evidence "what you verified"
-tmux-ide validate assert <ASSERT_ID> --status failing --evidence "what's wrong"
-tmux-ide validate assert <ASSERT_ID> --status blocked --evidence "why it's blocked"
+Self-report your state — this drives the fleet status glyphs (see AGENTS.md):
 
-The orchestrator will detect your results and advance the milestone automatically.
+    tmux set-option -p @agent_state "done:$(date +%s)"   # working|blocked|done|idle
 
-If you find issues beyond the validation contract:
-tmux-ide task update <TASK_ID> --discovered-issues "description of issue"
+Then report the verdict to the lead: for each assertion give its status
+(passing / failing / blocked) and the evidence, plus any issues you found beyond
+the validation contract:
 
-## After Completion
-
-When you finish, the orchestrator will:
-
-- Notify the lead with your proof and summary
-- Run any configured after-run hooks (e.g., linting)
-- Auto-dispatch the next available task
-- Append your summary to the learnings library
+    tmux-ide send <lead-pane> "assertion results with evidence, plus out-of-scope issues"

package/templates/vite.yml

@@ -1,5 +1,7 @@
 name: my-app
 
+before: pnpm install
+
 rows:
   - size: 70%
     panes:
@@ -11,5 +13,7 @@ rows:
   - panes:
       - title: Vite
         command: pnpm dev
+      - title: Changes
+        type: changes # live git changes widget
       - title: Shell
         focus: true

package/packages/daemon/src/tui/mirror/viewer.tsx

@@ -1,166 +0,0 @@
-/**
- * SPIKE viewer — renders ONE live tmux pane inside an OpenTUI app.
- *
- * The proof for the unified-TUI architecture: a control-mode client streams
- * the pane's bytes into a headless terminal (PaneMirror), this app draws the
- * grid, and keystrokes are forwarded back through `send-keys`. tmux stays the
- * multiplexer underneath; tmux-ide owns the screen.
- *
- * Run (needs the repo-root bunfig preload):
- *   bun packages/daemon/src/tui/mirror/viewer.tsx --target <session>
- * Exit with ctrl+q (everything else is forwarded to the pane).
- */
-import { parseArgs } from "node:util";
-import { render, useKeyboard, useTerminalDimensions } from "@opentui/solid";
-import { RGBA } from "@opentui/core";
-import { createSignal, onMount, onCleanup, For } from "solid-js";
-import { ControlModeClient } from "./control-client.ts";
-import { PaneMirror, type MirrorSnapshot } from "./pane-mirror.ts";
-
-const { values } = parseArgs({ options: { target: { type: "string" } } });
-const target = values.target ?? "_spike-target";
-
-// The 16 base ANSI palette colors, mapped for OpenTUI. Higher palette
-// entries fall back to the default foreground — fine for a spike.
-const PALETTE: Array<[number, number, number]> = [
-  [40, 40, 48],
-  [220, 90, 90],
-  [110, 200, 130],
-  [220, 200, 100],
-  [110, 150, 240],
-  [190, 120, 220],
-  [100, 200, 210],
-  [200, 200, 210],
-  [120, 120, 140],
-  [250, 120, 120],
-  [140, 230, 160],
-  [240, 220, 130],
-  [140, 180, 250],
-  [220, 150, 250],
-  [130, 230, 240],
-  [240, 240, 250],
-];
-
-/** Map named OpenTUI key events to tmux send-keys names. */
-const KEYMAP: Record<string, string> = {
-  return: "Enter",
-  backspace: "BSpace",
-  tab: "Tab",
-  escape: "Escape",
-  up: "Up",
-  down: "Down",
-  left: "Left",
-  right: "Right",
-  pageup: "PgUp",
-  pagedown: "PgDn",
-  home: "Home",
-  end: "End",
-  delete: "DC",
-  space: "Space",
-};
-
-render(() => {
-  const dims = useTerminalDimensions();
-  const cols = Math.max(20, dims().width - 2);
-  const rows = Math.max(5, dims().height - 3);
-
-  const mirror = new PaneMirror(cols, rows);
-  const [snap, setSnap] = createSignal<MirrorSnapshot>(mirror.snapshot());
-  const [status, setStatus] = createSignal(`attaching to ${target}…`);
-  let pane = "";
-  let dirty = false;
-
-  const client = new ControlModeClient({
-    attachTarget: target,
-    onOutput: (p, data) => {
-      if (p === pane || pane === "") {
-        mirror.write(data);
-        dirty = true;
-      }
-    },
-    onExit: () => {
-      setStatus("control client exited");
-    },
-  });
-
-  onMount(() => {
-    (async () => {
-      try {
-        await client.start();
-        // Pin our control client's size so tmux lays the window out to match
-        // the mirror grid, then seed with the pane's current content (-e keeps
-        // colors) so we don't start from a blank screen.
-        await client.command(`refresh-client -C ${cols}x${rows}`);
-        const panes = await client.command(`list-panes -t ${target} -F "#{pane_id}"`);
-        pane = panes[0] ?? "";
-        const seed = await client.command(`capture-pane -p -e -t ${pane}`);
-        mirror.write(seed.join("\r\n") + "\r\n");
-        dirty = true;
-        setStatus(`live: ${target} ${pane}  (ctrl+q to quit)`);
-      } catch (e) {
-        setStatus(`error: ${(e as Error).message}`);
-      }
-    })();
-
-    // Coalesce bursts: redraw at most ~30fps instead of per %output event.
-    const timer = setInterval(() => {
-      if (!dirty) return;
-      dirty = false;
-      setSnap(mirror.snapshot());
-    }, 33);
-    onCleanup(() => {
-      clearInterval(timer);
-      client.dispose();
-      mirror.dispose();
-    });
-  });
-
-  useKeyboard((evt) => {
-    if (evt.ctrl && evt.name === "q") {
-      client.dispose();
-      process.exit(0);
-    }
-    if (!pane) return;
-    if (evt.ctrl && evt.name.length === 1) {
-      void client.sendKey(pane, `C-${evt.name}`).catch(() => {});
-      return;
-    }
-    const named = KEYMAP[evt.name];
-    if (named) {
-      void client.sendKey(pane, named).catch(() => {});
-      return;
-    }
-    if (evt.name.length === 1 && !evt.meta && !evt.alt) {
-      void client.sendText(pane, evt.name).catch(() => {});
-    }
-  });
-
-  const fgFor = (idx: number | null): RGBA => {
-    if (idx === null || idx < 0 || idx > 15) return RGBA.fromInts(200, 200, 210, 255);
-    const [r, g, b] = PALETTE[idx]!;
-    return RGBA.fromInts(r, g, b, 255);
-  };
-
-  return (
-    <box flexDirection="column" flexGrow={1} backgroundColor={RGBA.fromInts(18, 18, 24, 255)}>
-      <box paddingLeft={1} flexDirection="row" gap={1}>
-        <text fg={RGBA.fromInts(130, 170, 255, 255)}>tmux-ide mirror</text>
-        <text fg={RGBA.fromInts(120, 120, 140, 255)}>{status()}</text>
-      </box>
-      <box flexDirection="column" flexGrow={1} paddingLeft={1}>
-        <For each={snap().rows}>
-          {(runs) => (
-            <box flexDirection="row">
-              <For each={runs}>{(run) => <text fg={fgFor(run.fg)}>{run.text}</text>}</For>
-            </box>
-          )}
-        </For>
-      </box>
-      <box paddingLeft={1}>
-        <text fg={RGBA.fromInts(120, 120, 140, 255)}>
-          {`cursor ${snap().cursorX},${snap().cursorY} · keys forwarded · ctrl+q quits`}
-        </text>
-      </box>
-    </box>
-  );
-});