agent-dag 1.33.34 → 1.33.36

package/dist/web/index.html

@@ -5,7 +5,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1" />
     <title>agents-deck</title>
     <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'%3E%3Ctext y='84' font-size='84'%3E%E2%97%89%3C/text%3E%3C/svg%3E" />
-    <script type="module" crossorigin src="/assets/index-w-uUYSqQ.js"></script>
+    <script type="module" crossorigin src="/assets/index-m26PmDnF.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/index-Cpi89XJ8.css">
   </head>
   <body>

package/hook/hook.js

@@ -2,8 +2,8 @@
 // agent-dag hook forwarder. Invoked by Claude Code or Codex CLI as a command
 // hook. Reads stdin (event JSON), tags it with the provider passed via
 // `--provider <name>`, finds the matching agent-dag server via per-workspace
-// discovery files in ~/.claude/agent-dag/, and POSTs the payload. Dead
-// instances are cleaned up.
+// discovery files in <claude config dir>/agent-dag/, and POSTs the payload.
+// Dead instances are cleaned up.
 "use strict";
 
 const fs = require("fs");
@@ -23,7 +23,16 @@ if (process.env.AGENTS_DECK_INTERNAL === "1") process.exit(0);
 
 // Single shared discovery dir — Claude Code and Codex CLI both register here
 // via the installer. Lets one running agent-dag server receive both providers.
