Expired50% confidenceFactTime unknown
CloakBrowser's maintenance cadence typically follows up with updates within one to two weeks after a major browser version release.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
7/2/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 9/30/2026(expired)
Sources
Related Claims
UnverifiedCursor needs to periodically merge upstream VSCode updates, and version synchronization typically has a delay of days to weeks, which may cause compatibility issues for some extensions that depend on the latest APIs.62% similarUnverifiedInternal research at Google shows that the average update delay for documentation corresponding to code changes exceeds two weeks.58% similarUnverifiedChrome's automatic update system checks for extension updates every few hours by default, so users naturally experience a delay of several hours before actually receiving an update.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/55846API
curl https://kongchang.com/api/v1/knowledge/claims/55846MCP
get_claim(id=55846)