You'll notice
Useful2 Signal2
Viewing a running fetch agent's transcript is refused by design, with clearer placeholder wording.
What's wrong with this entry?
Anonymous. No account, no email.
What
Two new messages cover a fetch agent whose transcript cannot be shown: one for an empty report body, one for an agent that has not reported yet. The second says the transcript is raw fetched page content and is not returned, so reading a running web-fetch agent's transcript is refused by design.
Details
- Surfaces only on the web-fetch agent path.
Evidence
[The agent produced no report text.]
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.239
Data-loss-prevention blocks are marked separately from fetch failures
Both mention fetch
-
v2.1.236
Web fetch agent switch moved into per-host state
Both mention fetch