@youdie006/prodex 0.39.0 → 0.39.2

package/dist/cli-help.js

@@ -26,7 +26,7 @@ Ask / consult commands:
   prodex pro browser models [--source-cli /absolute/path/to/dist/cli.js] [--port 9333] [--timeout-ms 15000]  # read-only list of model menu options
   prodex pro browser projects [--source-cli /absolute/path/to/dist/cli.js] [--port 9333] [--timeout-ms 15000]  # read-only list of sidebar project names (for --project)
   prodex pro browser recover [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--port 9333] --target-url <thread-url> [--timeout-ms 60000]  # recover a finished answer from a thread whose send timed out
-  prodex pro browser ask [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--port 9333] [--timeout-ms 300000] [--busy-wait-ms 600000] [--target-url url --confirm-target] [--new-chat] [--temporary] [--stdin] [--json] [--auto-login|--no-auto-login] [--file path] [--attach path] [--tool deep-research|web-search|create-image] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Pro] [--project "name" | --project-new "name"] "prompt"  # explicit visible-browser send
+  prodex pro browser ask [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--port 9333] [--timeout-ms 300000] [--busy-wait-ms 600000] [--target-url url --confirm-target] [--new-chat] [--temporary] [--stdin] [--json] [--auto-login|--no-auto-login] [--file path] [--attach path] [--tool deep-research|web-search|create-image] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Max|Ultra|Pro] [--project "name" | --project-new "name"] "prompt"  # explicit visible-browser send
   prodex pro latest [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--json]
   prodex pro list [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--json]
   prodex pro show <task-id|latest> [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--json]
@@ -52,7 +52,7 @@ Bridge ledger (durable tasks/results/receipts/sessions under .bridge/):
 
 Agent / MCP integration:
   prodex mcp [--cwd /absolute/path/to/repo]
-  prodex setup [--cwd /absolute/path/to/repo] [--host 127.0.0.1] [--port 8787] [--token-ttl-hours <hours>] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Pro] [--project "name"] [--clear-model|--clear-pro-mode|--clear-effort|--clear-project] [--interactive]
+  prodex setup [--cwd /absolute/path/to/repo] [--host 127.0.0.1] [--port 8787] [--token-ttl-hours <hours>] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Max|Ultra|Pro] [--project "name"] [--clear-model|--clear-pro-mode|--clear-effort|--clear-project] [--interactive]
   prodex start [--cwd /absolute/path/to/repo] [--source-cli /absolute/path/to/dist/cli.js]
   prodex status [--cwd /absolute/path/to/repo] [--source-cli /absolute/path/to/dist/cli.js] [--show-token] [--url-only] [--unsafe-show-non-expiring-token]
   prodex tunnel url [--cwd /absolute/path/to/repo] [--source-cli /absolute/path/to/dist/cli.js] --public-url https://... [--show-token] [--url-only]
