botmux 2.51.0 → 2.51.1

package/dist/core/dispatch.d.ts

@@ -0,0 +1,163 @@
+/**
+ * Phase 0 keystone — `botmux dispatch` pure core.
+ *
+ * The orchestrator (主 bot) splits a big project into sub-projects and assigns
+ * each to a small group of bots (often a coder + a reviewer). To open a
+ * sub-project it seeds a fresh Lark thread and @-mentions the assigned bots so
+ * each spawns its own thread-scoped session (botmux's existing one-thread-one-
+ * session routing; bot→bot @ inside a thread is ungated — see
+ * event-dispatcher.ts decideRouting + the chat-scope-only foreign-bot gate).
+ *
+ * This module is the pure, I/O-free core: parse the `--bot` specs and build the
+ * two messages (a top-level seed = the thread root, and the threaded kickoff
+ * that @-mentions the bots with their roles + the brief). The CLI shell
+ * (cli.ts) performs the actual sendMessage + replyMessage.
+ */
+export interface DispatchBot {
+    /** open_id as seen by the orchestrator's app (from <available_bots>). */
+    openId: string;
+    /** Display name, for readable @ rendering / division-of-labor lines. */
+    name?: string;
+    /** Short role label, e.g. "coder" / "reviewer". */
+    role?: string;
+}
+export type PostNode = {
+    tag: 'text';
+    text: string;
+} | {
+    tag: 'at';
+    user_id: string;
+};
+export type PostParagraph = PostNode[];
+export interface DispatchMessages {
+    /** Plain-text seed (the thread root) — the human-visible "this sub-project exists" header. */
+    seedText: string;
+    /** Lark 'post' content (paragraphs of nodes) for the threaded kickoff. */
+    threadContent: PostParagraph[];
+    /** open_ids @-mentioned in the kickoff — the bots that will be triggered. */
+    mentionedOpenIds: string[];
+}
+/**
+ * Parse a `--bot` spec `openId[:name[:role]]` into a {@link DispatchBot}.
+ * Mirrors the `--mention "open_id:Display Name"` convention, with an optional
+ * trailing role segment.
+ */
+export declare function parseDispatchBotSpec(raw: string): DispatchBot;
+/**
+ * Build the seed + threaded-kickoff messages for one sub-project dispatch.
+ * Throws when there is no title or no bot to dispatch to.
+ */
+export declare function buildDispatchMessages(input: {
+    title: string;
+    brief: string;
+    bots: DispatchBot[];
+}): DispatchMessages;
+/**
+ * Build the "repo prime" message: a `/repo <path>` command @-mentioning the
+ * target bots, sent as a **plain text message** — exactly like a human typing
+ * "@bot /repo <path>". Sent as the first message into a freshly-seeded thread,
+ * it makes each sub-bot's daemon resolve the working dir and spawn its CLI
+ * **idle** (no repo-selection card, no manual "直接开始" click) — i.e. standby.
+ *
+ * Why text (not a structured `post`): the receiving daemon parses a text
+ * message's @ via `resolveMentions` (the same clean path a human @ goes
+ * through), whereas a `post`'s at/text nodes go through `renderPostNode`, which
+ * drops the `/repo` argument in the live event — see the dispatch debugging
+ * notes. `/repo` is an existing botmux command, so this needs no receiving-side
+ * change. The `<at>` tags come first so that, once the receiving daemon strips
+ * leading mentions, it sees `/repo <path>` as the command.
+ */
+export declare function buildRepoPrimeText(input: {
+    path: string;
+    bots: DispatchBot[];
+}): {
+    text: string;
+    mentionedOpenIds: string[];
+};
+/**
+ * Build the report-back message a dispatched sub-bot sends to its orchestrator.
+ *
+ * In 多话题协作模式 a sub-bot must NOT @ the orchestrator in its own sub-topic —
+ * that thread has no orchestrator session, so the orchestrator's daemon would
+ * spawn a fresh, context-less one. Instead `botmux report` sends this content
+ * **into the orchestrator's own thread** (recorded by `botmux dispatch`),
+ * @-mentioning the orchestrator so its existing, context-rich session is the one
+ * that wakes up. This is the pure content builder; cli.ts resolves the coords
+ * and performs the reply.
+ *
+ * The @ stays on the first line so the mention renders next to the headline;
+ * any further lines become their own paragraphs (Lark 'post' shape).
+ */
+export declare function buildReportContent(input: {
+    orchOpenId: string;
+    content: string;
+}): PostParagraph[];
+/**
+ * Footgun guard for the orchestrator→sub-bot direction. A dispatched sub-bot's
+ * session lives **inside its sub-topic**, so @-mentioning it from the main chat
+ * (e.g. `botmux send --mention <sub-bot>`) doesn't reach that session — it
+ * spawns a fresh, context-less one in the chat (the mirror of the report-back
+ * problem). To talk to a sub-bot the orchestrator must send INTO its sub-topic
+ * (`botmux dispatch --into <seed> --bot <sub-bot>`).
+ *
+ * Given the dispatch registry (seed → {orchChatId, bots}) and the set of seeds
+ * whose sub-topic is still active, return the sub-topic seed to redirect to when
+ * `mentionOpenId` is a sub-bot dispatched into an active topic of `chatId`;
+ * otherwise null. Only fires for live topics so stale entries don't block sends.
+ */
+export declare function findSubBotTopic(input: {
+    mentionOpenId: string;
+    chatId: string;
+    registry: Record<string, {
+        orchChatId?: string;
+        bots?: string[];
+    }>;
+    activeSeeds: Set<string>;
+}): string | null;
+/**
+ * The footgun check shared by `botmux send`'s explicit-mention guard AND its
+ * prose `@Name` auto-injection: returns the sub-topic seed if `mentionOpenId` is
+ * a dispatched sub-bot in an active topic that is NOT reachable in the current
+ * conversation (so @-ing it here would spawn a context-less session), else null.
+ *
+ * The bot I'm replying to (`quoteTargetSenderOpenId`) is reachable right here, so
+ * it's never treated as off-topic — that's the boundary that stops the guard from
+ * blocking a normal reply to a bot conversing with me. Callers block (explicit
+ * --mention) or drop (prose injection) on a non-null result, and skip the whole
+ * check under `--anyway`.
+ */
+export declare function offTopicSubBotTopic(input: {
+    mentionOpenId: string;
+    quoteTargetSenderOpenId?: string;
+    chatId: string;
+    registry: Record<string, {
+        orchChatId?: string;
+        bots?: string[];
+    }>;
+    activeSeeds: Set<string>;
+}): string | null;
+/**
+ * Decide which names of a candidate bot are eligible for prose `@Name`
+ * auto-mention injection in `botmux send`.
+ *
+ * The fan-out bug: a bot writes "@Codex review" in its message; the injector
+ * matches each bot by **botName OR cliId**, and the cliId ("codex") is a shared
+ * *type* alias — so "@Codex" matches every codex-type bot (Codex分身, Codex二号分身,
+ * ttadk(codex), aiden x codex…) and pulls them ALL into the topic, each spawning
+ * a session and replying.
+ *
+ * Fix: the unique `botName` is always eligible (so first-time @-invites still
+ * work), but the type-generic `cliId` alias is eligible **only when this bot is
+ * actually in the current conversation** (`convoBotAppIds` = bots with an active
+ * session in this thread / chat). So "@Codex" resolves to the one codex bot
+ * collaborating here, not every same-type bot. `selfAliases` (the sender's own
+ * name/cliId) are always excluded.
+ */
+export declare function eligibleAutoMentionAliases(input: {
+    botName?: string;
+    cliId?: string;
+    larkAppId?: string;
+    selfAliases: Set<string>;
+    convoBotAppIds: Set<string>;
+}): string[];
+//# sourceMappingURL=dispatch.d.ts.map

