CHAPTERS
- 0:12 – 0:43
Launch announcement: Claude Tag for in-the-flow team collaboration
Lidia introduces Claude Tag, a new way to “tag Claude in” directly where teams already coordinate work. She frames it as a workflow Anthropic has been using internally for most of the year.
- •Claude Tag is launched as a collaboration feature for teams
- •Designed to work right alongside existing team workflows
- •Presented as “how we work now” at Anthropic
- 0:43 – 0:49
Internal adoption and impact: opening most product PRs
The video highlights how deeply Claude Tag is already embedded at Anthropic. It cites a concrete metric to signal real operational usage rather than a demo-only feature.
- •Claude Tag opens 65% of Anthropic’s product pull requests
- •Positioned as a proven internal workflow, not a pilot
- •Sets expectations that Claude can drive real engineering output
- 0:49 – 0:55
Pre-ship engineering scenario: sales-driven priority shift
A near-launch team receives input from sales that a specific feature is blocking major deals. This sets up a realistic, time-sensitive context where coordination speed matters.
- •Team is about a week from shipping
- •Sales flags scheduled exports as a top deal-blocking feature
- •Engineering needs to respond quickly to external pressure
- 0:55 – 1:01
Multiplayer thread collaboration: tagging Claude into the discussion
The workflow is shown as “multiplayer,” with humans and Claude collaborating inside the same group thread. Claude follows the evolving conversation and reacts to decisions in real time.
- •Claude is tagged directly in the group thread
- •Claude tracks the thread context as the team discusses options
- •Responds to product decisions as they happen
- 1:01 – 1:07
From conversation to code: Claude opens a PR and ships the change
Claude translates the team’s discussion into concrete engineering action by opening a pull request and landing the change. The emphasis is on reducing handoffs and accelerating delivery.
- •Claude opens the PR from within the workflow
- •Claude lands the change (end-to-end contribution)
- •Demonstrates execution, not just advice
- 1:07 – 1:13
Codebase understanding + scoping: knowing what to change and where
The video stresses that Claude can navigate the codebase and identify the right location for the feature work. It also introduces the idea of per-channel context scoping for different teams.
- •Claude knows what the feature is and where it lives in the codebase
- •Scopes context by channel/team to stay relevant
- •Reduces time spent orienting and searching
- 1:13 – 1:21
Team memory over time: retaining context as work unfolds
Claude builds memory as work happens, allowing it to connect changes to downstream needs. This helps keep teams aligned without repeated re-explanation.
- •Memory accumulates over time within the workflow
- •Claude understands implications beyond the immediate task
- •Helps prevent loss of context across conversations
- 1:21 – 1:28
Cross-team acceleration: anticipating downstream impacts (e.g., marketing)
Claude recognizes that an engineering change affects launch marketing and helps keep things moving. The goal is to eliminate cross-team communication lag by proactively connecting dots.
- •Claude notes when changes affect launch marketing
- •Keeps the team moving without typical cross-team delays
- •Supports coordination across functions
- 1:28 – 1:36
Direct document action: edits without switching tools
The workflow includes Claude making edits directly rather than requiring someone to open a document system manually. This highlights tool access and task execution in-place.
- •A team member doesn’t need to open Drive to make edits
- •Claude performs the edit itself
- •Emphasizes reduced context switching
- 1:36 – 1:43
Permissions model: Claude has its own account and scoped access
Claude operates with its own accounts and permissions, assigned per team and per channel. The video distinguishes what Claude can access in legal versus engineering contexts.
- •Claude has its own accounts and permissions
- •Access is configured per team/per channel
- •Legal channels can expose contracts; engineering channels can expose code
- 1:43
Hard boundaries and compliant memory: can’t access what it isn’t granted
The demo underlines that access restrictions are enforced technically, not just by instruction-following. Memory follows the same boundaries, preserving privacy between channels and DMs.
- •Claude cannot see or edit resources outside a channel’s permissions
- •Tagging Claude from legal to edit code won’t work because it can’t access it
- •Memory stays within private channels/DMs and doesn’t leak across boundaries
Auditability and call to action: logged credentials and try it in a channel
The close reiterates that Claude’s actions are attributable and logged, since it uses its own credentials. Viewers are encouraged to add Claude to a channel, tag it in, and share feedback.
- •Every credential used is logged via Claude’s own account
- •Tagging Claude changes day-to-day team workflows
- •CTA: add Claude to a channel, tag it in, and report impressions
