@youdie006/prodex 0.16.14 → 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.
Files changed (2) hide show
  1. package/dist/cli-pro.js +12 -4
  2. package/package.json +1 -1
package/dist/cli-pro.js CHANGED
@@ -581,10 +581,13 @@ export async function runAskProCommand(rest, io) {
581
581
  // from the confirmed tab).
582
582
  const selectionModel = explicitModel ?? browserDefaults?.model;
583
583
  const selectionProjectNew = explicitProjectNew;
584
- // A persisted default project is suppressed under --new-chat (the point
585
- // is a fresh root chat); an explicit --project still wins.
584
+ // A persisted default project APPLIES under --new-chat: since 0.16.11 a
585
+ // fresh chat inside the project is exactly what "--new-chat + project"
586
+ // produces, and the whole point of pinning a default project is that
587
+ // consults stop landing in the general chat list. Only --target-url
588
+ // (pinned tab) and --project-new suppress it.
586
589
  const selectionProject = explicitProject ??
587
- (normalizedTargetUrl || selectionProjectNew !== undefined || newChat ? undefined : browserDefaults?.project);
590
+ (normalizedTargetUrl || selectionProjectNew !== undefined ? undefined : browserDefaults?.project);
588
591
  const reasoningAxisChosen = explicitProMode !== undefined || explicitEffort !== undefined;
589
592
  const selectionProMode = explicitProMode ?? (reasoningAxisChosen ? undefined : browserDefaults?.pro_mode);
590
593
  const selectionEffort = explicitEffort ?? (reasoningAxisChosen ? undefined : browserDefaults?.effort);
@@ -599,7 +602,12 @@ export async function runAskProCommand(rest, io) {
599
602
  const busyWaitMs = readPositiveIntegerFlag(parsedAskPro.optionArgs, "--busy-wait-ms");
600
603
  // Pro extended can legitimately think for minutes, so its default timeout is
601
604
  // higher; an explicit --timeout-ms always wins.
602
- const defaultBrowserTimeoutMs = selectionProMode === "확장" ? 300_000 : 90_000;
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;
603
611
  const browserTimeoutMs = hasSendMode
604
612
  ? (readPositiveIntegerFlag(parsedAskPro.optionArgs, "--timeout-ms") ?? defaultBrowserTimeoutMs)
605
613
  : undefined;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@youdie006/prodex",
3
- "version": "0.16.14",
3
+ "version": "0.16.16",
4
4
  "description": "Local receipt bus for coordinating Codex execution with ChatGPT Pro/Projects consultation.",
5
5
  "author": "youdie006",
6
6
  "license": "MIT",