package/dist/core/dispatch.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"dispatch.d.ts","sourceRoot":"","sources":["../../src/core/dispatch.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,MAAM,WAAW,WAAW;IAC1B,yEAAyE;IACzE,MAAM,EAAE,MAAM,CAAC;IACf,wEAAwE;IACxE,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,mDAAmD;IACnD,IAAI,CAAC,EAAE,MAAM,CAAC;CACf;AAED,MAAM,MAAM,QAAQ,GAAG;IAAE,GAAG,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GAAG;IAAE,GAAG,EAAE,IAAI,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,CAAC;AACtF,MAAM,MAAM,aAAa,GAAG,QAAQ,EAAE,CAAC;AAEvC,MAAM,WAAW,gBAAgB;IAC/B,8FAA8F;IAC9F,QAAQ,EAAE,MAAM,CAAC;IACjB,0EAA0E;IAC1E,aAAa,EAAE,aAAa,EAAE,CAAC;IAC/B,6EAA6E;IAC7E,gBAAgB,EAAE,MAAM,EAAE,CAAC;CAC5B;AAED;;;;GAIG;AACH,wBAAgB,oBAAoB,CAAC,GAAG,EAAE,MAAM,GAAG,WAAW,CAY7D;AAED;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,KAAK,EAAE;IAC3C,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;IACd,IAAI,EAAE,WAAW,EAAE,CAAC;CACrB,GAAG,gBAAgB,CAwCnB;AAED;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,kBAAkB,CAAC,KAAK,EAAE;IACxC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,WAAW,EAAE,CAAC;CACrB,GAAG;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,gBAAgB,EAAE,MAAM,EAAE,CAAA;CAAE,CAO/C;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,kBAAkB,CAAC,KAAK,EAAE;IACxC,UAAU,EAAE,MAAM,CAAC;IACnB,OAAO,EAAE,MAAM,CAAC;CACjB,GAAG,aAAa,EAAE,CAclB;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,eAAe,CAAC,KAAK,EAAE;IACrC,aAAa,EAAE,MAAM,CAAC;IACtB,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE;QAAE,UAAU,CAAC,EAAE,MAAM,CAAC;QAAC,IAAI,CAAC,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC,CAAC;IACnE,WAAW,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;CAC1B,GAAG,MAAM,GAAG,IAAI,CAShB;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,mBAAmB,CAAC,KAAK,EAAE;IACzC,aAAa,EAAE,MAAM,CAAC;IACtB,uBAAuB,CAAC,EAAE,MAAM,CAAC;IACjC,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE;QAAE,UAAU,CAAC,EAAE,MAAM,CAAC;QAAC,IAAI,CAAC,EAAE,MAAM,EAAE,CAAA;KAAE,CAAC,CAAC;IACnE,WAAW,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;CAC1B,GAAG,MAAM,GAAG,IAAI,CAQhB;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,0BAA0B,CAAC,KAAK,EAAE;IAChD,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,WAAW,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;IACzB,cAAc,EAAE,GAAG,CAAC,MAAM,CAAC,CAAC;CAC7B,GAAG,MAAM,EAAE,CAaX"}

