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 workspage covers the session lifecycle in detail. Because a session runs Claude Code, the same OpenTelemetry tracing used for
Claude Agent SDK tracingworks 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, followAnthropic’s setup guidefirst.## Steps
1
2
Create an Anthropic-hosted environment
Go to
in your Claude admin settings and create a new Anthropic-hosted environment. Name it something like “Claude Tag Environment”. UnderCloud environments****Network access, pick a setting that lets sessions reachtracing.scorecard.io
. The example below uses Full access.In the** Environment variables**field, add the following, one per line asKEY=value
. Substitute your API key and project ID from the previous step.These variables are available to every session that uses this environment. Nothing is traced yet. That happens in the next step.
3
Assign the environment to Claude Tag
This is the step that turns tracing on. Go to
in admin settings and findClaude Tag****Claude Tag’s access. Select the** Slacktab, expand Advanced**, and set** Environment**to the environment you created in step 2.Threads that are already running don’t see configuration changes, so start a new thread after setting the environment.4
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.
What you’ll see #
Each Claude Tag session becomes one record. Record sizes vary a lot because Claude Tag runs several kinds of sessions: 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 hasheduser.id
, session IDs, and yourscorecard.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.
Next Steps #
Tracing Features #
Learn about advanced tracing patterns and trace grouping
Metrics #
Create custom metrics to evaluate Claude Tag’s performance