@youdie006/prodex 0.23.0 → 0.23.1

package/dist/cli-help.js

@@ -257,6 +257,14 @@ export function printProBrowserHelp(stdout, sourceCli) {
     const modelsUsage = sourceCli
         ? `${cli} pro browser models${sourceCliOption} [--port 9333] [--timeout-ms 15000]`
         : "prodex pro browser models [--source-cli /absolute/path/to/dist/cli.js] [--port 9333] [--timeout-ms 15000]";
+    const projectsUsage = sourceCli
+        ? `${cli} pro browser projects${sourceCliOption} [--port 9333] [--timeout-ms 15000]  # read-only: exact sidebar project names`
+        : "prodex pro browser projects [--source-cli /absolute/path/to/dist/cli.js] [--port 9333] [--timeout-ms 15000]  # read-only: exact sidebar project names";
+    // A send that outlives its budget is not a lost answer, but only if agents
+    // know this exists - and this help is where onboarding sends them.
+    const recoverUsage = sourceCli
+        ? `${cli} pro browser recover${sourceCliOption} [--cwd /absolute/path/to/repo] [--port 9333] --target-url <thread-url> [--timeout-ms 60000]  # fetch a finished answer (deep research reports too) from a thread whose send timed out`
+        : "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]  # fetch a finished answer (deep research reports too) from a thread whose send timed out";
     stdout(`${cli} pro browser
 
 Commands:
@@ -264,7 +272,9 @@ Commands:
   ${checkUsage}
   ${smokeUsage}
   ${modelsUsage}
+  ${projectsUsage}
   ${askUsage}
+  ${recoverUsage}
 
 Visible-browser sends require a manual browser session and stop on login, captcha, Cloudflare, permission, rate-limit, or usage-limit blockers.
 Model/project selection (ask):

package/dist/cli.js

@@ -322,6 +322,16 @@ repo: ${cwd}
    ${cli} pro browser check${sourceCliOption} --cwd ${quotedCwd}
    ${cli} pro browser smoke${sourceCliOption} --cwd ${quotedCwd}
    Sharing the browser with other agents? Sends queue behind an in-flight response automatically; pass --busy-wait-ms 0 to fail fast instead.
+   Hand ChatGPT a real file - the only way it can open a pdf, pptx, xlsx or image:
+   ${cli} ask --cwd ${quotedCwd} --attach deck.pptx "Review slides 40-60"  # uploads the file itself
+   ${cli} ask --cwd ${quotedCwd} --file notes.md "Summarize"  # pastes a text file's CONTENTS into the prompt
+   Both are restricted to paths inside the repo. Repeat either flag for several files.
+   Turn on a composer tool for one send:
+   ${cli} ask --cwd ${quotedCwd} --tool web-search "What shipped in Node 24?"  # current facts with sources
+   ${cli} ask --cwd ${quotedCwd} --tool deep-research "Compare managed Postgres providers"  # full browsed report; runs ~10 minutes, budget rises to 30
+   Any other label the composer menu shows works too, so a tool ChatGPT adds later needs no prodex release.
+   A send that outlives its budget did not lose the answer - ChatGPT usually finishes after prodex stops waiting:
+   ${cli} pro browser recover --target-url <thread-url> --cwd ${quotedCwd}  # fetches the finished answer (deep research reports too) and records it
 
 2. Let coding agents consult ChatGPT (stdio MCP: Claude, Codex, Cursor, ...):
    ${cli} claude config --cwd ${quotedCwd}${sourceCliOption}

package/package.json

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