@zenrows/cli 1.13.0 → 1.13.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## [1.13.1](https://github.com/ZenRows/cli/compare/v1.13.0...v1.13.1) (2026-11-06)
+
+
+### Behaviour Changes
+
+* **fetch:** the default --timeout is 200 s instead of 120 s, so a slow request gets the API's full 3 minutes ([07dc59f](https://github.com/ZenRows/cli/commit/07dc59ffecab780e3bfd78ceeee939c14c3b9891))
+
+
+### Bug Fixes
+
+* **fetch:** wait past the API's 3-minute budget before giving up ([07dc59f](https://github.com/ZenRows/cli/commit/07dc59ffecab780e3bfd78ceeee939c14c3b9891))
+
 ## [1.13.0](https://github.com/ZenRows/cli/compare/v1.12.0...v1.13.0) (2026-11-06)
 
 

package/dist/src/cli/commands/fetch.js

@@ -35,7 +35,7 @@ export const fetch_ = {
         "  --output <fmt>         html (default) | markdown | text | pdf",
         "  --screenshot           capture an above-the-fold screenshot",
         "  --out <file>           write the response body to a file",
-        "  --timeout <ms>         client-side timeout (default 120000; above the API's own 90s budget)",
+        "  --timeout <ms>         client-side timeout (default 200000; above the API's own 180s budget)",
         "  --retries <n>          retry 429/502/503/504 and failed connects up to n times (default 0)",
         "  --no-signup            do not auto-create a Free plan account if no key exists",
         "  --json                 print a structured result",

package/dist/src/core/config.js

@@ -14,7 +14,7 @@ export const CONFIG_VERSION = "0.1.0";
  * entrypoint) so core modules — telemetry, signup provenance — can read it
  * without an import cycle. `VERSION` in `cli/index.ts` re-exports this.
  */
-export const CLI_VERSION = "1.13.0"; // x-release-please-version
+export const CLI_VERSION = "1.13.1"; // x-release-please-version
 /** The User-Agent on every request to a Zenrows API. The gateway reads the version from it. */
 export const CLI_USER_AGENT = `zenrows-cli/${CLI_VERSION}`;
 /** Env var to override the Fetch and Extract API base (local/staging testing). */

package/dist/src/core/http.js

@@ -15,7 +15,7 @@ import { agentClientHeader } from "./agent-client.js";
 import { normalizeDomain, PAGE_NOT_RECOGNISED_STEPS, prepareCommand } from "./prepared-domains-api.js";
 /**
  * Client-side timeout for a Fetch and Extract request, deliberately ABOVE the
- * gateway's own 90s request budget.
+ * gateway's own request budget: a Fetch request can take up to 3 minutes.
  *
  * The two must not be equal. When they were both 90s, any request that used
  * the full server budget became a race between our own abort and the API's
@@ -24,9 +24,9 @@ import { normalizeDomain, PAGE_NOT_RECOGNISED_STEPS, prepareCommand } from "./pr
  * client must outlive the server budget so the API always gets the chance to
  * answer for itself.
  */
-export const DEFAULT_TIMEOUT_MS = 120_000;
+export const DEFAULT_TIMEOUT_MS = 200_000;
 /** The gateway's own request budget. Kept here only to justify the default above. */
-export const SERVER_BUDGET_MS = 90_000;
+export const SERVER_BUDGET_MS = 180_000;
 /** No retry starts later than this after the first request. */
 const RETRY_BUDGET_MS = 90_000;
 /** Busy answers from the API, retried with `--retries`. */
@@ -393,7 +393,7 @@ export function extractDomainNotPrepared(url, body) {
  * The CLI gave up waiting before the API answered. This is NOT unreachability:
  * the connection was established and the gateway was still working, so telling
  * the operator to check connectivity would send them at the wrong problem. The
- * elapsed time is included so the 90s server budget is visible in the output.
+ * elapsed time is included so the server budget is visible in the output.
  */
 export function requestTimeout(url, timeoutMs, elapsedMs) {
     const suggestedMs = Math.max(timeoutMs + 60_000, SERVER_BUDGET_MS + 60_000);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zenrows/cli",
-  "version": "1.13.0",
+  "version": "1.13.1",
   "description": "Open-source CLI, MCP, skills, templates, workflows, recipes, and evals layer for giving AI agents reliable access to protected web data through Zenrows cloud infrastructure.",
   "type": "module",
   "license": "MIT",

package/skills/trace-debug/SKILL.md

@@ -32,7 +32,7 @@ zenrows trace export <run-id>     # JSON for sharing
   it. A 429 ("Rate limited") keeps its advice with or without `--retries`: wait
   a few seconds and retry; if it persists, lower concurrency.
 - `REQUEST_TIMEOUT` → the CLI stopped waiting; the API was reached. Raise
-  `--timeout` (default 120000ms, above the API's own 90s budget), or drop
+  `--timeout` (default 200000ms, above the API's own 180s budget), or drop
   `--wait-for` so the request finishes inside that budget and the API returns
   its own error. Not a connectivity problem — do not chase the network.
 - `BACKEND_UNAVAILABLE` → a genuine transport failure (DNS/TCP/TLS). Check