Unverified50% confidenceFactExact time
The Chrome extension's history permission is coarse-grained; users can only grant or deny it as a whole at install time and cannot grant partial authorization by domain, time range, or site category.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe safety constraints of Browser use include: the model asks for confirmation before logging in, submitting forms, or triggering purchase/send/delete-type buttons; passwords, card numbers and one-time verification codes are never filled in by the model; and users can restrict in Settings > Browser the sites the model can open and its access to browsing history and downloaded content.63% similarUnverifiedChrome浏览器的File System Access API要求用户为每次会话重新授予权限，不支持后台静默访问，且禁止访问系统敏感目录61% similarUnverifiedThe governance approach based on credential escrow cannot cover browser agents, because they perform pixel-level click operations under a session where the user is already logged in and there are no independent credentials that can be withheld by a gateway.60% similarUnverifiedScreen Awesome 请求零主机权限（zero host permissions），使 Chrome 在系统层面阻止其访问任何外部服务器60% similarUnverifiedTokens must only be placed in the Authorization request header and never in the URL, as doing so would cause them to be recorded in logs and leaked in plaintext.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1010334API
curl https://kongchang.com/api/v1/knowledge/claims/1010334MCP
get_claim(id=1010334)