Anthropic Claude Cowork
Overview
The Anthropic Claude Cowork input receives OpenTelemetry (OTel) events from Claude Cowork, Anthropic's agentic workspace in the Claude desktop app. Cowork exports OTel log events for prompts, model responses, tool usage, API requests, and errors.
Anthropic's export covers Cowork sessions that run on a user's computer, including Cowork tasks that Dispatch starts. It doesn't cover Code tab sessions. Monad ingests whatever Cowork sends to the endpoint and doesn't filter by session type.
Requirements
The input takes no settings. Create a Claude Cowork input and attach it to a pipeline.
Anthropic's prerequisites:
- Plan: Team or Enterprise
- Claude desktop app: version
1.1.4173or later. The content capture behavior described below applies from version1.17377. - Scope: an admin configures the collector once for the whole organization
You also need:
- A Monad organization API key with the
pipeline:data:writepermission - The pipeline ID of the pipeline that contains your Claude Cowork input
Claude Cowork Configuration
Steps
-
Go to Admin settings → Cowork.
-
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 keep the previous settings.
Your pipeline's ingest hostname, <pipeline-id>.data.monad.com, tells Monad which pipeline the events belong to.
Cowork's admin settings offer HTTP only, so use 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.
Network access
Cowork adds your collector's hostname to the session's egress allowlist automatically, so it needs no entry under Admin settings → Capabilities → Network egress.
Your own firewall or proxy must still allow outbound HTTPS to *.data.monad.com on port 4318.
Content Capture
Events always carry metadata.
Whether they also carry content depends on the otlpContentCapture key on each user's computer.
otlpContentCapture isn't a field in Admin settings.
Deploy it with your device management tool to the managed configuration location for each operating system.
It takes effect when Claude Desktop restarts.
On Claude Desktop version 1.17377 or later:
otlpContentCapture | Content that events carry |
|---|---|
| Not set, standard deployment | User prompts, model responses, and toolDetails content |
| Not set, Amazon Bedrock or Google Vertex AI deployment | None (metadata only) |
| A list of categories | The listed categories. userPrompts also includes model responses. |
[] | None (metadata only) |
To export metadata only, set the key to [].
An empty string counts as not set, so on a standard deployment it exports full content.
| Category | Captures |
|---|---|
userPrompts | User prompt text. Also captures model responses. |
assistantResponses | Model response text, truncated at 60 KB |
toolDetails | The arguments each tool was called with (tool_input and tool_parameters), such as shell commands, file paths, URLs, and search patterns, plus a failed tool's error message. In tool_input, strings over 512 characters are truncated and the whole field is limited to about 4K characters. |
toolContent | Tool output content |
rawApiBodies | Inference request and response bodies |
Always sent
These attributes are sent even when otlpContentCapture is []:
workspace.host_paths: the paths of the folders a user connects to a taskuser.email: on standard deployments
If either is sensitive, remove it with the Drop Key transform or obscure it with the Mask transform in your pipeline.
Amazon Bedrock and Google Vertex AI Deployments
On Claude Desktop with Amazon Bedrock or Google Vertex AI, you configure the export with managed configuration keys instead of Admin settings:
otlpEndpoint:https://<pipeline-id>.data.monad.com:4318, without a/v1/logssuffixotlpProtocol:http/protobufotlpHeaders: a JSON object, for example{"Authorization":"ApiKey <your-api-key>"}. For credentials, Anthropic recommendsotlpHeadersHelper.
These deployments differ from standard deployments:
- Events carry metadata only unless
otlpContentCapturelists categories. user.emailand the other Anthropic account attributes are absent. Users are identified by theenduser.idresource attribute, controlled byendUserAttribution, and byprocess.owner.- The export also carries metrics and the
claude-code-desktopandclaude-desktopstreams, which this input receives too.
Monad accepts OTLP over gRPC on port 4317, but use HTTP on port 4318.
With otlpProtocol set to grpc, Cowork exports over http/protobuf instead on Windows and whenever an HTTP proxy is in use, without changing the endpoint, so events sent to port 4317 are lost.
The claude-desktop stream always exports over http/json.
Related Articles
- Claude Cowork — Monitoring
- Claude Desktop on third-party platforms — Telemetry
- 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.