@youdie006/prodex 0.16.15 → 0.16.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli-pro.js +6 -1
- package/package.json +1 -1
package/dist/cli-pro.js
CHANGED
|
@@ -602,7 +602,12 @@ export async function runAskProCommand(rest, io) {
|
|
|
602
602
|
const busyWaitMs = readPositiveIntegerFlag(parsedAskPro.optionArgs, "--busy-wait-ms");
|
|
603
603
|
// Pro extended can legitimately think for minutes, so its default timeout is
|
|
604
604
|
// higher; an explicit --timeout-ms always wins.
|
|
605
|
-
|
|
605
|
+
// Pro reasoning routinely runs for many minutes (a real consult measured
|
|
606
|
+
// ~13 minutes). The elevated default used to be keyed to the removed
|
|
607
|
+
// --pro-mode, so --model Pro sends fell back to 90s and chronically timed
|
|
608
|
+
// out. Any effective Pro selection now defaults to 15 minutes.
|
|
609
|
+
const effectiveProSelection = selectionProMode !== undefined || (selectionModel !== undefined && /pro/i.test(selectionModel));
|
|
610
|
+
const defaultBrowserTimeoutMs = effectiveProSelection ? 900_000 : 90_000;
|
|
606
611
|
const browserTimeoutMs = hasSendMode
|
|
607
612
|
? (readPositiveIntegerFlag(parsedAskPro.optionArgs, "--timeout-ms") ?? defaultBrowserTimeoutMs)
|
|
608
613
|
: undefined;
|