Claude Cowork
Overview
The Anthropic Claude Cowork input receives OTel telemetry data emitted by Claude Cowork, Anthropic's collaborative coding product in the Claude desktop app. Claude Cowork exports OpenTelemetry log events for monitoring session activity, prompts, tool usage, API calls, and cost.
Requirements
There is no configuration needed at the input level in Monad. Simply create a Claude Cowork input and attach it to a pipeline.
All configuration is done in the Anthropic admin console. Note the following pre-requisites from Anthropic:
- Plan: Team or Enterprise
- Claude desktop app: version
1.1.4173or later - Scope: monitoring is configured organization-wide by an admin — there is no per-user setup
Claude Cowork Configuration
To send telemetry from Claude Cowork to Monad, you need:
- A Monad organization API key with the
pipeline:data:writepermission - The pipeline ID of the pipeline with your Claude Cowork input
Steps
-
In the Claude desktop app, navigate to Admin settings → Cowork.
-
In the OTel configuration panel, set:
Field Value OTLP endpoint https://<pipeline-id>.data.monad.com:4318OTLP protocol http/protobuf(recommended) orhttp/jsonOTLP headers Authorization=ApiKey <your-api-key> -
Save the settings.
-
Start a new Cowork session — existing sessions won't pick up the new configuration.
Your pipeline's ingest hostname, <pipeline-id>.data.monad.com, tells Monad which pipeline the telemetry belongs to. Cowork does not currently support the gRPC OTLP protocol, so use one of the HTTP variants on port 4318.
Self-hosted deployments
A per-pipeline ingest host needs the *.data.<your Monad domain> wildcard in place: a DNS record plus a matching certificate SAN. Monad Cloud has this. A self-hosted deployment has it only if whoever installed Monad set it up, so check with them if you are not sure. See Customer Helm Install for the setup.
Without it, point the exporter at your own Monad hostname (https://<your-monad-host>:4318 for OTLP/HTTP, :4317 for gRPC) and name the pipeline with a header instead: Monad-Pipeline-Id: <pipeline-id>, or the lower-case monad-pipeline-id metadata key for gRPC. Everything else, including the API key, is the same.
Content Capture (optional)
By default, exported events contain metadata only. To also capture prompt text, model responses, and tool inputs, enable the otlpContentCapture setting on the admin config with any of:
userPrompts— include user prompt textassistantResponses— include model response text (truncated at ~60 KB)toolDetails— include tool parameters (truncated at ~4 KB)
Related Articles
- Claude Cowork — OpenTelemetry Monitoring
- Monad OpenTelemetry Input
- OpenTelemetry OTLP Exporter Configuration
Sync frequency
This is a push (receiver) input: Monad ingests records as the source sends them, so there is no polling interval. See Input Sync Frequency for details.