Planned data collection
The sensor is designed to report tool call activity from inside the VM to the deploying customer’s Kontext workspace. We will document which fields the package sends and how the workspace’s data collection settings apply to those fields before rollout. The sensor will retrieve policy and send reports over HTTPS on TCP port 443 toapi.kontext.security, or to the Kontext API URL configured by the customer. It will authenticate with a customer-scoped install token that an admin can revoke in Kontext. Keep that token out of the Claude Desktop install arguments file, which is for identifiers.
Deploy and verify
Follow these steps once Anthropic approves the integration and Kontext supplies a signed package and vendor ID. Use a Claude Desktop release that includes that vendor ID and key and meets Anthropic’s platform requirements. Use the package for the VM’s CPU architecture: arm64 for Apple silicon Macs and Arm-based Windows PCs, x86_64 for Intel Macs and x64 Windows PCs.- Copy the package and its detached signature, named as the package plus
.sig, into one folder that ordinary users can’t write to, nor any folder above it. On Windows, use the system drive and no symbolic links or junctions on the path. - Set
coworkEDRIntegrationto the full package path andcoworkEDRIntegrationVendorto Kontext’s vendor ID, in lower case. On macOS, set both in an MDM profile. On Windows, set both as string values underHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Claude. - Quit and reopen Claude Desktop. On Windows, quit with File → Exit.
cowork-edr-integration.txt. A run marked kind=installed means the installer exited without an error, not that the sensor is running. When the installer fails, the file shows the end of its output.
Stop future installs
Clear thecoworkEDRIntegration setting through device management to stop future installs. An installed sensor requires a separate uninstall procedure. Previously reported activity remains in the workspace and follows your workspace’s retention and deletion process.