Page cover

Claude Code and Cowork

Auditing of Claude Code and Cowork activity can be performed by the native Claude OpenTelemetry interface as well as Turngate's custom client side hook.

OTel Configuration

Account Requirements

OTel data is sent from the client to an OTel collector via environment variables. As of March 2026, there are no specific account requirements to configure this collection. However, only Teams and Enterprise accounts can supply configuration from a central location using Server-Managed Settingsarrow-up-right. If you are using Server-Managed Settings, the end user cannot modify the OTel configuration.

Setting up the Claude Code Data Source in the Turngate App

OTel access is controlled via an OTel ingest token. During the onboarding process you will be assigned a token for your org. To get started, go to the Integrations Pagearrow-up-right and start the Claude OTel integration wizard. Walk through the initial steps and then you will be presented with the token and endpoint information.

Copy the token value and store it securely.

Then, set up Claude Code with the following environment:

These environment variables can either be added manually locally or via the Claude Management interface if you have the appropriate Claude license.

Once the integration has been saved within Turngate and environment variables have been appropriately updated, OTel data should be flowing immediately. GIven the nature of OTel, there will be no historic ingestion of logs.

Setting up Cowork

Take the bearer token and endpoint information and put it in the "Monitoring" section of the Cowork settings in the Claude native app.

Other Resources

Claude Server-Managed Settingsarrow-up-right

Claude Monitoring Usagearrow-up-right (OTel Config)

Last updated