Tracing Claude Tag, Anthropic's Slack Agent

Anthropic's Claude Tag, a Slack agent that runs Claude Code in Anthropic-hosted sandboxes, can now be traced to Scorecard using OpenTelemetry, according to a new quickstart guide. The guide instructs Claude organization admins to create an Anthropic-hosted environment with specific environment variables and assign it to Claude Tag, enabling each session to appear as a trace record with user turns, LLM request spans, and tool spans. Claude Tag requires a Team or Enterprise plan, and tracing is limited to hashed user IDs and session IDs, with no email or account ID included.

Claude working inside your team’s Slack workspace https://claude.com/docs/claude-tag/overview . 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 https://claude.com/docs/claude-tag/concepts/how-it-works page covers the session lifecycle in detail. Because a session runs Claude Code, the same OpenTelemetry tracing used for Claude Agent SDK tracing /intro/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 https://claude.com/docs/claude-tag/admins/setup-overview first. 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”. Under https://claude.ai/admin-settings/cloud-environments Cloud environments 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.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 find https://claude.ai/admin-settings/claude-tag Claude Tag Claude Tag’s access . Select the Slack tab, 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 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. Next Steps Tracing Features Learn about advanced tracing patterns and trace grouping Metrics Create custom metrics to evaluate Claude Tag’s performance