@@ -80,14 +80,14 @@ export function printSetupHelp(stdout) {
     stdout(`prodex setup
 
 Commands:
-  prodex setup [--cwd /absolute/path/to/repo] [--host 127.0.0.1] [--port 8787] [--token-ttl-hours <hours>] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Pro] [--project "name"] [--clear-model|--clear-pro-mode|--clear-effort|--clear-project] [--interactive]
+  prodex setup [--cwd /absolute/path/to/repo] [--host 127.0.0.1] [--port 8787] [--token-ttl-hours <hours>] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Max|Ultra|Pro] [--project "name"] [--clear-model|--clear-pro-mode|--clear-effort|--clear-project] [--interactive]
 
 Save a loopback-only HTTP MCP profile in .bridge/config.local.json. Use --token-ttl-hours before tunnels or ChatGPT Project use.
 
 Optional visible-browser send defaults (applied by \`pro browser ask\` when the matching per-ask flag is omitted):
-  --model      Composer model to pick by its exact menu label (verified: Pro)
+  --model      Composer model by its exact menu label. Only Pro applies on the current picker: it is a slider step, and the model rows cannot be clicked
   --pro-mode   Pro sub-mode: 기본 (standard) or 확장 (extended)
-  --effort     Reasoning effort: 즉시 / 중간 / 높음 / 매우 높음 (English aliases: instant/medium/high/max); picking one deselects Pro
+  --effort     Reasoning effort: 즉시 / 중간 / 높음 / 매우 높음 / Max / Ultra / Pro. Max and Ultra are rungs of ChatGPT's Work surface and only apply when the browser is already on Work (prodex does not switch to Work for them); every other value is sent on Chat, whose top step is Pro
   --project    Sidebar project to enter before sending
 Clear a saved default with --clear-model / --clear-pro-mode / --clear-effort / --clear-project.
 --pro-mode and --effort are different model axes and cannot be combined. View saved defaults with \`prodex status\`.`);
@@ -168,7 +168,7 @@ Commands:
   prodex pro browser check [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo]
   prodex pro browser smoke [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo]
   prodex pro browser models [--source-cli /absolute/path/to/dist/cli.js]
-  prodex pro browser ask [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--target-url url --confirm-target] [--new-chat] [--temporary] [--stdin] [--json] [--auto-login|--no-auto-login] [--file path] [--attach path] [--tool deep-research|web-search|create-image] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Pro] [--project "name" | --project-new "name"] "prompt"
+  prodex pro browser ask [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--target-url url --confirm-target] [--new-chat] [--temporary] [--stdin] [--json] [--auto-login|--no-auto-login] [--file path] [--attach path] [--tool deep-research|web-search|create-image] [--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Max|Ultra|Pro] [--project "name" | --project-new "name"] "prompt"
   prodex pro latest [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--json]
   prodex pro list [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--json]
   prodex pro show <task-id|latest> [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--json]
