Skip to content

docs(tracing): add Claude Tag tracing quickstart - #139

Merged
Yash1hi merged 7 commits into
mainfrom
docs/claude-tag-tracing
Aug 25, 2026
Merged

docs(tracing): add Claude Tag tracing quickstart#139
Yash1hi merged 7 commits into
mainfrom
docs/claude-tag-tracing

Conversation

@Yash1hi

@Yash1hi Yash1hi commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds intro/claude-tag-tracing.mdx, a quickstart for tracing Claude Tag (Claude in Slack) sessions to Scorecard, and links it from the Getting Started nav, the tracing overview, and the Claude Agent SDK tracing quickstart.

Page contents

  • Intro defines a Claude Tag session (one per Slack thread, runs Claude Code in an Anthropic-hosted sandbox) and links to Anthropic's session-lifecycle docs.
  • Five steps: get API key + project ID → create an Anthropic-hosted environment with the OTEL env vars → assign the environment under Claude Tag's access → Slack → Advanced (called out as the step that turns tracing on, with a Warning that a workspace-level environment traces every channel and how to scope per channel) → talk to Claude in Slack → view records.
  • What you'll see section: the session types that show up as records (channel, thread, DM, routine), why record sizes vary, and what a trace contains (Slack author names/handles/IDs, message text, tool inputs/outputs; hashed user.id only, no email/account ID; env vars and API key not included). Based on inspecting 57 sessions from project 1403.

Screenshots (images/claude-tag-*.png)

  • Environment dialog with the tracing variables filled in, Environment variables field highlighted.
  • Claude Tag's access page (full frame) with the Environment dropdown highlighted.
  • Records page (light + dark) rebuilt from unredacted originals with targeted redaction only (Slack channel ID, author name/ID, message body, one name in agent reasoning).

Other changes

  • docs.json: nav entry after Claude Agent SDK tracing.
  • features/tracing.mdx, intro/claude-agent-sdk-tracing.mdx: cross-links.

Verification

  • npx mintlify broken-links passes.
  • Copy went through two humanize passes.

Add a quickstart for tracing Claude Tag (Claude in Slack) sessions to
Scorecard: creating an Anthropic-hosted environment with the tracing
environment variables, assigning it under Claude Tag's access → Slack →
Advanced, and viewing sessions as records. Link the page from the
Getting Started nav, the tracing overview, and the Claude Agent SDK
tracing quickstart.
@mintlify

mintlify Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
scorecard 🟢 Ready View Preview Aug 25, 2026, 6:38 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@github-actions

Copy link
Copy Markdown
Contributor

🖼️ Image Usage Check ✅

All 251 images in the repository are being used! No unused images found.

Great job keeping the repository clean! 🎉

Screenshots: crop out redacted regions (channel list, user turn, agent
thinking) so each image is a single clean example, and add red highlight
boxes around the Environment variables field, the Environment dropdown,
and a session record.

Copy: define what a Claude Tag session is and link to Anthropic's session
lifecycle docs; add a prerequisites step so assigning the environment is
step 3; call out prominently that a workspace-level environment traces
every channel; humanize pass on the rest of the text.
Replace the environment dialog screenshot with one showing the tracing
variables filled in. Restore the full-frame Claude Tag access and
Records screenshots instead of cropped versions, keeping their existing
redactions, and add red highlight boxes to each.
Rebuild the Records screenshots from the unredacted originals, covering
only the Slack channel ID, author name and ID, message body, and the
author's name in the agent's reasoning. Drop the trace-panel tabs
paragraph from the final step.
Describe the session types that show up as records (channel, thread, DM,
routine), why record sizes vary, and what a trace contains, based on
inspecting 57 sessions from a live Claude Tag project.
@James-C137

Copy link
Copy Markdown

No blocking comments, just some thoughts:

  • This adds a page to the Quickstarts section, but the section is a mix of "xyz quickstart" and "xyz tracing", which reads like it should be split into two sections such as "Quickstart" (Scorecard app setup) and "Tracing setup"
  • Page content makes sense, some parts like the "What you'll see" section is slightly hard to understand but the info is correct

@Yash1hi
Yash1hi merged commit 7bbc3e1 into main Aug 25, 2026
7 checks passed
@Yash1hi
Yash1hi deleted the docs/claude-tag-tracing branch August 25, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants