@youdie006/prodex 0.40.15 → 0.40.17

package/README.md

@@ -191,7 +191,7 @@ The last recorded window mode is reused by later `login` commands and by CLI/MCP
 
 `--headless` may be blocked even with a saved login: a previous test on a signed-in profile stayed on Cloudflare's interstitial past sixty seconds. `--background` verifies the actual handoff and only reports READY when the signed-in composer works headless. A challenge does not prove that the saved login was lost. Only the window is optional; authentication and protection checks still apply.
 
-If a running headless browser needs login, captcha, Cloudflare, or account verification, run `prodex pro browser login --headed --recover-visible`. This is an explicit, guarded switch for a known authentication/protection blocker, not an automatic fallback or a general browser reset. It preserves the profile and page, waits for a clean shutdown, and opens a visible browser for any required manual step. That window is temporary: after it closes, the next launch remains headless. Another challenge stops instead of opening a visible window automatically; an ordinary explicit `login --headed` selects headed mode permanently. A virtual-display browser must still be closed manually before `login --headed`; it is not covered by this headless-only recovery. Merely omitting `--headless` does not switch modes because the saved preference persists. prodex never bypasses protection or force-kills a browser for a mode change.
+If a running headless browser needs login, captcha, Cloudflare, or account verification, run `prodex pro browser login --headed --recover-visible`. This is an explicit, guarded switch for a known authentication/protection blocker, not an automatic fallback or a general browser reset. It preserves the profile and page, waits for a clean shutdown, and opens a visible browser for any required manual step. That window is temporary: after the dedicated browser fully exits, the next launch remains headless. On macOS, closing a window alone may leave Chrome running; prodex stops rather than reopening that temporary visible window. Another challenge also stops instead of opening a visible window automatically; an ordinary explicit `login --headed` selects headed mode permanently. A virtual-display browser must still be closed manually before `login --headed`; it is not covered by this headless-only recovery. Merely omitting `--headless` does not switch modes because the saved preference persists. prodex never bypasses protection or force-kills a browser for a mode change.
 
 Before a prompt is submitted, a browser confirmed to have stopped answering its control port can be ended and started fresh, and the receipt says so (`PRODEX_NO_AUTO_CLEAR=1` turns that off). A browser that is merely slow is left alone. After submission, prodex never auto-resends a lost prompt.
 

package/dist/cli-pro.js

@@ -2082,6 +2082,14 @@ async function attemptMissingChatGptTabRecovery(stderr, options) {
                 throw new ChatGptBrowserBlockerError(status.blocker);
             return false;
         }
+        if (saved?.headless !== true && resolveBrowserWindowMode({ lastLogin: saved, forRelaunch: true }).headless) {
+            throw new ChatGptBrowserBlockerError({
+                code: "browser_mode_transition_required",
+                message: "The temporary visible browser is still running after its ChatGPT tab closed; reopening a tab would show another window.",
+                retryable: false,
+                next_step: "Fully quit only the dedicated browser, then retry to launch the saved profile headlessly. On macOS, closing a window alone does not quit Chrome. Do not log in again solely because this transition stopped."
+            });
+        }
         stderr("recover: the browser is running but its ChatGPT tab was closed; opening one tab and checking the saved login...");
         if (!await openChatGptTab(port))
             return false;
@@ -2282,7 +2290,7 @@ async function completeVisibleAuthRecovery(io, options) {
             sourceCli: options.sourceCli, commandOptions: options.commandOptions
         });
         io.stdout("recovery: visible browser opened with the same profile and page. Complete a manual step only if ChatGPT requests it; no prompt was sent.");
-        io.stdout("recovery: this visible window is temporary. After it closes, the next launch remains headless; another challenge stops without opening a visible window automatically.");
+        io.stdout("recovery: this visible window is temporary. After the dedicated browser fully exits, the next launch remains headless. On macOS, closing its window alone may leave Chrome running; prodex will not reopen that temporary visible window automatically.");
         if (!options.shouldWait)
             return 0;
         const ready = await waitForChatGptLoginReady(io.stderr, {
@@ -3067,6 +3075,21 @@ export function printBrowserLoginGuide(stdout, input) {
                 : input.opened
                     ? "Opened the dedicated Chrome window for ChatGPT."
                     : "Dry run: no browser was opened.");
+    if (noInteractiveWindow && !input.opened && !input.reused) {
+        const previewCommand = formatBrowserLoginCommand(input.sourceCli, {
+            ...input.commandOptions,
+            profileDir: input.profileDir,
+            port: input.port
+        });
+        const modeFlag = input.headless ? "--headless" : "--virtual-display";
+        stdout("");
+        stdout(`Next: run \`${previewCommand} ${modeFlag}\` without \`--dry-run\` to start or reuse Chrome with no visible window.`);
+        stdout("Readiness was not checked. A real launch reuses this profile and reports any login or protection blocker; it does not switch to a visible window automatically.");
+        stdout("");
+        stdout(`Profile: ${input.profileDir}`);
+        stdout(`Debug: http://127.0.0.1:${input.port}`);
+        return;
+    }
     if (noInteractiveWindow && (input.opened || input.reused)) {
         stdout("");
         stdout(input.headless

package/docs/cli-reference.md

@@ -125,7 +125,7 @@ For a one-time interactive login followed by a no-window handoff, run `prodex pr
 
 To inspect an authentication/protection blocker in a running headless browser, explicitly use `prodex pro browser login --headed --recover-visible`. The command requires one verified dedicated headless browser and one ChatGPT page reporting `login_required`, `cloudflare_check`, `captcha_required`, or `permission_required`. It preserves the exact profile and page under the shared send lock, refuses unfinished inputs, active work, dialogs, attachments, extra tabs, and ambiguous identity, and waits for a verified shutdown before launching headed. It does not click, solve, or suppress a security check. Use `--wait` to wait for manual handling or `--no-wait` to return after launch; `--dry-run` performs no browser change. This is headless-only, not a generic reset or a virtual-display switch.
 
-The visible recovery window does not change the headless relaunch preference. Once it closes, both a new `login` launch and an automatic browser restart use headless mode again. Reusing the still-open window with `login --wait` keeps that preference. An ordinary explicit window-mode option or environment override replaces it. There is no automatic headed fallback when the next headless launch encounters another challenge.
+The visible recovery window does not change the headless relaunch preference. Once the dedicated browser fully exits, both a new `login` launch and an automatic browser restart use headless mode again. On macOS, closing its last window may leave the process running: automatic missing-tab recovery stops with `browser_mode_transition_required` instead of opening another visible window. Fully quit only the dedicated browser before retrying; the closed tab alone is not a reason to log in again. Reusing a still-open window with `login --wait` keeps the preference. An ordinary explicit window-mode option or environment override replaces it. There is no automatic headed fallback when the next headless launch encounters another challenge.
 
 If only the ChatGPT tab was closed, MCP and auto-login-enabled CLI requests can reopen one tab in the existing browser before an unsent request. They verify the saved login before sending and never use this path to resend an accepted or uncertain request.
 

package/package.json

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