package/dist/core/dispatch.js

@@ -0,0 +1,212 @@
+/**
+ * Phase 0 keystone — `botmux dispatch` pure core.
+ *
+ * The orchestrator (主 bot) splits a big project into sub-projects and assigns
+ * each to a small group of bots (often a coder + a reviewer). To open a
+ * sub-project it seeds a fresh Lark thread and @-mentions the assigned bots so
+ * each spawns its own thread-scoped session (botmux's existing one-thread-one-
+ * session routing; bot→bot @ inside a thread is ungated — see
+ * event-dispatcher.ts decideRouting + the chat-scope-only foreign-bot gate).
+ *
+ * This module is the pure, I/O-free core: parse the `--bot` specs and build the
+ * two messages (a top-level seed = the thread root, and the threaded kickoff
+ * that @-mentions the bots with their roles + the brief). The CLI shell
+ * (cli.ts) performs the actual sendMessage + replyMessage.
+ */
+/**
+ * Parse a `--bot` spec `openId[:name[:role]]` into a {@link DispatchBot}.
+ * Mirrors the `--mention "open_id:Display Name"` convention, with an optional
+ * trailing role segment.
+ */
+export function parseDispatchBotSpec(raw) {
+    const trimmed = raw.trim();
+    if (!trimmed)
+        throw new Error('empty --bot spec');
+    const parts = trimmed.split(':');
+    const openId = parts[0]?.trim();
+    if (!openId)
+        throw new Error(`invalid --bot spec: ${JSON.stringify(raw)}`);
+    const bot = { openId };
+    const name = parts[1]?.trim();
+    const role = parts[2]?.trim();
+    if (name)
+        bot.name = name;
+    if (role)
+        bot.role = role;
+    return bot;
+}
+/**
+ * Build the seed + threaded-kickoff messages for one sub-project dispatch.
+ * Throws when there is no title or no bot to dispatch to.
+ */
+export function buildDispatchMessages(input) {
+    const title = input.title.trim();
+    if (!title)
+        throw new Error('dispatch requires a title');
+    if (input.bots.length === 0)
+        throw new Error('dispatch requires at least one bot');
+    const seedText = `📋 子项目：${title}`;
+    const content = [];
+    // Line 1: @ every assigned bot (role suffix inline) so each gets triggered.
+    const atLine = [];
+    input.bots.forEach((b, i) => {
+        if (i > 0)
+            atLine.push({ tag: 'text', text: ' ' });
+        atLine.push({ tag: 'at', user_id: b.openId });
+        if (b.role)
+            atLine.push({ tag: 'text', text: `（${b.role}）` });
+    });
+    content.push(atLine);
+    content.push([{ tag: 'text', text: '' }]);
+    // The brief, one paragraph per line.
+    for (const line of input.brief.split('\n')) {
+        content.push([{ tag: 'text', text: line }]);
+    }
+    // Division of labour, when any role was given.
+    if (input.bots.some(b => b.role)) {
+        content.push([{ tag: 'text', text: '' }]);
+        content.push([{ tag: 'text', text: '分工：' }]);
+        for (const b of input.bots) {
+            const label = b.name || b.openId;
+            content.push([{ tag: 'text', text: `· ${label}：${b.role ?? '执行'}` }]);
+        }
+    }
+    return {
+        seedText,
+        threadContent: content,
+        mentionedOpenIds: input.bots.map(b => b.openId),
+    };
+}
+/**
+ * Build the "repo prime" message: a `/repo <path>` command @-mentioning the
+ * target bots, sent as a **plain text message** — exactly like a human typing
+ * "@bot /repo <path>". Sent as the first message into a freshly-seeded thread,
+ * it makes each sub-bot's daemon resolve the working dir and spawn its CLI
+ * **idle** (no repo-selection card, no manual "直接开始" click) — i.e. standby.
+ *
+ * Why text (not a structured `post`): the receiving daemon parses a text
+ * message's @ via `resolveMentions` (the same clean path a human @ goes
+ * through), whereas a `post`'s at/text nodes go through `renderPostNode`, which
+ * drops the `/repo` argument in the live event — see the dispatch debugging
+ * notes. `/repo` is an existing botmux command, so this needs no receiving-side
+ * change. The `<at>` tags come first so that, once the receiving daemon strips
+ * leading mentions, it sees `/repo <path>` as the command.
+ */
+export function buildRepoPrimeText(input) {
+    const path = input.path.trim();
+    if (!path)
+        throw new Error('repo prime requires a path');
+    if (input.bots.length === 0)
+        throw new Error('repo prime requires at least one bot');
+    const ats = input.bots.map(b => `<at user_id="${b.openId}"></at>`).join(' ');
+    return { text: `${ats} /repo ${path}`, mentionedOpenIds: input.bots.map(b => b.openId) };
+}
+/**
+ * Build the report-back message a dispatched sub-bot sends to its orchestrator.
+ *
+ * In 多话题协作模式 a sub-bot must NOT @ the orchestrator in its own sub-topic —
+ * that thread has no orchestrator session, so the orchestrator's daemon would
+ * spawn a fresh, context-less one. Instead `botmux report` sends this content
+ * **into the orchestrator's own thread** (recorded by `botmux dispatch`),
+ * @-mentioning the orchestrator so its existing, context-rich session is the one
+ * that wakes up. This is the pure content builder; cli.ts resolves the coords
+ * and performs the reply.
+ *
+ * The @ stays on the first line so the mention renders next to the headline;
+ * any further lines become their own paragraphs (Lark 'post' shape).
+ */
+export function buildReportContent(input) {
+    const openId = input.orchOpenId.trim();
+    if (!openId)
+        throw new Error('report requires the orchestrator open_id');
+    const text = input.content.trim();
+    if (!text)
+        throw new Error('report requires content');
+    const lines = text.split('\n');
+    const paras = [
+        [{ tag: 'at', user_id: openId }, { tag: 'text', text: ' ' }, { tag: 'text', text: lines[0] }],
+    ];
+    for (let i = 1; i < lines.length; i++) {
+        paras.push([{ tag: 'text', text: lines[i] }]);
+    }
+    return paras;
+}
+/**
+ * Footgun guard for the orchestrator→sub-bot direction. A dispatched sub-bot's
+ * session lives **inside its sub-topic**, so @-mentioning it from the main chat
+ * (e.g. `botmux send --mention <sub-bot>`) doesn't reach that session — it
+ * spawns a fresh, context-less one in the chat (the mirror of the report-back
+ * problem). To talk to a sub-bot the orchestrator must send INTO its sub-topic
+ * (`botmux dispatch --into <seed> --bot <sub-bot>`).
+ *
+ * Given the dispatch registry (seed → {orchChatId, bots}) and the set of seeds
+ * whose sub-topic is still active, return the sub-topic seed to redirect to when
+ * `mentionOpenId` is a sub-bot dispatched into an active topic of `chatId`;
+ * otherwise null. Only fires for live topics so stale entries don't block sends.
+ */
+export function findSubBotTopic(input) {
+    // Newest-first: a bot dispatched into several topics over time is, right now,
+    // working in the most-recent one — point there, not at a stale earlier topic.
+    for (const [seed, entry] of Object.entries(input.registry).reverse()) {
+        if (entry.orchChatId && entry.orchChatId !== input.chatId)
+            continue;
+        if (!input.activeSeeds.has(seed))
+            continue;
+        if ((entry.bots ?? []).includes(input.mentionOpenId))
+            return seed;
+    }
+    return null;
+}
+/**
+ * The footgun check shared by `botmux send`'s explicit-mention guard AND its
+ * prose `@Name` auto-injection: returns the sub-topic seed if `mentionOpenId` is
+ * a dispatched sub-bot in an active topic that is NOT reachable in the current
+ * conversation (so @-ing it here would spawn a context-less session), else null.
+ *
+ * The bot I'm replying to (`quoteTargetSenderOpenId`) is reachable right here, so
+ * it's never treated as off-topic — that's the boundary that stops the guard from
+ * blocking a normal reply to a bot conversing with me. Callers block (explicit
+ * --mention) or drop (prose injection) on a non-null result, and skip the whole
+ * check under `--anyway`.
+ */
+export function offTopicSubBotTopic(input) {
+    if (!input.mentionOpenId || input.mentionOpenId === input.quoteTargetSenderOpenId)
+        return null;
+    return findSubBotTopic({
+        mentionOpenId: input.mentionOpenId,
+        chatId: input.chatId,
+        registry: input.registry,
+        activeSeeds: input.activeSeeds,
+    });
+}
+/**
+ * Decide which names of a candidate bot are eligible for prose `@Name`
+ * auto-mention injection in `botmux send`.
+ *
+ * The fan-out bug: a bot writes "@Codex review" in its message; the injector
+ * matches each bot by **botName OR cliId**, and the cliId ("codex") is a shared
+ * *type* alias — so "@Codex" matches every codex-type bot (Codex分身, Codex二号分身,
+ * ttadk(codex), aiden x codex…) and pulls them ALL into the topic, each spawning
+ * a session and replying.
+ *
+ * Fix: the unique `botName` is always eligible (so first-time @-invites still
+ * work), but the type-generic `cliId` alias is eligible **only when this bot is
+ * actually in the current conversation** (`convoBotAppIds` = bots with an active
+ * session in this thread / chat). So "@Codex" resolves to the one codex bot
+ * collaborating here, not every same-type bot. `selfAliases` (the sender's own
+ * name/cliId) are always excluded.
+ */
+export function eligibleAutoMentionAliases(input) {
+    const out = [];
+    const { botName, cliId, larkAppId, selfAliases, convoBotAppIds } = input;
+    if (botName && !selfAliases.has(botName.toLowerCase()))
+        out.push(botName);
+    if (cliId &&
+        !selfAliases.has(cliId.toLowerCase()) &&
+        !!larkAppId &&
+        convoBotAppIds.has(larkAppId)) {
+        out.push(cliId);
+    }
+    return out;
+}
+//# sourceMappingURL=dispatch.js.map

