Claude Tag API
A management interface introduced by Anthropic for enterprise administrators. It allows Claude to be enabled per channel in Slack channels through code, with instructions set, model versions selected, guest policies defined, and Access bundles attached, making AI assistant configuration codified and versionable.
Timeline (last 90 days)
The Claude Tag API was released as a beta version, allowing Enterprise administrators to manage Claude per channel in Slack through code.
The Claude Tag API supports enabling Claude per channel rather than enabling it globally and uniformly.
The Claude Tag API allows administrators to set different instruction templates for different channels to change Claude's response style and boundaries.
The Claude Tag API supports specifying the model version used per channel to match the capabilities and costs of different workloads.
The Claude Tag API supports defining guest policies to control the permission boundaries for external guests or non-members interacting with Claude in a channel.
The Claude Tag API supports attaching Access bundles (predefined sets of access permissions) to Slack channels, keeping Claude's availability consistent with the channel's existing permission boundaries.
The Claude Tag API is aimed at Enterprise administrators, and its core capability is fine-grained control at the channel level.
Configuring Claude manually in the Slack backend suits a small number of channels and one-time setup, whereas the API approach suits scaled scenarios.
When adopting the Claude Tag API during beta, it is recommended to put key configurations under version management, retain a manual fallback path, and follow the official changelog.
The specific auditing capabilities of the Claude Tag API at the beta stage have not yet been fully laid out.
2 more timeline events
All Facts (12)
The configuration-as-code approach of the Claude Tag API assumes administrators are willing to handle configuration in an engineering way, which usually holds in large organizations but may not be a priority need in small and medium-sized teams.
50%UnverifiedThe Claude Tag API supports enabling Claude per channel rather than enabling it globally and uniformly.
50%UnverifiedThe Claude Tag API allows administrators to set different instruction templates for different channels to change Claude's response style and boundaries.
50%UnverifiedThe Claude Tag API supports specifying the model version used per channel to match the capabilities and costs of different workloads.
50%UnverifiedThe Claude Tag API supports defining guest policies to control the permission boundaries for external guests or non-members interacting with Claude in a channel.
50%UnverifiedThe Claude Tag API supports attaching Access bundles (predefined sets of access permissions) to Slack channels, keeping Claude's availability consistent with the channel's existing permission boundaries.
50%UnverifiedThe Claude Tag API is aimed at Enterprise administrators, and its core capability is fine-grained control at the channel level.
50%UnverifiedConfiguring Claude manually in the Slack backend suits a small number of channels and one-time setup, whereas the API approach suits scaled scenarios.
50%UnverifiedWhen adopting the Claude Tag API during beta, it is recommended to put key configurations under version management, retain a manual fallback path, and follow the official changelog.
50%UnverifiedThe specific auditing capabilities of the Claude Tag API at the beta stage have not yet been fully laid out.
50%UnverifiedThe information officially disclosed about the Claude Tag API currently focuses on "what it can do" rather than "what the limitations are."
50%UnverifiedThe Claude Tag API was released as a beta version, allowing Enterprise administrators to manage Claude per channel in Slack through code.
50%