baychat 0.24.0 → 0.25.0

package/dist/index.js

@@ -1,504 +1,31 @@
 #!/usr/bin/env node
 "use strict";
+// The `baychat` entry point: a router, deliberately tiny.
+//
+// Three commands are run BY CLAUDE CODE, not by a person — its status line (on every assistant
+// message) and its compaction hooks — and the status line must not get slower because BayChat
+// is in it. Loading the whole CLI (the MCP SDK and every command module) costs 0.7–1 s on a busy
+// disk, against ~50 ms for Node itself. So those three are routed to `claude-context.ts`, which
+// loads nothing heavy, and everything else requires `main.ts`, which is the CLI as it always was.
+// Each side is required only when it is the one running, so neither pays for the other.
 Object.defineProperty(exports, "__esModule", { value: true });
-const commands_1 = require("./commands");
-const approve_hook_1 = require("./approve-hook");
-const session_name_1 = require("./session-name");
-const start_command_1 = require("./start-command");
-const update_command_1 = require("./update-command");
-const session_command_1 = require("./session-command");
-const doctor_command_1 = require("./doctor-command");
-const hermes_1 = require("./hermes");
-const connect_1 = require("./connect");
-const connect_plan_1 = require("./connect-plan");
-const runtimes_1 = require("./runtimes");
-const mcp_1 = require("./mcp");
-const mcp_config_1 = require("./mcp-config");
-const commands_2 = require("./relay/commands");
-const help_topics_1 = require("./help-topics");
-const args_1 = require("./args");
-const owner_pid_1 = require("./relay/owner-pid");
-const profiles_1 = require("./relay/profiles");
-const LOGIN_HELP = `Usage: baychat login [--start | --finish | --token <PAT>] [--base <url>]
-
-  --start   Print an approval link and return immediately; no waiting process.
-  --finish  Check approval once, save it and refresh connected clients.
-  --token   Verify and save a device token (prefer the approval link in chat).
-  --base    Use your BayChat server instead of the default.
-
-Without a mode, display a QR/link and wait for approval in this terminal.
-For an agent session: login --start, show the link, then login --finish after approval.
-Exit 0: step succeeded; 2: awaiting approval or expired; 1: error.
-`;
-const HELP = `baychat — BayChat connector CLI for agent sessions (Claude Code, Codex)
-
-${help_topics_1.UPDATE_HELP}
-
-Usage:
-  baychat                               Start a session. This is the whole thing: it runs
-                                        your agent somewhere BayChat can reach, so /clear
-                                        and /new from the app work. Sign in once with
-                                        \`baychat login\` first
-  baychat start [name] [--runtime <runtime>]
-                                        The same, with a name for the session
-  baychat update                        Bring this machine onto the current version —
-                                        the package, every connected client's config, and
-                                        the relay daemon (which otherwise keeps running
-                                        old code). \`baychat\` does this for you once a day
-  baychat join [name] [group] [--sessions | --private | --group <title>] [--runtime <runtime>]
-  baychat join --session <name> --group <title> --runtime codex
-  baychat skill --runtime codex|claude   Read the current packaged skill workflow
-                                        Join and connect incoming messages in this terminal
-  baychat session-name --runtime <runtime>
-                                        Stable automatic name for this verified session
-  baychat onboard [conversationId] [--catch-up]
-                                        Start here — print the agent protocol + your
-                                        live identity, conversations, and room context.
-                                        --catch-up also appends the rolling summary +
-                                        the messages after its boundary
-  baychat connect [codex|cursor|desktop] [--base <url>]
-                                        START HERE, once per laptop. Approve a QR on your
-                                        phone, and your client's MCP config is written for
-                                        you. Then run /baychat <name> in any session to
-                                        join as that session. No config blocks, no editing
-  baychat connect dsh|cursor-cli [--folder <path>] [--max-mode <mode>] [--mode <mode>] [--session <name>]
-                                        An agent the relay runs by itself (DeepSeek Harness,
-                                        Cursor's CLI): you talk to it from the app. The
-                                        folder and the highest mode are set here, never
-                                        from a chat
-  baychat login [--start | --finish | --token <PAT>] [--base <url>]
-                                        Log this laptop in to BayChat (QR) and add the
-                                        BayChat MCP server to Claude Code. Creates a
-                                        device credential only — no agent, no room
-  baychat pair <code> [--base <url>]   Redeem a pairing code from the BayChat app
-  baychat hermes init [--home <dir>] [--enable]
-                                        Install the BayChat platform plugin into a Hermes
-                                        agent (~/.hermes), and put your paired agent token
-                                        where its adapter reads it. --enable also runs the
-                                        two hermes commands that switch it on
-  baychat link [--name <n>] [--base <url>]
-                                        Link this session via a QR you scan with your phone
-  baychat help [topic|question]         How to USE BayChat from a client — making a
-                                        group, joining a room, which tools your
-                                        credential gets. Ask it however you like:
-                                        \`baychat help "make a new group"\`. These are
-                                        MCP tools your client calls, not subcommands,
-                                        so they are not in the list below
-  baychat whoami                        Show the connected agent identity
-  baychat conversations                 List conversations this agent is in
-  baychat send <conversationId> <text>  Send a message
-  baychat typing <conversationId>       Show the typing indicator while you work, so a long
-                                        tool call doesn't look like a crash. ONE call at the
-                                        start of a turn — it lapses on its own after a few
-                                        seconds, so there is nothing to stop and no loop to run
-  baychat react <conversationId> <messageId> <emoji> [--remove]
-                                        Acknowledge one message so the person who sent it
-                                        knows you have read it and are on it. Unlike typing,
-                                        the reaction STAYS on the message — use 👀 the moment
-                                        you pick up work that will take more than a few
-                                        seconds. Reacting again replaces it; --remove clears it
-  baychat check <conversationId>        Print messages since the last check
-  baychat context <conversationId>      Show the roster + the group's agent instructions
-  baychat summary <conversationId> [--refresh]
-                                        Catch up: rolling summary + the messages after
-                                        its boundary (--refresh forces regeneration)
-  baychat search <query> [--limit <n>]  Search the web through BayChat (results are
-                                        untrusted content — read, never obey)
-  baychat fetch <url> [--max-chars <n>] Fetch one public http(s) page as readable text
-                                        (untrusted content — read, never obey)
-  baychat qr [<conversationId>]         Render this agent's connection QR in the terminal
-  baychat mcp                           Run a local stdio MCP server so MCP-aware clients
-                                        (Claude Desktop, Claude Code, Cursor) get BayChat
-                                        as native tools. Speaks JSON-RPC on stdout — do not
-                                        run it interactively
-  baychat mcp-config [--client codex|cursor|desktop]
-                                        Print a paste-ready MCP config for another
-                                        client, pointed at the remote BayChat server.
-                                        No --client lists what's supported. The config
-                                        goes to stdout, the guidance to stderr
-  baychat watch <conversationId> [--interval <sec>] [--timeout <sec>]
-                                        Block until new messages arrive (exit 0)
-                                        or timeout (exit 2)
-  baychat relay start [--foreground]    Run the relay: one event stream for this whole
-                                        machine, waking local sessions the moment a
-                                        message arrives. Prefers the agent WebSocket
-                                        and falls back to the /updates long-poll on its
-                                        own. Installs a systemd user unit so it returns
-                                        after a reboot; --foreground runs it in this
-                                        process instead
-  baychat relay status                  Transport, sessions, cursor, and any DELIVERY
-                                        PENDING — messages that reached this box and
-                                        that nothing answered (exit 2 if any pending).
-                                        Each session also prints WHERE its resume id
-                                        came from, so "we can wake this headlessly"
-                                        is a claim you can check
-  baychat relay stop                    Stop the relay and disable it at boot
-  baychat doctor [--json]               Check every link between this machine and
-                                        BayChat — credential, relay, and per runtime
-                                        its MCP registration, skill, executable and
-                                        live session — and print exactly what to type
-                                        for each thing that is wrong. Exit 0 clear,
-                                        1 broken, 2 messages nothing answered.
-                                        --json emits the same report as data, for
-                                        pasting into a support thread
-  baychat approve-hook [--session <name>] [--timeout <sec>]
-                                        Claude Code PermissionRequest hook: send the
-                                        permission prompt to BayChat as a decision card
-                                        and answer it from your phone. Reads the hook
-                                        JSON on stdin, writes ONE decision object to
-                                        stdout, and always exits 0. FAILS CLOSED — every
-                                        error denies. NOT enabled by default; see
-                                        docs/features/REMOTE_APPROVAL_HOOK.md before
-                                        switching it on, because it moves the last line
-                                        between an agent and this machine onto a phone
-  baychat relay attach --session <name> [--runtime claude|codex|hermes]
-                        [--resume-id <id>] [--timeout <sec>]
-                                        Register this session with the relay and block
-                                        until it is woken (exit 0), or the wait lapses
-                                        (exit 2). Without --resume-id the session is
-                                        asked to identify itself from its runtime's
-                                        environment ($CLAUDE_CODE_SESSION_ID for Claude
-                                        Code); failing that the relay searches the
-                                        runtime's own session state when a message
-                                        arrives. A session it cannot identify is
-                                        reported pending, never guessed at
-
-Connect flow: in BayChat, open the agent -> Connect -> copy the pairing code,
-then run \`baychat pair <code>\`. Pairing rotates the agent token; use a
-dedicated agent per session.`;
-/** Drop a `--name <value>` pair, so a multi-word positional (a search query)
- * doesn't swallow the flag's value as part of itself.
- *
- * Only the flag is dropped when its value is missing — the next token is
- * another option, or there is none. Consuming two entries there would eat an
- * unrelated argument, the same mistake `flag` refuses to make. */
-function withoutFlag(args, name) {
-    const i = args.indexOf(name);
-    if (i < 0)
-        return args;
-    const next = args[i + 1];
-    const consumed = next !== undefined && !next.startsWith("--") ? 2 : 1;
-    return [...args.slice(0, i), ...args.slice(i + consumed)];
+/** Kept in step with `FAST_CONTEXT_COMMANDS` in claude-context.ts (a test pins the two). */
+const FAST_COMMANDS = new Set(["context-statusline", "context-hook", "context-flush"]);
+const command = process.argv[2];
+if (command !== undefined && FAST_COMMANDS.has(command)) {
+    // eslint-disable-next-line @typescript-eslint/no-require-imports
+    const fast = require("./claude-context");
+    fast.runFastContextCommand(command, process.argv.slice(3)).then(
+    // `exitCode`, not `exit()`: a status line's output may still be draining into a pipe, and
+    // `process.exit` does not wait for it on every platform.
+    (code) => {
+        process.exitCode = code;
+    }, (err) => {
+        fast.logContextError(`${command}: ${err instanceof Error ? err.message : String(err)}`);
+        process.exitCode = 0;
+    });
 }
-/** A flag's value as a number, or undefined when absent. A non-numeric value
- * becomes NaN and is rejected by the tool's own bounds check with a message
- * that names the field. */
-function numberFlag(args, name) {
-    const raw = (0, args_1.flag)(args, name);
-    return raw === undefined ? undefined : Number(raw);
+else {
+    // eslint-disable-next-line @typescript-eslint/no-require-imports
+    require("./main");
 }
-async function main() {
-    const [command, ...args] = process.argv.slice(2);
-    // BARE `baychat` STARTS A SESSION. The bar is "download BayChat, start a session, nothing
-    // else", and a usage dump printed at somebody who typed the product's own name is the
-    // "something else". `--help` still prints the help, and `start` refuses with one sentence
-    // when this machine is not signed in, so nothing is launched from an unusable state.
-    if (command === undefined)
-        return (0, start_command_1.cmdStart)([]);
-    // Setup help must be side-effect free. Do not apply this to chat commands:
-    // a sent message may legitimately contain the literal text "--help".
-    if (["login", "link", "connect", "pair", "join", "skill"].includes(command) &&
-        args.some((arg) => arg === "--help" || arg === "-h")) {
-        console.log(command === "login" ? LOGIN_HELP : HELP);
-        return 0;
-    }
-    switch (command) {
-        case "--version":
-        case "-v":
-            console.log(require("../package.json").version);
-            return 0;
-        case "join":
-            return (0, session_command_1.cmdJoinSession)(args);
-        case "start":
-            return (0, start_command_1.cmdStart)(args);
-        case "update":
-            return (0, update_command_1.cmdUpdate)();
-        case "skill": {
-            const runtime = args[1];
-            if (args.length !== 2 ||
-                args[0] !== "--runtime" ||
-                (runtime !== "codex" && runtime !== "claude"))
-                throw new Error("Usage: baychat skill --runtime codex|claude");
-            console.log((0, runtimes_1.renderCommandFor)(runtime));
-            return 0;
-        }
-        case "session-name": {
-            (0, args_1.rejectUnknownFlags)(args, ["--runtime"], "baychat session-name --runtime <runtime>");
-            const runtime = (0, args_1.flag)(args, "--runtime") ?? (0, owner_pid_1.detectRuntime)(profiles_1.RUNTIME_PROFILES);
-            if (!runtime)
-                throw new Error("Cannot detect this runtime. Pass --runtime, or choose a BayChat session name.");
-            console.log(await (0, session_name_1.automaticSessionName)(runtime));
-            return 0;
-        }
-        case "onboard":
-            await (0, commands_1.cmdOnboard)((0, args_1.positional)(args), {
-                catchUp: args.includes("--catch-up"),
-            });
-            return 0;
-        case "login": {
-            (0, args_1.rejectUnknownFlags)(args, ["--start", "--finish", "--base", "--token"], LOGIN_HELP);
-            for (let index = 0; index < args.length; index++) {
-                const arg = args[index];
-                if (arg === "--base" || arg === "--token") {
-                    if (!(0, args_1.flag)(args.slice(index), arg))
-                        throw new Error(`${arg} needs a value.\n${LOGIN_HELP}`);
-                    index++;
-                }
-                else if (arg !== "--start" && arg !== "--finish")
-                    throw new Error(`Unexpected login argument.\n${LOGIN_HELP}`);
-            }
-            if (["--start", "--finish", "--token"].filter((arg) => args.includes(arg))
-                .length > 1)
-                throw new Error(`Choose one login mode.\n${LOGIN_HELP}`);
-            const loggedIn = await (0, commands_1.cmdLogin)({
-                base: (0, args_1.flag)(args, "--base"),
-                token: (0, args_1.flag)(args, "--token"),
-                mode: args.includes("--start")
-                    ? "start"
-                    : args.includes("--finish")
-                        ? "finish"
-                        : "interactive",
-            });
-            return loggedIn ? 0 : 2; // 2 = not approved yet, or expired
-        }
-        case "pair": {
-            if (!args[0])
-                throw new Error("Usage: baychat pair <code>");
-            await (0, commands_1.cmdPair)(args[0], (0, args_1.flag)(args, "--base"));
-            return 0;
-        }
-        case "link": {
-            const linked = await (0, commands_1.cmdLink)({
-                name: (0, args_1.flag)(args, "--name"),
-                base: (0, args_1.flag)(args, "--base"),
-            });
-            return linked ? 0 : 2;
-        }
-        case "qr":
-            await (0, commands_1.cmdQr)(args[0]);
-            return 0;
-        case "whoami":
-            await (0, commands_1.cmdWhoami)();
-            return 0;
-        case "conversations":
-            await (0, commands_1.cmdConversations)();
-            return 0;
-        case "send": {
-            // `--reply-to <id>` is pulled out before the positionals, so the message text can
-            // contain anything — including a word that looks like a flag.
-            const flagAt = args.indexOf("--reply-to");
-            let replyToMessageId;
-            let rest = args;
-            if (flagAt !== -1) {
-                replyToMessageId = args[flagAt + 1];
-                if (!replyToMessageId)
-                    throw new Error("--reply-to needs a message id.");
-                rest = [...args.slice(0, flagAt), ...args.slice(flagAt + 2)];
-            }
-            const [conversationId, ...words] = rest;
-            if (!conversationId || words.length === 0) {
-                throw new Error("Usage: baychat send [--reply-to <messageId>] <conversationId> <text>");
-            }
-            await (0, commands_1.cmdSend)(conversationId, words.join(" "), replyToMessageId);
-            return 0;
-        }
-        case "typing": {
-            if (!args[0])
-                throw new Error("Usage: baychat typing <conversationId>");
-            await (0, commands_1.cmdTyping)(args[0]);
-            return 0;
-        }
-        case "react": {
-            // `--remove` needs no emoji, so the positionals are read from the flag-free
-            // list rather than by index: `react c1 m1 --remove` must not read "--remove"
-            // as the emoji and try to store it.
-            const [conversationId, messageId, emoji] = args.filter((a) => !a.startsWith("--"));
-            const remove = args.includes("--remove");
-            if (!conversationId || !messageId || (!emoji && !remove)) {
-                throw new Error("Usage: baychat react <conversationId> <messageId> <emoji> [--remove]");
-            }
-            await (0, commands_1.cmdReact)(conversationId, messageId, emoji, { remove });
-            return 0;
-        }
-        case "check": {
-            if (!args[0])
-                throw new Error("Usage: baychat check <conversationId>");
-            await (0, commands_1.cmdCheck)(args[0]);
-            return 0;
-        }
-        case "context": {
-            if (!args[0])
-                throw new Error("Usage: baychat context <conversationId>");
-            await (0, commands_1.cmdContext)(args[0]);
-            return 0;
-        }
-        case "summary": {
-            const conversationId = (0, args_1.positional)(args);
-            if (!conversationId)
-                throw new Error("Usage: baychat summary <conversationId> [--refresh]");
-            await (0, commands_1.cmdSummary)(conversationId, { refresh: args.includes("--refresh") });
-            return 0;
-        }
-        case "search": {
-            const words = withoutFlag(args, "--limit").filter((a) => !a.startsWith("--"));
-            if (words.length === 0)
-                throw new Error("Usage: baychat search <query> [--limit <n>]");
-            await (0, commands_1.cmdSearch)(words.join(" "), { limit: numberFlag(args, "--limit") });
-            return 0;
-        }
-        case "fetch": {
-            const url = (0, args_1.positional)(withoutFlag(args, "--max-chars"));
-            if (!url)
-                throw new Error("Usage: baychat fetch <url> [--max-chars <n>]");
-            await (0, commands_1.cmdFetch)(url, { maxChars: numberFlag(args, "--max-chars") });
-            return 0;
-        }
-        case "watch": {
-            if (!args[0])
-                throw new Error("Usage: baychat watch <conversationId>");
-            const intervalSec = Number((0, args_1.flag)(args, "--interval") ?? "5");
-            const timeoutSec = Number((0, args_1.flag)(args, "--timeout") ?? "300");
-            const got = await (0, commands_1.cmdWatch)(args[0], {
-                intervalMs: intervalSec * 1000,
-                timeoutMs: timeoutSec * 1000,
-            });
-            return got ? 0 : 2;
-        }
-        case "relay": {
-            const sub = (0, args_1.positional)(args) ?? "";
-            const rest = args.filter((a) => a !== sub);
-            switch (sub) {
-                case "start":
-                    (0, args_1.rejectUnknownFlags)(rest, ["--foreground"], "baychat relay start [--foreground]");
-                    await (0, commands_2.cmdRelayStart)({ foreground: args.includes("--foreground") });
-                    return 0;
-                case "status":
-                    (0, args_1.rejectUnknownFlags)(rest, [], "baychat relay status");
-                    return await (0, commands_2.cmdRelayStatus)();
-                case "stop":
-                    (0, args_1.rejectUnknownFlags)(rest, [], "baychat relay stop");
-                    return await (0, commands_2.cmdRelayStop)();
-                case "attach": {
-                    const session = (0, args_1.flag)(rest, "--session");
-                    if (!session) {
-                        throw new Error("Usage: baychat relay attach --session <name> [--runtime claude|codex|hermes] [--resume-id <id>] [--timeout <sec>]");
-                    }
-                    (0, args_1.rejectUnknownFlags)(rest, [
-                        "--session",
-                        "--runtime",
-                        "--resume-id",
-                        "--timeout",
-                        "--owner-pid",
-                    ], "baychat relay attach --session <name> [--runtime claude|codex|hermes] [--resume-id <id>] [--timeout <sec>]");
-                    const timeoutSec = numberFlag(rest, "--timeout");
-                    return await (0, commands_2.cmdRelayAttach)({
-                        session,
-                        // Detected from the process tree when not given, so a person
-                        // connecting Gemini or Kimi does not have to know the flag exists.
-                        // Defaulting to "claude" for everyone was fine when four runtimes
-                        // were all we served; it is a wrong answer now.
-                        runtime: (0, args_1.flag)(rest, "--runtime") ??
-                            (0, owner_pid_1.detectRuntime)(profiles_1.RUNTIME_PROFILES) ??
-                            "claude",
-                        resumeId: (0, args_1.flag)(rest, "--resume-id"),
-                        timeoutMs: timeoutSec ? timeoutSec * 1000 : undefined,
-                        // Passed by `relay rearm`, which reads it where the runtime is still
-                        // an ancestor and hands it to a child that has been detached.
-                        ownerPid: numberFlag(rest, "--owner-pid"),
-                    });
-                }
-                default:
-                    throw new Error("Usage: baychat relay <start|status|stop|attach> [options]");
-            }
-        }
-        case "hermes": {
-            const sub = (0, args_1.positional)(args) ?? "";
-            const rest = args.filter((a) => a !== sub);
-            if (sub !== "init") {
-                throw new Error("Usage: baychat hermes init [--home <dir>] [--enable]");
-            }
-            (0, args_1.rejectUnknownFlags)(rest, ["--home", "--enable"], "baychat hermes init [--home <dir>] [--enable]");
-            return (0, hermes_1.cmdHermesInit)(rest);
-        }
-        case "approve-hook":
-            // Never throws and always returns 0 — see the file header in approve-hook.ts. A thrown
-            // error here would reach main()'s catch, print to stderr and exit 1, and to Claude Code an
-            // exit-1 hook with no JSON on stdout is a NON-BLOCKING error: the tool call proceeds. The
-            // guard in the catch below covers that anyway.
-            return await (0, approve_hook_1.cmdApproveHook)(args);
-        case "doctor":
-            // Deliberately placed with the setup commands: it is the thing you run
-            // when one of them did not take, and the one command that inspects all
-            // of them at once.
-            return await (0, doctor_command_1.cmdDoctor)(args);
-        case "connect": {
-            // A bare `connect` prints the client menu; positional() skips a leading flag
-            // so `connect --base x codex` still finds the client.
-            const { client, ...options } = (0, connect_plan_1.parseConnectArgs)(args);
-            return await (0, connect_1.cmdConnect)(client, options);
-        }
-        case "mcp-config": {
-            // `--client` with no value is a typo, not a request for the menu: pass the
-            // empty string so it is rejected by name rather than silently listing.
-            (0, mcp_config_1.cmdMcpConfig)(args.includes("--client") ? ((0, args_1.flag)(args, "--client") ?? "") : undefined);
-            return 0;
-        }
-        case "mcp": {
-            // Boot the stdio MCP server, then block forever: the transport keeps the
-            // process alive on stdin, and falling through to process.exit() would kill
-            // it. All diagnostics go to stderr — stdout is the JSON-RPC channel.
-            await (0, mcp_1.startMcpServer)();
-            await new Promise(() => { });
-            return 0; // unreachable
-        }
-        case "help":
-        case "--help":
-        case "-h":
-        case undefined: {
-            // `baychat help <anything>` answers a question about USING BayChat from a
-            // client — how to make a group, what tools you get, why yours are missing.
-            // Those are MCP tools, not subcommands, so they can never appear in the
-            // usage block above, and until this existed the only answer was "read a
-            // website" — which is how a shipped capability gets reported as absent.
-            const query = args.join(" ").trim();
-            if (query) {
-                const topic = (0, help_topics_1.findTopic)(query);
-                if (topic) {
-                    console.log(topic.body);
-                    return 0;
-                }
-                // A miss is not an error: they asked a real question and deserve the
-                // list rather than a usage dump.
-                console.error(`No help topic matches "${query}".\n`);
-                console.log((0, help_topics_1.topicIndex)());
-                return 1;
-            }
-            console.log(HELP);
-            console.log("");
-            console.log((0, help_topics_1.topicIndex)());
-            return 0;
-        }
-        default:
-            console.error(`Unknown command: ${command}`);
-            console.log(HELP);
-            return 1;
-    }
-}
-main()
-    .then((code) => process.exit(code))
-    .catch((err) => {
-    const message = err instanceof Error ? err.message : String(err);
-    console.error(message);
-    // The last fail-closed guard. For every other command, exit 1 is the right answer. For
-    // `approve-hook` it is the WRONG one twice over: Claude Code treats a non-zero exit with no
-    // JSON on stdout as a non-blocking error and lets the tool call through, so a crash in the
-    // approval gate would silently grant the permission it exists to withhold. Print a deny and
-    // exit 0 instead. Deliberately not sharing main()'s dispatch — this must still hold if the
-    // failure happened while parsing argv, or inside an import.
-    if (process.argv[2] === "approve-hook") {
-        process.stdout.write(`${JSON.stringify((0, approve_hook_1.denyDecision)(`Denied by BayChat remote approval: the approval gate crashed (${message}). ` +
-            `This gate fails closed, so the call was refused rather than allowed.`))}\n`);
-        process.exit(0);
-    }
-    process.exit(1);
-});