package/dist/core/dispatch.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"dispatch.js","sourceRoot":"","sources":["../../src/core/dispatch.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAuBH;;;;GAIG;AACH,MAAM,UAAU,oBAAoB,CAAC,GAAW;IAC9C,MAAM,OAAO,GAAG,GAAG,CAAC,IAAI,EAAE,CAAC;IAC3B,IAAI,CAAC,OAAO;QAAE,MAAM,IAAI,KAAK,CAAC,kBAAkB,CAAC,CAAC;IAClD,MAAM,KAAK,GAAG,OAAO,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;IACjC,MAAM,MAAM,GAAG,KAAK,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,CAAC;IAChC,IAAI,CAAC,MAAM;QAAE,MAAM,IAAI,KAAK,CAAC,uBAAuB,IAAI,CAAC,SAAS,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;IAC3E,MAAM,GAAG,GAAgB,EAAE,MAAM,EAAE,CAAC;IACpC,MAAM,IAAI,GAAG,KAAK,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,CAAC;IAC9B,MAAM,IAAI,GAAG,KAAK,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,CAAC;IAC9B,IAAI,IAAI;QAAE,GAAG,CAAC,IAAI,GAAG,IAAI,CAAC;IAC1B,IAAI,IAAI;QAAE,GAAG,CAAC,IAAI,GAAG,IAAI,CAAC;IAC1B,OAAO,GAAG,CAAC;AACb,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,qBAAqB,CAAC,KAIrC;IACC,MAAM,KAAK,GAAG,KAAK,CAAC,KAAK,CAAC,IAAI,EAAE,CAAC;IACjC,IAAI,CAAC,KAAK;QAAE,MAAM,IAAI,KAAK,CAAC,2BAA2B,CAAC,CAAC;IACzD,IAAI,KAAK,CAAC,IAAI,CAAC,MAAM,KAAK,CAAC;QAAE,MAAM,IAAI,KAAK,CAAC,oCAAoC,CAAC,CAAC;IAEnF,MAAM,QAAQ,GAAG,UAAU,KAAK,EAAE,CAAC;IAEnC,MAAM,OAAO,GAAoB,EAAE,CAAC;IAEpC,4EAA4E;IAC5E,MAAM,MAAM,GAAe,EAAE,CAAC;IAC9B,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE;QAC1B,IAAI,CAAC,GAAG,CAAC;YAAE,MAAM,CAAC,IAAI,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,GAAG,EAAE,CAAC,CAAC;QACnD,MAAM,CAAC,IAAI,CAAC,EAAE,GAAG,EAAE,IAAI,EAAE,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC;QAC9C,IAAI,CAAC,CAAC,IAAI;YAAE,MAAM,CAAC,IAAI,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC,IAAI,GAAG,EAAE,CAAC,CAAC;IAChE,CAAC,CAAC,CAAC;IACH,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IAErB,OAAO,CAAC,IAAI,CAAC,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE,EAAE,CAAC,CAAC,CAAC;IAE1C,qCAAqC;IACrC,KAAK,MAAM,IAAI,IAAI,KAAK,CAAC,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC;QAC3C,OAAO,CAAC,IAAI,CAAC,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;IAC9C,CAAC;IAED,+CAA+C;IAC/C,IAAI,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,EAAE,CAAC;QACjC,OAAO,CAAC,IAAI,CAAC,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE,EAAE,CAAC,CAAC,CAAC;QAC1C,OAAO,CAAC,IAAI,CAAC,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC,CAAC;QAC7C,KAAK,MAAM,CAAC,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC;YAC3B,MAAM,KAAK,GAAG,CAAC,CAAC,IAAI,IAAI,CAAC,CAAC,MAAM,CAAC;YACjC,OAAO,CAAC,IAAI,CAAC,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,KAAK,KAAK,IAAI,CAAC,CAAC,IAAI,IAAI,IAAI,EAAE,EAAE,CAAC,CAAC,CAAC;QACxE,CAAC;IACH,CAAC;IAED,OAAO;QACL,QAAQ;QACR,aAAa,EAAE,OAAO;QACtB,gBAAgB,EAAE,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC;KAChD,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,UAAU,kBAAkB,CAAC,KAGlC;IACC,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,CAAC,IAAI,EAAE,CAAC;IAC/B,IAAI,CAAC,IAAI;QAAE,MAAM,IAAI,KAAK,CAAC,4BAA4B,CAAC,CAAC;IACzD,IAAI,KAAK,CAAC,IAAI,CAAC,MAAM,KAAK,CAAC;QAAE,MAAM,IAAI,KAAK,CAAC,sCAAsC,CAAC,CAAC;IAErF,MAAM,GAAG,GAAG,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,gBAAgB,CAAC,CAAC,MAAM,SAAS,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;IAC7E,OAAO,EAAE,IAAI,EAAE,GAAG,GAAG,UAAU,IAAI,EAAE,EAAE,gBAAgB,EAAE,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC;AAC3F,CAAC;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,kBAAkB,CAAC,KAGlC;IACC,MAAM,MAAM,GAAG,KAAK,CAAC,UAAU,CAAC,IAAI,EAAE,CAAC;IACvC,IAAI,CAAC,MAAM;QAAE,MAAM,IAAI,KAAK,CAAC,0CAA0C,CAAC,CAAC;IACzE,MAAM,IAAI,GAAG,KAAK,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC;IAClC,IAAI,CAAC,IAAI;QAAE,MAAM,IAAI,KAAK,CAAC,yBAAyB,CAAC,CAAC;IAEtD,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;IAC/B,MAAM,KAAK,GAAoB;QAC7B,CAAC,EAAE,GAAG,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,EAAE,EAAE,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,GAAG,EAAE,EAAE,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,KAAK,CAAC,CAAC,CAAC,EAAE,CAAC;KAC9F,CAAC;IACF,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QACtC,KAAK,CAAC,IAAI,CAAC,CAAC,EAAE,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,KAAK,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;IAChD,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,eAAe,CAAC,KAK/B;IACC,8EAA8E;IAC9E,8EAA8E;IAC9E,KAAK,MAAM,CAAC,IAAI,EAAE,KAAK,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC;QACrE,IAAI,KAAK,CAAC,UAAU,IAAI,KAAK,CAAC,UAAU,KAAK,KAAK,CAAC,MAAM;YAAE,SAAS;QACpE,IAAI,CAAC,KAAK,CAAC,WAAW,CAAC,GAAG,CAAC,IAAI,CAAC;YAAE,SAAS;QAC3C,IAAI,CAAC,KAAK,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC,QAAQ,CAAC,KAAK,CAAC,aAAa,CAAC;YAAE,OAAO,IAAI,CAAC;IACpE,CAAC;IACD,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,mBAAmB,CAAC,KAMnC;IACC,IAAI,CAAC,KAAK,CAAC,aAAa,IAAI,KAAK,CAAC,aAAa,KAAK,KAAK,CAAC,uBAAuB;QAAE,OAAO,IAAI,CAAC;IAC/F,OAAO,eAAe,CAAC;QACrB,aAAa,EAAE,KAAK,CAAC,aAAa;QAClC,MAAM,EAAE,KAAK,CAAC,MAAM;QACpB,QAAQ,EAAE,KAAK,CAAC,QAAQ;QACxB,WAAW,EAAE,KAAK,CAAC,WAAW;KAC/B,CAAC,CAAC;AACL,CAAC;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,0BAA0B,CAAC,KAM1C;IACC,MAAM,GAAG,GAAa,EAAE,CAAC;IACzB,MAAM,EAAE,OAAO,EAAE,KAAK,EAAE,SAAS,EAAE,WAAW,EAAE,cAAc,EAAE,GAAG,KAAK,CAAC;IACzE,IAAI,OAAO,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,OAAO,CAAC,WAAW,EAAE,CAAC;QAAE,GAAG,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;IAC1E,IACE,KAAK;QACL,CAAC,WAAW,CAAC,GAAG,CAAC,KAAK,CAAC,WAAW,EAAE,CAAC;QACrC,CAAC,CAAC,SAAS;QACX,cAAc,CAAC,GAAG,CAAC,SAAS,CAAC,EAC7B,CAAC;QACD,GAAG,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;IAClB,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC"}

