neuvikon 0.2.18 → 0.2.19

package/README.md

@@ -55,13 +55,16 @@ pbpaste | npx neuvikon start
 npx neuvikon start --tickets EWWQ-1,EWWQ-2,EWWQ-3 --spawn
 ```
 
-Opens one terminal per ticket (a tmux window if you're already in tmux, an
-iTerm2 or Terminal.app tab on macOS, a Windows Terminal tab on Windows), each
-`cd`'d into this directory. If a coding agent CLI is installed (Claude Code,
-Cursor, Codex) it's launched in each terminal with that ticket's full text as
-its first prompt — same substance a manual paste would give it. With more
-than one installed, you're asked once which to use and that choice is
-remembered (`--agent <name>` overrides it any time). Nothing is tracked
+If [Herdr](https://herdr.dev) is installed, every ticket in the batch lands as
+its own tab in one Herdr workspace instead of separate OS windows — Herdr's
+own UI then shows each agent's live working/blocked/done state. Otherwise it
+opens one terminal per ticket the usual way (a tmux window if you're already
+in tmux, an iTerm2 or Terminal.app tab on macOS, a Windows Terminal tab on
+Windows), each `cd`'d into this directory. Either way, if a coding agent CLI
+is installed (Claude Code, Cursor, Codex) it's launched with that ticket's
+full text as its first prompt — same substance a manual paste would give it.
+With more than one installed, you're asked once which to use and that choice
+is remembered (`--agent <name>` overrides it any time). Nothing is tracked
 automatically, even then: a session only scopes safely once an agent is
 actually running, so the launched agent runs `npx neuvikon start --ticket
 EWWQ-1` itself once it's up, via its rules file, same as a manual paste

package/dist/index.mjs

@@ -2,7 +2,7 @@
 import { chmodSync, closeSync, existsSync, fstatSync, mkdirSync, openSync, readFileSync, readSync, readdirSync, rmSync, writeFileSync } from "node:fs";
 import { homedir } from "node:os";
 import { delimiter, dirname, join } from "node:path";
-import { spawn } from "node:child_process";
+import { execFileSync, spawn } from "node:child_process";
 import { createInterface } from "node:readline/promises";
 //#region src/api.ts
 var ApiError = class extends Error {
@@ -1262,6 +1262,116 @@ async function resolveAgentCli(flags) {
 	return picked;
 }
 //#endregion
+//#region src/herdr.ts
+/** Herdr's `--kind` values for the agents we already know how to pick between. */
+const HERDR_KIND = {
+	"claude-code": "claude",
+	codex: "codex",
+	cursor: "cursor"
+};
+function herdrAvailable() {
+	return isOnPath("herdr");
+}
+/** Every mutating Herdr socket-API command prints one JSON object; a failure prints to stderr instead. */
+function runHerdr(args) {
+	try {
+		const output = execFileSync("herdr", args, {
+			encoding: "utf8",
+			stdio: [
+				"ignore",
+				"pipe",
+				"ignore"
+			]
+		});
+		return JSON.parse(output);
+	} catch {
+		return null;
+	}
+}
+/**
+* Herdr's `agent start` requires a name matching `[a-z][a-z0-9_-]{0,31}`,
+* unique among live agents. A ticket ref (`NS-60`) lowercases straight into
+* that shape, and reusing the ref as the name is what makes `herdr agent
+* get NS-60`-style lookups obvious later.
+*/
+function agentName(ref) {
+	return ref.toLowerCase();
+}
+/**
+* One Herdr workspace per `--spawn` call, one tab per ticket, so a whole
+* batch shows up together in Herdr's own UI — with its live
+* working/blocked/done state per agent — instead of scattered across OS
+* windows. The first successful ref seeds the workspace; every later ref in
+* the same batch adds a tab to it.
+*/
+var HerdrBatch = class {
+	workspaceId = null;
+	openPane(ref, cwd) {
+		if (!this.workspaceId) {
+			const created = runHerdr([
+				"workspace",
+				"create",
+				"--cwd",
+				cwd,
+				"--label",
+				ref,
+				"--focus"
+			]);
+			if (!created) return null;
+			this.workspaceId = created.result.workspace.workspace_id;
+			return created.result.root_pane.pane_id;
+		}
+		return runHerdr([
+			"tab",
+			"create",
+			"--workspace",
+			this.workspaceId,
+			"--cwd",
+			cwd,
+			"--label",
+			ref,
+			"--focus"
+		])?.result.root_pane.pane_id ?? null;
+	}
+	/**
+	* True once this ref has a live Herdr pane — even if starting an agent in
+	* it failed, in which case the pane still exists with the same
+	* print-and-wait fallback a plain spawned terminal gets. False only means
+	* Herdr itself couldn't be reached, and the caller should fall back to
+	* opening a native OS terminal for this ref instead.
+	*/
+	spawn(ref, cwd, agent, ticketText) {
+		const paneId = this.openPane(ref, cwd);
+		if (!paneId) return false;
+		if (agent && ticketText) {
+			if (runHerdr([
+				"agent",
+				"start",
+				agentName(ref),
+				"--kind",
+				HERDR_KIND[agent.id],
+				"--pane",
+				paneId
+			])) {
+				runHerdr([
+					"agent",
+					"prompt",
+					agentName(ref),
+					ticketText
+				]);
+				return true;
+			}
+		}
+		runHerdr([
+			"pane",
+			"run",
+			paneId,
+			`echo 'Ticket: ${ref}' && echo 'Paste it into your agent, or run: npx neuvikon start --ticket ${ref}'`
+		]);
+		return true;
+	}
+};
+//#endregion
 //#region src/terminal.ts
 function shQuote(value) {
 	return `'${value.replace(/'/g, `'\\''`)}'`;
