Claude Tag Adds Personal Connectors to Shared Channels
Anthropic announced that Claude Tag, its Slack-native AI teammate, can now use an individual's personal claude.ai connectors, such as Google Drive, calendar, or CRM accounts, when responding inside shared team channels. Previously Claude Tag in a channel could only draw on connectors the team had attached; now a single request can blend shared channel context with a person's own private tools. Anthropic gives users control over disclosure through a review mode that checks responses before posting and an auto mode that posts automatically unless sensitive content is flagged. The feature is rolling out now on Team plans, with Enterprise plans to follow, and every action taken through a personal connector is logged separately under that person's own account.
Key Takeaways
- Claude Tag can now use a person's own claude.ai connectors (Google Drive, calendar, CRM) inside a shared Slack channel, not just the connectors the team attached.
- A worked example shows Claude combining a shared GitHub connector with a private Google Drive doc in one response, without exposing that document to the rest of the channel.
- Review mode holds every response for a manual check before it posts, giving individuals a way to vet output before teammates see it.
- Auto mode posts automatically but flags likely-sensitive content for review first, balancing speed against exposure risk.
- Enterprise admins will be able to force review mode org-wide, removing the auto-post option for their organization.
- The rollout is staged by plan tier, live now on Team plans with Enterprise support still to come.
A Single Claude, Blended With Personal Tools
Claude Tag, Anthropic's AI teammate that lives inside Slack, has so far worked from whatever connectors a team attaches to a shared channel: a GitHub repository, a shared Drive folder, a project tracker. Anthropic announced that Claude Tag can now also reach into a specific person's own claude.ai connectors, such as their personal Google Drive, calendar, or CRM account, when they ask for something inside a shared channel.
The example Anthropic gives: an employee named Priya, working in a #checkout-migration channel, asks Claude to "check my Google Drive doc 'Checkout migration, Q3' against what we've shipped." Claude reads merged pull requests through the channel's shared GitHub connector and pulls Priya's own planning document through her personal Google Drive connector, then compares the two. No one else in the channel needs access to that document for the comparison to happen.
Two Ways to Stay in Control
Because a personal connector can surface information only the requester is meant to see, Anthropic built two disclosure modes into the feature. Review mode holds Claude's response for the requester to check before it posts to the channel. Auto mode posts automatically, but flags anything Claude judges to be sensitive for manual review first. On Enterprise plans, admins will be able to require review mode for everyone, removing the auto-post option entirely.
Every action Claude takes through a personal connector is logged in that tool's own activity log under the requesting employee's account, kept separate from the record of the channel's shared work.
Rollout
Personal connectors in Claude Tag are rolling out now on Team plans, with Enterprise plans to follow.