package/dist/daemon.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"daemon.d.ts","sourceRoot":"","sources":["../src/daemon.ts"],"names":[],"mappings":"AA0BA,YAAY,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAmErD,OAAO,EAAE,oBAAoB,EAA6B,MAAM,uBAAuB,CAAC;AACxF,OAAO,KAAK,EAAE,sBAAsB,EAAiB,MAAM,wBAAwB,CAAC;AAyWpF,wBAAgB,0BAA0B,CAAC,KAAK,EAAE,MAAM,EAAE,GAAG,CAAC,EAAE,sBAAsB,GAAG,oBAAoB,CA0C5G;AAijED,wBAAsB,WAAW,CAAC,QAAQ,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAyTlE"}
+{"version":3,"file":"daemon.d.ts","sourceRoot":"","sources":["../src/daemon.ts"],"names":[],"mappings":"AA0BA,YAAY,EAAE,aAAa,EAAE,MAAM,iBAAiB,CAAC;AAmErD,OAAO,EAAE,oBAAoB,EAA6B,MAAM,uBAAuB,CAAC;AACxF,OAAO,KAAK,EAAE,sBAAsB,EAAiB,MAAM,wBAAwB,CAAC;AAyWpF,wBAAgB,0BAA0B,CAAC,KAAK,EAAE,MAAM,EAAE,GAAG,CAAC,EAAE,sBAAsB,GAAG,oBAAoB,CA0C5G;AA6lED,wBAAsB,WAAW,CAAC,QAAQ,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAyTlE"}