-const DIR = path.join(os.homedir(), ".claude", "agent-dag");
+//
+// This has to name the same directory src/server/claude-dir.mjs does, because
+// the installer writes the files read below. It is duplicated rather than
+// imported because this script is copied out of the package and run standalone
+// by the host CLI, with no path back to the module it came from.
+const configOverride = (process.env.CLAUDE_CONFIG_DIR || "").trim();
+const CLAUDE_DIR = configOverride
+  ? path.resolve(configOverride)
+  : path.join(os.homedir(), ".claude");
+const DIR = path.join(CLAUDE_DIR, "agent-dag");
 
 function parseProvider(argv) {
   for (let i = 0; i < argv.length; i++) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-dag",
-  "version": "1.33.34",
+  "version": "1.33.36",
   "description": "Live deck of Claude Code and Codex agents — watch parallel subagents fork, call tools, and return on one calm canvas. Also available as npx ccdeck and npx agent-dag.",
   "type": "module",
   "bin": {

package/src/server/claude-dir.mjs

@@ -0,0 +1,22 @@
+// Where Claude Code keeps its configuration — and therefore where the
+// settings.json our hooks have to be registered in actually lives.
+//
+// CLAUDE_CONFIG_DIR relocates that directory wholesale; it is a replacement for
+// ~/.claude, not an overlay, so on a machine where it is set there is nothing in
+// ~/.claude for Claude Code to read. Writing hook entries there is silent
+// failure of the worst kind: the install reports success, no hook ever fires,
+// and the deck stays empty with no error anywhere to explain it.
+//
+// Every module on the Claude side of the install resolves the directory through
+// here, so the deck can never register its hooks in one file while Claude Code
+// reads another. hook/hook.js repeats the rule inline rather than importing it:
+// it is copied out of the package and run standalone by the host CLI, so it has
+// no way back to this module, but it has to resolve the same directory.
+import { homedir } from "node:os";
+import { join, resolve } from "node:path";
+
+/** Absolute path of the Claude Code config dir: $CLAUDE_CONFIG_DIR or ~/.claude. */
+export function claudeConfigDir() {
+  const override = process.env.CLAUDE_CONFIG_DIR?.trim();
+  return override ? resolve(override) : join(homedir(), ".claude");
+}

package/src/server/index.mjs

@@ -8,6 +8,7 @@ import { extname, join, resolve, dirname as pdirname, sep } from "node:path";
 import { fileURLToPath, pathToFileURL } from "node:url";
 import { dirname } from "node:path";
 import { createInterface } from "node:readline";
+import { claudeConfigDir } from "./claude-dir.mjs";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const PKG_ROOT = resolve(__dirname, "..", "..");
@@ -1283,7 +1284,8 @@ function isProcessAlive(pid) {
 }
 
 async function sweepStaleDiscovery() {
-  const dir = join(homedir(), ".claude", "agent-dag");
+  // Same directory the installer writes and the hooks read — see claude-dir.mjs.
+  const dir = join(claudeConfigDir(), "agent-dag");
   let files;
   try { files = await readdir(dir); } catch { return 0; }
   let removed = 0;

package/src/server/installer.mjs

@@ -1,27 +1,32 @@
 // Idempotent hook installer. Supports two providers:
-//  - "claude"  → ~/.claude/settings.json (Claude Code)
-//  - "codex"   → ~/.codex/hooks.json     (OpenAI Codex CLI)
-// Both providers share the discovery dir at ~/.claude/agent-dag/ so a single
-// running server can receive events from either CLI. Re-runs are safe; entries
-// are tagged with __agent-dag and de-duped.
+//  - "claude"  → $CLAUDE_CONFIG_DIR/settings.json (Claude Code, ~/.claude by default)
+//  - "codex"   → $CODEX_HOME/hooks.json           (OpenAI Codex CLI, ~/.codex by default)
+// Both providers share the discovery dir at <claude config dir>/agent-dag/ so a
+// single running server can receive events from either CLI. Re-runs are safe;
+// entries are tagged with __agent-dag and de-duped.
 import { readFile, writeFile, mkdir, copyFile, unlink, rename, open, stat, chmod } from "node:fs/promises";
 import { existsSync } from "node:fs";
 import { homedir } from "node:os";
 import { join, resolve, dirname } from "node:path";
 import { setTimeout as delay } from "node:timers/promises";
 import { fileURLToPath } from "node:url";
+import { claudeConfigDir } from "./claude-dir.mjs";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const PKG_ROOT = resolve(__dirname, "..", "..");
 
 const HOME = homedir();
-const CLAUDE_DIR = join(HOME, ".claude");
+// Honours CLAUDE_CONFIG_DIR, exactly as CODEX_DIR honours CODEX_HOME below.
+// Without it the hooks land in a settings.json Claude Code never opens.
+const CLAUDE_DIR = claudeConfigDir();
 const CODEX_DIR = process.env.CODEX_HOME
   ? resolve(process.env.CODEX_HOME)
   : join(HOME, ".codex");
 
 // Single shared discovery dir — both providers' hook scripts post here so one
-// running agent-dag server can match either ecosystem's events.
+// running agent-dag server can match either ecosystem's events. It follows the
+// Claude config dir, so hook/hook.js has to resolve that dir the same way: it
+// reads what this writes, and a disagreement means the hooks find no server.
 const AGENT_DAG_DIR = join(CLAUDE_DIR, "agent-dag");
 
 const CLAUDE_EVENTS = [

package/src/server/sound-hook.mjs

@@ -15,10 +15,11 @@ import { existsSync } from "node:fs";
 import { join, dirname } from "node:path";
 import { homedir } from "node:os";
 import { fileURLToPath } from "node:url";
+import { claudeConfigDir } from "./claude-dir.mjs";
 import { readSettingsForWrite, writeFileAtomic } from "./installer.mjs";
 
 const PKG_ROOT      = join(dirname(fileURLToPath(import.meta.url)), "..", "..");
-const CLAUDE_DIR    = process.env.CLAUDE_CONFIG_DIR ?? join(homedir(), ".claude");
+const CLAUDE_DIR    = claudeConfigDir();
 const SETTINGS_PATH = join(CLAUDE_DIR, "settings.json");
 const INSTALL_DIR   = join(CLAUDE_DIR, "agent-dag");
 const NOTIFY_PATH   = join(INSTALL_DIR, "notify.js");