You'll notice
Useful3 Signal3
Web fetching is capped at 15 turns and runs in the foreground unless you background it.
What's wrong with this entry?
Anonymous. No account, no email.
run_in_background
What
The 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.
Details
- Live for everyone using the web-fetch tool; no gate.
Evidence
maxTurns: 15
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
WebFetch refuses redirects that leave a trusted docs path
Both mention fetch
-
v2.1.232
Fetched pages are wrapped in an untrusted-content envelope
Both mention fetch
-
v2.1.232
WebFetch reports which local files a fetch actually wrote
Both mention fetch