@youdie006/prodex 0.40.48 → 0.40.49

package/dist/chatgpt-browser.js

@@ -1150,7 +1150,8 @@ export function shouldRecoverThreadNavigation(args) {
     return !chatGptUrlsReferToSameTarget(currentUrl, pinnedThreadUrl);
 }
 export function hasFreshChatGptAnswer(previousAssistantMessageCount, state) {
-    return state.assistantMessageCount > previousAssistantMessageCount && isUsableChatGptAnswer(state.answer) && !state.generating;
+    return state.assistantMessageCount > previousAssistantMessageCount && isUsableChatGptAnswer(state.answer) && !state.generating &&
+        state.answerRenderFailed !== true;
 }
 // The acceptance phase waits for the prompt to POST (a new user/assistant
 // message), not for the answer. So a timeout here almost never means "slow
@@ -1193,7 +1194,8 @@ export function acceptanceTimeoutError(ctx) {
     });
 }
 export function hasPartialChatGptAnswer(previousAssistantMessageCount, state) {
-    return state.assistantMessageCount > previousAssistantMessageCount && isUsableChatGptAnswer(state.answer);
+    return state.assistantMessageCount > previousAssistantMessageCount && isUsableChatGptAnswer(state.answer) &&
+        state.answerRenderFailed !== true;
 }
 /**
  * True when the tab is on a fresh, empty ChatGPT chat: the root URL (not a
@@ -1590,6 +1592,21 @@ export function chatGptBlockerErrorFromAnswerState(state) {
 export function chatGptBlockerFromAnswerState(state) {
     return detectChatGptPageBlocker(state);
 }
+/**
+ * The answer exists, but the page shows "This response couldn’t load" in
+ * its place. Measured 2026-10-30 in the browser container, where Chromium could
+ * not start threads: the conversation held the finished answer, and loading
+ * the thread again drew it.
+ */
+export function answerRenderFailedBlocker(thread) {
+    return {
+        code: "answer_render_failed",
+        message: "ChatGPT answered, but the page could not display the answer (it shows \"This response couldn’t load\"). No answer was returned.",
+        retryable: false,
+        next_step: "Recovery loads the conversation again and reads the answer.",
+        ...(thread ? { thread } : {})
+    };
+}
 function submittedRequestBlocker(blocker, requestId, thread) {
     return {
         ...blocker,
@@ -2884,6 +2901,64 @@ export function sidebarProjectRowPointExpression(name) {
     return { ok: true, x: Math.round(r.x + Math.min(r.width / 3, 60)), y: Math.round(r.y + r.height / 2) };
   })()`;
 }
+/**
+ * Show the projects the sidebar keeps behind "Show more".
+ *
+ * Measured 2026-10-30 on WSL: the sidebar listed 9 project rows (4 pinned, 5
+ * under Projects) and a "Show more" button under the Projects section;
+ * pressing it added 16 more rows that were not in the page at all before. A
+ * --project send for any of them failed as "project not found in sidebar (9
+ * projects visible)". The button has no label of its own, so it is found as
+ * the ghost button of a section that lists projects, outside every row, and
+ * not the section's toggle; its English text is the fallback. The sidebar
+ * offers nothing to fold the list again, so it stays shown.
+ */
+export function expandSidebarProjectsExpression() {
+    return `(async () => {
+    const projectRows = (root) => root.querySelectorAll("[data-app-action-sidebar-project-row]").length;
+    const before = projectRows(document);
+    const showMore = (button) =>
+      !button.closest("[data-app-action-sidebar-project-row],[data-sidebar-project-container-id^='project:']") &&
+      !button.hasAttribute("data-app-action-sidebar-section-toggle") &&
+      !button.getAttribute("aria-label") &&
+      (button.getAttribute("data-variant") === "ghost" || /^show more$/i.test((button.innerText || "").trim())) &&
+      button.getClientRects().length > 0;
+    const sections = [...document.querySelectorAll("section[data-app-action-sidebar-section]")].filter((section) => projectRows(section) > 0);
+    const more = sections.flatMap((section) => [...section.querySelectorAll("button")]).find(showMore);
+    if (!more) return { clicked: false, before, after: before };
+    more.click();
+    for (let waited = 0; waited < 3000 && projectRows(document) <= before; waited += 100) {
+      await new Promise((resolve) => setTimeout(resolve, 100));
+    }
+    return { clicked: true, before, after: projectRows(document) };
+  })()`;
+}
+/**
+ * The sidebar row of an existing project, shown first if it is behind "Show
+ * more". Polls, because right after a --new-chat navigation the sidebar's
+ * Projects section has not hydrated yet (measured live: "0 projects visible"
+ * on the first read, rows appear moments later) - the same class of race as
+ * the model-selector button after new-chat (0.15.7).
+ */
+export async function findSidebarProjectRow(cdp, project, timeoutMs = 6_000) {
+    let hit = { ok: false };
+    let expanded = false;
+    const deadline = Date.now() + timeoutMs;
+    for (;;) {
+        hit = await cdp.evaluate(projectItemRectExpression(project));
+        if (hit.ok && hit.x !== undefined && hit.y !== undefined)
+            return hit;
+        if (!expanded && /project not found in sidebar/.test(hit.reason ?? "")) {
+            const shown = await cdp.evaluate(expandSidebarProjectsExpression());
+            expanded = shown?.clicked === true;
+            if (expanded)
+                continue;
+        }
+        if (Date.now() >= deadline)
+            return hit;
+        await sleep(300);
+    }
+}
 /** Hover a project row so its hover-only controls can be clicked. A no-op on the older sidebar. */
 async function revealSidebarProjectControls(cdp, name) {
     const point = await cdp.evaluate(sidebarProjectRowPointExpression(name));
@@ -3775,21 +3850,7 @@ async function waitForComposerProjectBinding(cdp, project, timeoutMs) {
 // question, not this one's.
 async function navigateToExistingProject(cdp, project) {
     const hrefBefore = await cdp.evaluate("location.href");
-    // Poll for the project row instead of a single check: right after a
-    // --new-chat navigation the sidebar's Projects section has not hydrated yet
-    // (measured live: "0 projects visible" on the first read, rows appear
-    // moments later) - the same class of race as the model-selector button
-    // after new-chat (0.15.7).
-    let hit = { ok: false };
-    const projectDeadline = Date.now() + 6_000;
-    for (;;) {
-        hit = await cdp.evaluate(projectItemRectExpression(project));
-        if (hit.ok && hit.x !== undefined && hit.y !== undefined)
-            break;
-        if (Date.now() >= projectDeadline)
-            break;
-        await sleep(300);
-    }
+    const hit = await findSidebarProjectRow(cdp, project);
     if (!hit.ok || hit.x === undefined || hit.y === undefined) {
         const detail = hit.reason && hit.reason !== "project not found in sidebar" ? ` (${hit.reason})` : "";
         throw new Error(`ChatGPT project not found in sidebar: ${project}${detail} List the visible names with \`prodex pro browser projects\`.`);
@@ -3981,6 +4042,8 @@ export async function recoverChatGptAnswerFromThread(options) {
     let lastAnswer = "";
     let lastObservedUrl = "";
     let completed = false;
+    let renderFailed = false;
+    let reloadedForRenderFailure = false;
     try {
         await cdp.send("Runtime.enable");
         // In-tab navigation (location.assign, not Page.navigate which has crashed the
@@ -4033,6 +4096,21 @@ export async function recoverChatGptAnswerFromThread(options) {
                     thread: url
                 });
             }
+            // The tab may already be on the thread with the page's error in place
+            // of the answer, so recovery loads the thread once more to draw it.
+            if (state.answerRenderFailed && !state.generating && state.assistantMessageCount > 0) {
+                renderFailed = true;
+                stableRuns = 0;
+                lastAnswer = "";
+                if (!reloadedForRenderFailure) {
+                    reloadedForRenderFailure = true;
+                    await evaluateOnPage(page.page, markDocumentForReloadExpression());
+                    await navigateIdleChatGptPage(page.page, url);
+                    await waitForReloadedDocument(page.page, deadline);
+                }
+                continue;
+            }
+            renderFailed = false;
             // Require a REAL assistant message, not answerExpression's page-chrome
             // fallback (empty assistant returns sidebar/nav text): the thread's
             // conversation loads asynchronously after navigation, so keep polling.
@@ -4057,6 +4135,13 @@ export async function recoverChatGptAnswerFromThread(options) {
     }
     if (!completed) {
         const targetMatched = Boolean(state && chatGptUrlsReferToSameTarget(state.url, url));
+        if (targetMatched && renderFailed) {
+            throw new ChatGptBrowserBlockerError({
+                ...answerRenderFailedBlocker(url),
+                retryable: true,
+                next_step: "The page still could not display the answer after loading the conversation again. Check that the browser is not short of memory or processes, then rerun recovery."
+            });
+        }
         const hasUsableAnswer = Boolean(state && state.assistantMessageCount > 0 && isUsableChatGptAnswer(state.answer));
         const code = !targetMatched
             ? "thread_target_mismatch"
@@ -4609,6 +4694,7 @@ export async function sendChatGptPrompt(options) {
     expandingPolls = 0;
     let nonTextPolls = 0;
     let nonTextSettled = false;
+    let renderFailedPolls = 0;
     const answerIsStable = createChatGptAnswerStabilityTracker();
     while (Date.now() - started < timeoutMs) {
         await sleep(1000);
@@ -4680,6 +4766,16 @@ export async function sendChatGptPrompt(options) {
             continue;
         }
         nonTextPolls = 0;
+        // Two reads in a row, so a failure the renderer is about to replace does
+        // not end the send.
+        if (finalState.answerRenderFailed && !finalState.generating && finalState.assistantMessageCount > beforeSubmit.assistantMessageCount) {
+            renderFailedPolls += 1;
+            if (renderFailedPolls >= 2) {
+                throw attachSendWarnings(new ChatGptBrowserBlockerError(submittedRequestBlocker(answerRenderFailedBlocker(pinnedThreadUrl), requestId, pinnedThreadUrl)), sendWarnings);
+            }
+            continue;
+        }
+        renderFailedPolls = 0;
         if (!hasFreshChatGptAnswer(beforeSubmit.assistantMessageCount, finalState))
             continue;
         // A "fresh" answer must also be stable: ChatGPT can momentarily look done
@@ -5012,7 +5108,10 @@ export function resolveProjectToDelete(projects, request) {
     return { ok: true, id: matches[0].id, name: matches[0].name };
 }
 export async function listChatGptProjectsWithIds(input = {}) {
-    return listVisibleChatGptNavigation(input, projectsWithIdsExpression());
+    return listVisibleChatGptNavigation(input, `(async () => {
+    await ${expandSidebarProjectsExpression()};
+    return ${projectsWithIdsExpression()};
+  })()`);
 }
 /** Project deletion has no bounded visible-DOM implementation. */
 export async function deleteChatGptProject(_input) {
@@ -5064,6 +5163,11 @@ export async function listChatGptSidebarProjects(input = {}) {
             break;
         await sleep(300);
     }
+    if (projects.length > 0) {
+        const shown = await evaluateOnPage(page, expandSidebarProjectsExpression());
+        if (shown?.clicked)
+            projects = await evaluateOnPage(page, sidebarProjectNamesExpression());
+    }
     return { url: status.url, projects };
 }
 /**
@@ -6780,6 +6884,12 @@ export function answerExpression() {
           return Boolean(lastUser.node.compareDocumentPosition(img) & Node.DOCUMENT_POSITION_FOLLOWING);
         });
       })(),
+      // The newer answer renderer, when it cannot draw an answer, puts
+      // div[role=status][data-dil-render-failed] reading "This response
+      // couldn’t load" in its place (measured 2026-10-30, while ChatGPT
+      // held the finished answer), and that sentence was saved as the answer.
+      answerRenderFailed: Boolean(assistant && [assistant.textNode, assistant.node].some((node) =>
+        node && typeof node.querySelector === "function" && node.querySelector("[data-dil-render-failed]"))),
       // ChatGPT tags each assistant message with the model that produced it -
       // the only ground truth for "did the Pro selection actually take".
       modelSlug: assistant ? assistant.modelSlug : undefined,

package/dist/cli-pro.js

@@ -1236,6 +1236,11 @@ export async function runAskProCommand(rest, io, beforeSend) {
     // --tool turns on a composer tool (deep-research, web-search,
     // create-image, or any label the menu shows) for this send.
     const tools = readRepeatedFlag(parsedAskPro.optionArgs, "--tool");
+    // A tool is opened by its label, so a value that is only spaces names none:
+    // the prompt went out with no tool and nothing said so.
+    if (tools.some((tool) => !tool.trim())) {
+        throw new Error("--tool is blank; name a composer tool (web-search, create-image), or leave the option out.");
+    }
     if (tools.length > 0 && !hasSendMode) {
         throw new Error("--tool only applies when sending (`prodex pro browser ask`); the dry-run preview cannot open ChatGPT's tools menu.");
     }

package/dist/continue-thread.js

@@ -94,9 +94,11 @@ export function threadMatchesProject(threadUrl, project, knownProjectIds) {
     // of them slug to "". The id is the only thing that identifies those, and
     // the caller reads it off the live sidebar.
     const slug = chatGptProjectSlug(project);
-    // The id comes first and the name follows it, so an exact suffix match keeps
-    // "notes" from answering for "notes-archive".
-    if (slug && projectSegment.toLowerCase().endsWith(`-${slug}`))
+    // The segment is "g-p-", the id, a dash and the name, so the name has to be
+    // all that follows the id. A suffix test let "notes" answer for "my-notes";
+    // a prefix test would let it answer for "notes-archive".
+    const named = /^g-p-[0-9a-f]+-(.+)$/i.exec(projectSegment)?.[1]?.toLowerCase();
+    if (slug && named === slug)
         return true;
     // No name in the URL: fall back to the id this project has been seen using.
     // Nothing is guessed - the id came from another record of the same project -

package/docs/releasing.md

@@ -16,6 +16,24 @@ Release target: `v0.40.13` on `main`. The GitHub Release records the resolved co
 
 The release adds a guarded, opt-in transition and more accurate blocker reporting. It does not claim that headless Pro consultation is verified on either deployment target or that authentication can be retained indefinitely.
 
+## Browser Incident 2026-10-30: WSL browser container out of threads
+
+**What happened**
+- A probe consult through the WSL container (`prodex-browser-browser-1`, branch build reporting 0.40.18) came back `done`, request verified, with the answer "This response couldn’t load". The conversation held the real answer ("OK"). The page had drawn its own error in its place (`div[role=status][data-dil-render-failed]`).
+- Cause: the container allowed 256 processes and threads. Chromium and the service used about 171 with one ChatGPT tab, and 17 stdio MCP servers (16 Claude Code sessions on the host, about 7 threads each) took the rest. Chromium logged `pthread_create: Resource temporarily unavailable` during the send.
+- A reload of that thread while diagnosing it failed the same way, and then `Zygote could not fork`. After that Chromium could start no renderer at all. The tab stayed `browser_tab_crashed`, and prodex's one same-address reload before a send crashed again within 300 ms, so every consult through the container failed.
+- M3's container was checked the same day: 151 of 256 in use, with 1 MCP server and no thread errors in 72 hours.
+
+**Recovery (maintainer approved each step)**
+- `docker update --pids-limit 1024 prodex-browser-browser-1` raised the limit in place. The thread errors stopped, but the browser still could not start renderers.
+- `docker restart prodex-browser-browser-1`, after the container's send lock was confirmed free. The limit stays 1024 across restarts. Health was `healthy` within seconds, `container-client.mjs status` reported `ready: true`, and a fresh-chat consult with markdown in its prompt answered "OK" with its request verified. No thread errors were logged after the restart.
+- The restart dropped every client's MCP connection to the container. Each WSL Claude Code session needs `/mcp` to reconnect.
+
+**Fixes**
+- `main` PR #79 (merge `eab9340`, not yet released): a send no longer saves the page's render error as the answer, and recovery loads the thread again to draw it. It was ported to `container/redesign-patches` as `f93b63f`.
+- `container/redesign-patches` `55f2f3e`: `compose.json` sets `pids_limit` to 1024. The running WSL container already has it through `docker update`. M3's container gets it on its next rebuild.
+- Neither container image has been rebuilt with these commits yet.
+
 ## Browser Incident 2026-10-20: M3 headless browser behind Cloudflare
 
 **What happened**
@@ -35,6 +53,26 @@ The release adds a guarded, opt-in transition and more accurate blocker reportin
 **Open**
 - A long-running headless browser ends up behind Cloudflare's check (also noted on WSL, where the Xvfb display is used instead). On macOS there is no virtual display, and a minimized window counts as hidden, so the remaining no-headless option there is a window kept behind others. Changing the headless preference is a design decision that was not made here.
 
+## 0.40.48 Release Record
+
+Release commit `406ae25` on `main` (cut after PRs #74-#78, last merge `7a88f85`); tag `v0.40.48`. Released on the user's go-ahead, promptly because of #76: on 0.40.47, with the machine under load, the page often ignored the press on the model selector and the send was blocked as "ChatGPT model menu did not open after clicking the selector" (9 of 23 sends across five runs, every one starting from a conversation; also twice the same day without added load). #74 (horizontal rules), #75 (block content inside list items), #77 (inline code holding backticks) and #78 (table column alignment), found comparing live answers with the page, went out with it.
+
+**Publishing**
+- `npm run release:verify` passed on the release commit after a build, with nothing else running on the machine.
+- `publish.yml` run 40819980786 passed all six platforms, then npm publish with SLSA v1 provenance and the GitHub Release, which lists the five entries from `CHANGELOG.md`.
+
+**Installed**
+- WSL, M3, Mac mini: `prodex --version` reports 0.40.48. Running services were not restarted: no host stdio MCP servers on WSL, 1 on M3, none on the Mac mini.
+- The maintainer watchdog checkout was pulled to `406ae25` and rebuilt.
+
+**Container**
+- `container/redesign-patches` `7f1a7b9` ports #74, `e8b970d` #75, `4f1670e` #76, `3b947c7` #77 and `e30e649` #78. That branch recognises the picker only through its trigger, so #76's test case for a stray picker beside a closed trigger is left out there. tsc, build, the full suite (2144 tests) and `release:verify` pass on `e30e649`.
+- The images were not rebuilt: the WSL container still runs the `facbd9d` image (`c03be48c060d`) and the M3 container `cfaf881d2fd6`.
+
+**Verified live on installed 0.40.48 (WSL, scratch repo, Instant)**
+- One answer holding a numbered step with a code block, the inline code ``a`b``, a rule and a table aligned left and right came back as written: the code block indented under its step, ``a`b`` intact, `---`, and `| :--- | ---: |`.
+- Six sends with two test suites running on the machine (load average up to 9.4) all went through; a read-only page watcher showed one of them pressing the model selector twice before its menu opened.
+
 ## 0.40.47 Release Record
 
 Release commit `609b1c9` on `main` (cut after PRs #71-#73, last merge `40d7eee`); tag `v0.40.47`. Released promptly because of #72: on 0.40.46 any prompt carrying a url with "&" (a query string, bare or in a markdown link) was answered and then refused as `request_mismatch`, so the answer was not returned. #71 (italic and strikethrough in the newer renderer) and #73 (the `utm_source=chatgpt.com` parameter ChatGPT appends to rendered links) went out with it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@youdie006/prodex",
-  "version": "0.40.48",
+  "version": "0.40.49",
   "description": "Local receipt bus for coordinating Codex execution with ChatGPT Pro/Projects consultation.",
   "author": "youdie006",
   "license": "MIT",