Unverified50% confidenceFactExact time
APX assigns each agent its own browser profile and checks ownership before operations; an agent cannot drive tabs assigned to other agents, and if another agent is controlling a tab, APX rejects the request rather than letting two running instances manipulate the same page simultaneously.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedAPX provides a path for requesting user approval to copy cookies for a specific domain into the APX browser profile; this operation can only be performed by a human, and at runtime the origin name and number of domains can be checked, but cookie values remain on the desktop side.72% similarUnverifiedAPX's chat history, tool call records, sessions and interruption markers are local execution state and are not part of a portable project contract.59% similarUnverifiedAfter verifying that the grant passes, the application must itself issue an access token representing the agent's actual access permissions within that application.57% similarUnverifiedAgent Activity adopts a privacy-by-default design that does not upload data and only collects usage data and crash data after explicit user consent.57% similarUnverifiedPermission systems typically protect the agent itself (approving commands, prohibiting writes outside the project, sandboxing the shell) but not the application around the agent; any interface that renders repository content (preview, Markdown, notebooks, images, embedded browser) is part of the attack surface.56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1068458API
curl https://kongchang.com/api/v1/knowledge/claims/1068458MCP
get_claim(id=1068458)