Claude Tag Tracing

Claude Tag is Claude working inside your team’s Slack workspace. Each thread Claude works in is a session: it starts when someone mentions @Claude, runs Claude Code in an Anthropic-hosted sandbox, and ends when the thread goes quiet. Anthropic’s How Claude Tag works page covers the session lifecycle in detail. Because a session runs Claude Code, the same OpenTelemetry tracing used for Claude Agent SDK tracing works here too. Every session shows up in Scorecard as one record with a trace of user turns, agent reasoning, and tool calls. This quickstart shows how to configure an Anthropic-hosted environment so Claude Tag sessions are traced to Scorecard.

Claude Tag requires a Claude Team or Enterprise plan, and these steps are done by a Claude organization admin. If your Slack workspace doesn’t have Claude Tag yet, follow Anthropic’s setup guide first.

Steps

Get your Scorecard API key and project ID

You’ll need two values from Scorecard:

Your API key from Settings. It starts with ak_.
The ID of the project you want traces to land in.

If the project ID is wrong or invalid, traces are sent to the oldest project in your organization.

Create an Anthropic-hosted environment

Go to Cloud environments in your Claude admin settings and create a new Anthropic-hosted environment. Name it something like “Claude Tag Environment”. Under Network access, pick a setting that lets sessions reach tracing.scorecard.io. The example below uses Full access.In the Environment variables field, add the following, one per line as KEY=value. Substitute your API key and project ID from the previous step.

OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer <your_scorecard_api_key>
ENABLE_BETA_TRACING_DETAILED=1
BETA_TRACING_ENDPOINT=https://tracing.scorecard.io/otel
OTEL_LOG_USER_PROMPTS=1
OTEL_LOG_TOOL_DETAILS=1
OTEL_LOG_TOOL_CONTENT=1
OTEL_RESOURCE_ATTRIBUTES=scorecard.project_id=<your-project-id>

These variables are available to every session that uses this environment. Nothing is traced yet. That happens in the next step.

Assign the environment to Claude Tag

This is the step that turns tracing on. Go to Claude Tag in admin settings and find Claude Tag’s access. Select the Slack tab, expand Advanced, and set Environment to the environment you created in step 2.

Every channel in the workspace is traced. Setting the environment on the Slack workspace applies to every channel Claude works in, and traces include user prompts and tool inputs and outputs. If you only want to trace some channels, leave the workspace setting alone and instead select each channel in the left sidebar and set its Environment there.

Threads that are already running don’t see configuration changes, so start a new thread after setting the environment.

Talk to Claude in Slack

Mention @Claude in a channel it’s been invited to and give it a task. Nothing changes on the Slack side. The session is traced as it runs.

@Claude summarize the open questions in this thread.

View traces in Scorecard

Open the Records page of your project in Scorecard. Each Claude Tag session appears as a record. Click one to open its trace detail panel and see the full session, including tool calls like Slack replies and reactions.

What you’ll see

Each Claude Tag session becomes one record. Record sizes vary a lot because Claude Tag runs several kinds of sessions:

Session	How it starts	What the record looks like
Channel session	Any new top-level message in a channel Claude is in	A few LLM calls, usually ending in an `mcp__slackbot__no_reply_needed` tool call. You get one of these for most messages in the channel, not only the ones addressed to Claude.
Thread session	The channel session hands a task to a thread, or someone replies in a thread Claude is working in	Tens to hundreds of LLM calls, sub-agent tasks, and tool calls (Slack replies, GitHub, Bash). Can run for hours and stitch together many traces.
DM	Someone messages Claude directly	Similar to a thread session.
Routine	A scheduled trigger fires	No Slack messages in the prompt. The routine’s instructions are the prompt, and there’s no channel on the record until Claude posts somewhere.

Inside a record:

User turns are the raw Slack payload Claude receives: message text, author display names, @handles, Slack user IDs, channel IDs, thread participants, attachment file names, message edits, and reactions. In thread sessions this also includes the parent session’s hand-off notes and Claude’s own memory files for the channel.
LLM request spans carry the model, token counts, a system prompt preview, the model output, and tool results as they were fed back to the model.
Tool spans carry the tool name and full inputs and outputs: Slack reply text, Bash commands, file paths, GitHub calls.
Identity is limited to a hashed user.id, session IDs, and your scorecard.project_id. Unlike Claude Code CLI traces, there is no email or account ID. Your environment variables and Scorecard API key are not in the trace.

Introduction

Quickstarts

Core features

Advanced features

Governance, Risk, and Compliance

Steps

What you’ll see

Next Steps

Tracing Features

Metrics

​Steps

​What you’ll see

​Next Steps

Tracing Features

Metrics

Steps

What you’ll see

Next Steps