@@ -1416,14 +1526,6 @@ async function fetchTicketText(credentials, ref) {
 		return null;
 	}
 }
-async function buildLaunch(agent, credentials, ref) {
-	const text = await fetchTicketText(credentials, ref);
-	if (!text) return null;
-	return {
-		binary: agent.binary,
-		args: agent.buildArgs(text)
-	};
-}
 /**
 * Opens one terminal per ref and stops there — it deliberately never calls
 * `start` itself. A session file written outside of a running agent has no
@@ -1434,13 +1536,27 @@ async function buildLaunch(agent, credentials, ref) {
 * as its first prompt, but this never calls `start` itself — the agent does,
 * once it's actually running, via the rules file, exactly as if the ticket
 * had been pasted in by hand.
+*
+* Herdr, when installed, wins over a native OS terminal: it's a multiplexer
+* built for exactly this (multiple coding agents, one UI, live
+* working/blocked/done state), so a whole `--tickets` batch lands as one
+* Herdr workspace with one tab per ticket instead of scattered app windows.
 */
 async function spawnMode(flags, credentials, refs) {
 	const cwd = process.cwd();
 	const agent = await resolveAgentCli(flags);
-	info(`Opening ${refs.length} terminal${refs.length === 1 ? "" : "s"} in ${cwd}...`);
+	const herdr = herdrAvailable() ? new HerdrBatch() : null;
+	info(`Opening ${refs.length} terminal${refs.length === 1 ? "" : "s"}${herdr ? " in Herdr" : ` in ${cwd}`}...`);
 	for (const ref of refs) {
-		const launch = agent ? await buildLaunch(agent, credentials, ref) : null;
+		const ticketText = agent ? await fetchTicketText(credentials, ref) : null;
+		if (herdr?.spawn(ref, cwd, agent, ticketText)) {
+			success(`${bold(ref)} — ${agent && ticketText ? `${agent.label} starting in Herdr` : "opened in Herdr"}`);
+			continue;
+		}
+		const launch = agent && ticketText ? {
+			binary: agent.binary,
+			args: agent.buildArgs(ticketText)
+		} : null;
 		const startingLabel = launch && agent ? agent.label : null;
 		if (spawnTerminal({
 			ref,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "neuvikon",
-  "version": "0.2.18",
+  "version": "0.2.19",
   "description": "Tell Neuvikon which ticket your coding agent is working on.",
   "keywords": [
     "neuvikon",