package/dist/daemon.js

@@ -1925,9 +1925,50 @@ async function handleThreadReply(data, ctx) {
                 sessionReply(anchor, tr('daemon.cmd_allowed_users_only', { cmd }, localeForBot(larkAppId)), 'text', larkAppId);
                 return;
             }
+            // First message of a fresh thread carrying a session-needing daemon command
+            // — e.g. another bot dispatched `/repo <path>` into a brand-new thread.
+            // Without a session, handleCommand gets ds=undefined and `/repo` (and other
+            // session commands) fall through to the repo-select card. Create the session
+            // first, mirroring handleNewTopic's first-message `/repo` pendingRepo setup.
+            // Session-less commands (/group /g) don't need one.
+            if (!existingDs && threadChatId && !SESSIONLESS_DAEMON_COMMANDS.has(cmd)) {
+                const session = sessionStore.createSession(threadChatId, anchor, cmdContent.substring(0, 50), ctxChatType);
+                const now = Date.now();
+                session.larkAppId = larkAppId;
+                session.ownerOpenId = threadSenderOpenId;
+                session.creatorOpenId = threadSenderOpenId; // stable creator (= dispatch orchestrator for /repo prime) — see Session.creatorOpenId
+                session.ownerUnionId = data?.sender?.sender_id?.union_id;
+                session.lastCallerOpenId = threadSenderOpenId;
+                session.lastMessageAt = new Date(now).toISOString();
+                session.scope = scope;
+                let cmdPending;
+                if (cmd === '/repo') {
+                    const { pinnedWorkingDir } = await resolvePinnedWorkingDir({ scope, anchor, chatId: threadChatId, chatType: ctxChatType, larkAppId });
+                    if (pinnedWorkingDir)
+                        session.workingDir = pinnedWorkingDir;
+                    cmdPending = { pendingRepo: true, pendingPrompt: '', workingDir: pinnedWorkingDir };
+                }
+                sessionStore.updateSession(session);
+                activeSessions.set(sessionKey(anchor, larkAppId), {
+                    session,
+                    worker: null,
+                    workerPort: null,
+                    workerToken: null,
+                    larkAppId,
+                    chatId: threadChatId,
+                    chatType: ctxChatType,
+                    scope,
+                    spawnedAt: Date.parse(session.createdAt) || now,
+                    cliVersion: cliVersionCache.get(getBot(larkAppId).config.cliId)?.version ?? 'unknown',
+                    lastMessageAt: now,
+                    hasHistory: false,
+                    ownerOpenId: threadSenderOpenId,
+                    ...cmdPending,
+                });
+            }
             // Pass mention-stripped content so /command argument parsing works.
             // chatId lets session-less handlers (e.g. /group) reach the chat roster.
-            handleCommand(cmd, anchor, { ...parsed, content: commandContent, chatId: threadChatId }, commandDeps, larkAppId);
+            await handleCommand(cmd, anchor, { ...parsed, content: commandContent, chatId: threadChatId }, commandDeps, larkAppId);
             return;
         }
     }
@@ -2039,6 +2080,10 @@ async function handleThreadReply(data, ctx) {
         const ownerUnionId = isForeignBot ? undefined : senderUId;
         session.larkAppId = larkAppId;
         session.ownerOpenId = ownerOpenId;
+        // creatorOpenId is the raw creating sender — set even for foreign-bot
+        // sessions (unlike ownerOpenId, nulled above) so `botmux report` can find the
+        // dispatch orchestrator on a no-`/repo` kickoff auto-create. See Session.creatorOpenId.
+        session.creatorOpenId = senderOId;
         session.ownerUnionId = ownerUnionId;
         session.lastCallerOpenId = senderOId;
         session.quoteTargetId = parsed.messageId;