{"version":"2.1.251","anchor":"web-fetching-capped-at-15-turns-and-runs-in-the-foreground","canonical_anchor":"web-fetching-capped-at-15-turns-and-runs-in-the-foreground","heading":"Web fetching capped at 15 turns and runs in the foreground","tier":"notice","area":"Web Fetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/web-fetching-capped-at-15-turns-and-runs-in-the-foreground","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Web fetching capped at 15 turns and runs in the foreground\n\nWeb fetching is capped at 15 turns and runs in the foreground unless you background it.\n\n**What**\n\nThe built-in web-fetching helper is now bounded to 15 turns, where its configuration previously set no cap. Its instructions were also reframed: it runs in the foreground and returns its report as the tool result, and backgrounding is now the exception you opt into with `run_in_background: true` when you have independent work to do meanwhile.\n\n**Details**\n\n- Live for everyone using the web-fetch tool; no gate.\n\n**Evidence**\n\n`maxTurns: 15`\n\n- Area: Web Fetch\n- Names: `run_in_background`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}