@@ -179,7 +179,7 @@ Use \`prodex pro browser ask\` only when you want an explicit visible-browser se
 Model/project selection (visible-browser send):
   --model "label"              Pick the composer model by its exact menu label (verified: Pro). Submenu models (e.g. the GPT-5.6 Sol variants) are rejected for now.
   --pro-mode 기본 | 확장          Pro sub-mode (only when the model is Pro); a Pro selection raises the default timeout to 1200000 ms
-  --effort 즉시|중간|높음|매우 높음   Reasoning effort (aliases: instant/medium/high/max); picking one deselects Pro
+  --effort 즉시|중간|높음|매우 높음|Max|Ultra|Pro   Reasoning effort (aliases: instant/light, medium, high, extrahigh/max, ultra); picking one moves the single power slider
   --project "name"             Enter an existing sidebar project first (cannot combine with --target-url)
 Labels are matched in both the Korean and English (US) UI; run \`prodex pro browser models\` to list what your account shows.
 Persist defaults with \`prodex setup --model/--pro-mode/--effort/--project\`; clear them with setup --clear-model/--clear-pro-mode/--clear-effort/--clear-project.
@@ -253,7 +253,7 @@ export function printProBrowserHelp(stdout, sourceCli) {
     const smokeUsage = sourceCli
         ? `${cli} pro browser smoke${sourceCliOption} [--cwd /absolute/path/to/repo] [--port 9333] [--timeout-ms 90000]`
         : "prodex pro browser smoke [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--port 9333] [--timeout-ms 90000]";
-    const selectionUsage = '[--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Pro] [--project "name" | --project-new "name"]';
+    const selectionUsage = '[--model Pro] [--pro-mode 기본|확장] [--effort 즉시|중간|높음|"매우 높음"|Max|Ultra|Pro] [--project "name" | --project-new "name"]';
     const askUsage = sourceCli
         ? `${cli} pro browser ask${sourceCliOption} [--cwd /absolute/path/to/repo] [--port 9333] [--timeout-ms 300000] [--busy-wait-ms 600000] [--target-url url --confirm-target] [--new-chat] [--temporary] [--stdin] [--json] [--auto-login|--no-auto-login] [--file path] [--attach path] [--tool deep-research|web-search|create-image] ${selectionUsage} "prompt"`
         : `prodex pro browser ask [--source-cli /absolute/path/to/dist/cli.js] [--cwd /absolute/path/to/repo] [--port 9333] [--timeout-ms 300000] [--busy-wait-ms 600000] [--target-url url --confirm-target] [--new-chat] [--temporary] [--stdin] [--json] [--auto-login|--no-auto-login] [--file path] [--attach path] [--tool deep-research|web-search|create-image] ${selectionUsage} "prompt"`;
@@ -299,9 +299,9 @@ Commands:
 
 Visible-browser sends require a manual browser session and stop on login, captcha, Cloudflare, permission, rate-limit, or usage-limit blockers, plus response_choice_pending when ChatGPT is waiting for you to pick which of two answers you prefer.
 Model/project selection (ask):
-  --model      Composer model to pick by its exact menu label (verified: Pro). Models whose menu entry opens a submenu of variants are rejected with a clear error for now.
+  --model      Composer model by its exact menu label. On the current picker only Pro applies - it is a step of the power slider, while the model rows carry pointer-events: none and no coordinate reaches them, so any other name warns and the send goes out on whatever the composer already had. Models whose menu entry opens a submenu of variants are rejected with a clear error for now.
   --pro-mode   Pro sub-mode: 기본 (standard) or 확장 (extended), used when the model is Pro. A Pro selection raises the default --timeout-ms to 1200000.
-  --effort     Reasoning effort: 즉시 / 중간 / 높음 / 매우 높음 (aliases: instant/medium/high/max). Picking an effort switches the composer to the standard reasoning model, deselecting Pro.
+  --effort     Reasoning effort: 즉시 / 중간 / 높음 / 매우 높음 / Max / Ultra / Pro (aliases: instant/light, medium, high, extrahigh/max, ultra). One power slider sets the model and the effort together, so picking an effort moves off Pro. Max and Ultra are rungs of the Work surface and only apply when the browser is already on Work; everything else is sent on Chat.
   --project    Enter an existing sidebar project before sending. Cannot be combined with --target-url.
 --pro-mode and --effort cannot be combined. Labels are matched in both the Korean and English (US) ChatGPT UI (e.g. 높음/High, Pro 확장/Pro Extended).
 Run \`${cli} pro browser models${sourceCliOption}\` to list the labels your account currently shows.

package/dist/cli-pro.js

@@ -2,7 +2,7 @@ import { existsSync, statSync } from "node:fs";
 import { mkdir, readFile, writeFile } from "node:fs/promises";
 import path from "node:path";
 import { buildDryRunBundle } from "./bundle.js";
-import { DEFAULT_CDP_PORT, resolveCdpPort, resolveConversationToDelete, resolveProjectToDelete, chatGptVisibilityBlocker, defaultChatGptProfileDir, formatDurationMs, getChatGptBrowserStatus, formatModelMenuOption, listChatGptModelOptions, deleteChatGptConversation, endWedgedBrowser, browserRecoveryPlan, findWedgedBrowser, wedgedBrowserBlocker, deleteChatGptProject, listChatGptProjectsWithIds, listRecentChatGptConversations, listChatGptSidebarProjects, normalizeChatGptTargetUrl, openChatGptBrowser, openChatGptTab, parseProMode, parseReasoningEffort, defaultTimeoutForTools, ensureVirtualDisplay, minimizeChatGptWindow, readLastBrowserLoginLaunch, resolveVirtualDisplayPreference, resolveBrowserWindowMode, resolveHeadlessPreference, recordBrowserLoginLaunch, recoverChatGptAnswerFromThread, sendChatGptPrompt } from "./chatgpt-browser.js";
+import { DEFAULT_CDP_PORT, resolveCdpPort, resolveConversationToDelete, resolveProjectToDelete, chatGptVisibilityBlocker, defaultChatGptProfileDir, formatDurationMs, getChatGptBrowserStatus, formatModelMenuOption, listChatGptModelOptions, deleteChatGptConversation, endWedgedBrowser, browserRecoveryPlan, findWedgedBrowser, wedgedBrowserBlocker, deleteChatGptProject, listChatGptProjectsWithIds, listRecentChatGptConversations, listChatGptSidebarProjects, normalizeChatGptTargetUrl, openChatGptBrowser, openChatGptTab, parseProMode, parseReasoningEffort, defaultTimeoutForTools, ensureVirtualDisplay, minimizeChatGptWindow, readLastBrowserLoginLaunch, resolveVirtualDisplayPreference, resolveBrowserWindowMode, resolveHeadlessPreference, recordBrowserLoginLaunch, recoverChatGptAnswerFromThread, sendChatGptPrompt, statusMeansBrowserDead } from "./chatgpt-browser.js";
 import { ASK_PRO_BOOLEAN_FLAGS, ASK_PRO_PREVIEW_VALUE_FLAGS, ASK_PRO_VALUE_FLAGS, assertHelpRequestArgs, assertNoExtraArgs, assertOnlyOptions, findHelpFlagIndexBeforePromptDelimiter, formatCliCommand, hasAskProDryRunMode, hasAskProMode, hasAskProSendMode, isHelpSubcommand, parseAskProArgs, printHelpIfRequested, readFlag, readPortFlag, readPositionalsWithOptions, readNonNegativeIntegerFlag, readPositiveIntegerFlag, readRepeatedFlag, resolveCwdFlag, resolveOptionalFileFlag, unknownSubcommandError } from "./cli-args.js";
 import { printProBrowserHelp, printProHelp } from "./cli-help.js";
 import { listRawResultsForInspection, listTasksForInspection } from "./cli-ledger.js";
@@ -429,10 +429,14 @@ export async function runProCommand(rest, io, runCliFn) {
             const modelsResolvedPort = resolveCdpPort(modelsPort);
             let listed;
             try {
-                listed = await listChatGptModelOptions({
+                // Reading the ladder WALKS the slider, so it must not interleave with
+                // a send: two processes driving one browser is how a listing ended up
+                // changing the model a consult was about to use. Waits for a send in
+                // flight rather than barging in.
+                listed = await withBrowserSendLock(modelsTimeoutMs ?? 60_000, (detail) => io.stderr(`progress: ${detail}`), () => listChatGptModelOptions({
                     port: modelsPort,
                     timeoutMs: modelsTimeoutMs
-                });
+                }));
             }
             catch (error) {
                 // Keep the next step actionable for a custom port: the raw blocker
@@ -443,6 +447,9 @@ export async function runProCommand(rest, io, runCliFn) {
                 });
                 throw new Error(blocker.next_step ? `${blocker.message} Next: ${blocker.next_step}` : errorMessage(error));
             }
+            if (listed.surface) {
+                io.stdout(`Read from ChatGPT's ${listed.surface} surface. Chat and Work have different pickers - only one of them offers Pro.`);
+            }
             io.stdout("Model menu options in the visible ChatGPT tab (read-only; nothing was selected):");
             for (const option of listed.options) {
                 io.stdout(formatModelMenuOption(option));
@@ -525,7 +532,12 @@ export async function runProCommand(rest, io, runCliFn) {
             const recoverResolvedPort = resolveCdpPort(recoverPort);
             let consult;
             try {
-                consult = await recoverChatGptAnswerFromThread({ port: recoverPort, targetUrl, timeoutMs: recoverTimeoutMs });
+                // Recovery NAVIGATES the tab to the thread it is reading. Doing that
+                // under a send in flight walks the browser off the conversation that
+                // send is streaming into, which is the consult it would destroy - and
+                // recovery is exactly what gets run after a send appears to hang, so
+                // the two meeting is a when rather than an if.
+                consult = await withBrowserSendLock(recoverTimeoutMs ?? 60_000, (detail) => io.stderr(`progress: ${detail}`), () => recoverChatGptAnswerFromThread({ port: recoverPort, targetUrl, timeoutMs: recoverTimeoutMs }));
             }
             catch (error) {
                 const blocker = sourceAwareBrowserBlocker(browserSendBlockerFromError(error), recoverSourceCli, {
@@ -1206,12 +1218,16 @@ export async function runAskProCommand(rest, io) {
                 const firstBlocker = browserSendBlockerFromError(error);
                 if (firstBlocker.code !== "browser_unreachable" || !autoLoginAllowed)
                     throw error;
+                const recoveryNotes = [];
                 const recovered = await attemptBrowserAutoRecovery(io.stderr, {
-                    ...(browserPort !== undefined ? { port: browserPort } : {})
+                    ...(browserPort !== undefined ? { port: browserPort } : {}),
+                    notes: recoveryNotes
                 });
                 if (!recovered)
                     throw error;
                 consult = await sendOnce();
+                if (recoveryNotes.length > 0)
+                    consult = { ...consult, warnings: [...recoveryNotes, ...consult.warnings] };
             }
         }
         catch (error) {
@@ -1524,7 +1540,9 @@ async function confirmBrowserSilence(port, probes = 3, gapMs = 2_000) {
         if (attempt > 0)
             await sleep(gapMs);
         const status = await getChatGptBrowserStatus({ ...(port !== undefined ? { port } : {}), timeoutMs: 2_000 });
-        if (status.reachable)
+        // Slow is not silent. Three 2s timeouts on a loaded machine used to read as
+        // a dead browser, and what followed was SIGTERM to a live one mid-answer.
+        if (!statusMeansBrowserDead(status))
             return false;
     }
     return true;
@@ -1565,6 +1583,9 @@ export async function attemptBrowserAutoRecovery(stderr, options) {
             return false;
         }
         stderr(`recover: the browser stopped answering; ending it (pid ${wedged.join(", ")}) and starting a fresh one...`);
+        // Ending someone's browser is not a progress line to scroll past: it goes on
+        // the receipt, where an agent or a person reading `pro latest` will see it.
+        options.notes?.push(`browser_recovered: the dedicated browser stopped answering its control port and prodex ended it (pid ${wedged.join(", ")}) and started a fresh one before sending. Anything it was doing at the time is gone; the profile and login were kept.`);
         await endWedgedBrowser(wedged);
         // Wait for the profile lock to actually clear rather than guessing at a
         // delay: the replacement launch fails outright if the old process still
@@ -1738,13 +1759,35 @@ export function browserSendBlockerFromError(error) {
     // A CDP command timeout means the page's renderer stalled, which in the
     // field means a very long thread (or a long prompt landing on one). Generic
     // "resolve the browser issue manually" advice gave the caller nothing to do.
+    // The browser lock refusing is not a browser issue: another prodex send owns
+    // the window. Sending people to "resolve the visible browser issue" for it
+    // pointed at a problem that did not exist.
+    if (/Another prodex browser send is in progress/.test(message)) {
+        return {
+            code: "browser_busy",
+            message,
+            retryable: true,
+            next_step: "Another prodex send holds the browser. Wait for it to finish and retry, or pass a longer --timeout-ms, which is also the queue budget."
+        };
+    }
+    // The tab's DevTools connection went away mid-send with no timeout behind
+    // it: the tab was closed, navigated from outside, or the browser exited.
+    if (/Chrome DevTools websocket (closed|is not open)/.test(message)) {
+        return {
+            code: "browser_connection_lost",
+            message,
+            retryable: true,
+            next_step: "The connection to the ChatGPT tab closed while prodex was using it - the tab was closed or navigated by someone else, or the browser exited. Check the visible window and retry; `prodex pro browser login` reopens it."
+        };
+    }
     const cdpTimeout = message.match(/Chrome DevTools command timed out: (\S+)/);
     if (cdpTimeout) {
         return {
             code: "browser_cdp_timeout",
             message,
             retryable: true,
-            next_step: "The ChatGPT tab stopped responding (usually a very long thread). Retry with `--new-chat` for a fresh, light thread, or reload the tab in the browser first."
+            next_step: "The ChatGPT tab stopped responding. A very long thread does it, and so does an open JavaScript dialog - that one halts the page outright, and no retry gets past it because the browser will not let a late client dismiss it. " +
+                "Look at the visible window and close any dialog sitting on it, or reopen the window with `prodex pro browser login`. For a heavy thread, retry with `--new-chat` for a fresh, light one."
         };
     }
     return {

package/dist/cli-server.js

@@ -63,10 +63,42 @@ export async function runSetupCommand(rest, io) {
     }
     return 0;
 }
+/** A best-effort warning must not outlast the command it decorates. */
+const PINNED_SELECTION_CHECK_BUDGET_MS = 15_000;
 /** What the picker currently offers, compared against what was just pinned. */
 async function pinnedSelectionCheck(defaults) {
     const { listChatGptModelOptions, pinnedSelectionWarning } = await import("./chatgpt-browser.js");
-    const listed = await listChatGptModelOptions({ timeoutMs: 8_000 });
+    // Only the model names are compared here, so the ladder is not walked: this
+    // is a config command and it has no business moving the live slider. The
+    // whole check is also raced against a deadline, because timeoutMs covers
+    // finding the page and not what happens inside the picker afterwards - a
+    // best-effort warning must never be what makes `setup` hang.
+    // Fail fast if a send holds the browser: this is a decoration on a config
+    // command, and opening a menu underneath a streaming consult is not worth a
+    // warning. The caller already swallows what this throws.
+    const { withBrowserSendLock } = await import("./browser-send-lock.js");
+    // The deadline timer is cleared once the listing wins and never holds the
+    // process open: the CLI exits through process.exitCode, so a live timer kept
+    // `setup` alive for the whole budget after its work was done. And when the
+    // deadline wins, the listing is abandoned - its connection closed, the send
+    // lock released - rather than left running unattended behind the prompt.
+    let deadline;
+    const abandon = new AbortController();
+    const listed = await Promise.race([
+        withBrowserSendLock(0, () => { }, () => listChatGptModelOptions({ timeoutMs: 8_000, walkPowerSlider: false, signal: abandon.signal })),
+        new Promise((resolve) => {
+            deadline = setTimeout(() => {
+                abandon.abort();
+                resolve(undefined);
+            }, PINNED_SELECTION_CHECK_BUDGET_MS);
+            deadline.unref?.();
+        })
+    ]).finally(() => {
+        if (deadline)
+            clearTimeout(deadline);
+    });
+    if (!listed)
+        return undefined;
     const offered = listed.options.flatMap((option) => [option.label, ...(option.value ? [option.value] : [])]);
     return pinnedSelectionWarning({
         ...(defaults.model !== undefined ? { model: defaults.model } : {}),

package/dist/mcp.js

@@ -190,7 +190,7 @@ export function createServer(cwd = process.cwd(), options = {}) {
     const browserRecover = options.browserRecover;
     if (browserRecover) {
         server.registerTool("pro_recover", {
-            description: "Fetch a ChatGPT answer that finished AFTER a consult stopped waiting, and record it as a normal consult receipt. Use this whenever pro_consult came back with a timeout or a still-running blocker: those carry the thread URL, and the answer is almost always sitting in that thread. This is also how a deep research report is collected - a research run takes about ten minutes and keeps going even when the consult that started it has already returned. Reading is cheap and does not send anything, so it is safe to retry.",
+            description: "Fetch a ChatGPT answer that finished AFTER a consult stopped waiting, and record it as a normal consult receipt. Use this whenever pro_consult came back with a timeout or a still-running blocker: those carry the thread URL, and the answer is almost always sitting in that thread. This is also how a deep research report is collected - a research run takes about ten minutes and keeps going even when the consult that started it has already returned. It sends no prompt, but it does navigate the visible tab to that thread, so it waits for any consult still streaming rather than walking the browser off it.",
             inputSchema: {
                 thread: McpShortTextSchema.min(1).describe("The ChatGPT conversation URL from the blocker (its `thread` field)."),
                 timeout_ms: z.number().int().positive().max(600_000).optional()

package/dist/picker-interaction.js

@@ -70,3 +70,115 @@ export function menuKeyboardStep(input) {
     }
     return pressed < limit ? "down" : "exhausted";
 }
+/**
+ * One move towards putting the power slider back where the walk found it.
+ *
+ * Driven by the position actually read rather than by a replayed count, so an
+ * interrupted walk still converges instead of abandoning the setting wherever
+ * it stopped.
+ */
+export function sliderRestoreStep(input) {
+    const { current, target } = input;
+    if (!Number.isInteger(current) || !Number.isInteger(target))
+        return "done";
+    if (current === target)
+        return "done";
+    return current > target ? "left" : "right";
+}
+/**
+ * Decide whether the browser needs putting back on ChatGPT's Chat surface.
+ *
+ * Chat and Work have different model pickers - Work's has no Pro at all - so a
+ * browser that has drifted onto Work silently drives the wrong one.
+ */
+export function chatSurfaceChoice(surfaces) {
+    const chat = surfaces.find((surface) => surface.label.trim().toLowerCase() === "chat");
+    if (!chat)
+        return "no-toggle";
+    return chat.checked ? "already-chat" : "switch-to-chat";
+}
+/**
+ * Which surface is live, using the visible toggle where there is one and the
+ * value ChatGPT persists where there is not.
+ *
+ * The toggle is only rendered on the home screen, but threads and project pages
+ * keep the surface that was chosen - so a send into a project can be driving
+ * Work's picker with nothing on the page to say so.
+ */
+export function chatSurfaceState(input) {
+    const fromToggle = chatSurfaceChoice(input.surfaces);
+    if (fromToggle !== "no-toggle")
+        return fromToggle;
+    const stored = (input.storedMode ?? "").trim().replace(/^"|"$/g, "").toLowerCase();
+    if (stored === "chat")
+        return "already-chat";
+    // Only a value that names Work is a reason to move. Anything else - "null",
+    // a mode this code has never heard of - is not evidence, and acting on it
+    // would rewrite the preference and reload the page on every send.
+    if (stored === "work")
+        return "switch-to-chat";
+    return "unknown";
+}
+/** Steps that exist only on ChatGPT's Work surface, so asking for one means staying there. */
+const WORK_ONLY_EFFORTS = new Set(["max", "ultra"]);
+/**
+ * Whether the requested effort only exists on the Work surface.
+ *
+ * Sends otherwise put the browser back on Chat, which would make these two
+ * impossible to apply while still being offered by the help.
+ */
+export function effortNeedsWorkSurface(effort) {
+    return effort ? WORK_ONLY_EFFORTS.has(effort.trim().toLowerCase()) : false;
+}
+/**
+ * How to answer a JavaScript dialog that appeared in the driven browser.
+ *
+ * A dialog halts the page's main thread, so every evaluate after it hangs -
+ * and a client that had not enabled the Page domain beforehand cannot dismiss
+ * it at all. Answering one is therefore about getting out of the way, not about
+ * agreeing to whatever it asked: only beforeunload is accepted, because that is
+ * the page questioning a navigation prodex itself requested.
+ */
+export function javascriptDialogResponse(type) {
+    return { accept: type === "beforeunload" };
+}
+/**
+ * A note that prodex answered a dialog in the driven browser.
+ *
+ * Answering one is a button pressed in someone's real session, and it is also
+ * the likeliest explanation for a send that behaved strangely around it, so it
+ * belongs in the receipt rather than in nobody's notes.
+ */
+export function answeredDialogWarning(types) {
+    if (types.length === 0)
+        return undefined;
+    const counts = new Map();
+    for (const type of types)
+        counts.set(type, (counts.get(type) ?? 0) + 1);
+    const listed = [...counts]
+        .map(([type, count]) => (count > 1 ? `${type} x${count}` : type))
+        .join(", ");
+    const accepted = types.some((type) => type === "beforeunload");
+    const action = accepted
+        ? "accepted the page's leave prompt and dismissed the rest"
+        : "dismissed without agreeing to it";
+    return (`dialog_answered: a JavaScript dialog appeared in the ChatGPT window during this send (${listed}) and prodex ${action}, ` +
+        "because a dialog left open halts the page and nothing after it would have run.");
+}
+/**
+ * The surface a picker listing was read from: the checked toggle where one is
+ * drawn (the home screen), else the choice ChatGPT persists - which is what the
+ * app itself reads on the pages that draw no toggle. Undefined when neither
+ * says anything.
+ */
+export function surfaceFromProbe(probe) {
+    const checked = probe?.surfaces?.find((entry) => entry.checked)?.label;
+    if (checked)
+        return checked;
+    const stored = (probe?.storedMode ?? "").trim().replace(/^"|"$/g, "").toLowerCase();
+    if (stored === "chat")
+        return "Chat";
+    if (stored === "work")
+        return "Work";
+    return undefined;
+}