Which Claude plans include the local session endpoints?

Local session endpoints are limited to Claude Enterprise organizations and are in beta. A standalone Claude Console organization with no parent organization cannot use them; that setup uses Admin API keys and can query the Activity Feed only. Organizations already running the Compliance API need no new key, scope, setting, or client update.

Can an admin delete a local session through the Compliance API?

Deletion through the API is not supported for local sessions, and the same holds for remote sessions. The Compliance API can delete chats, files, and projects on demand, but session transcripts are read-only. Local session content is kept for six years by default, or for a shorter window when an organization sets a finite conversation retention period.

Are all Claude Code sessions captured?

Several Claude Code setups are never captured. Sessions are skipped when Claude Code authenticates with a Claude Console API key or runs through Amazon Bedrock, Google Cloud, or Microsoft Foundry, and Claude Code on the web is not captured either. Organizations with HIPAA readiness enabled record no local session data at all.

How do local sessions differ from remote sessions?

Local sessions run on a user's own machine and cover both Cowork and Claude Code, while remote sessions run in Anthropic-managed cloud environments and cover Cowork only. Local session IDs start with clls_ and filter only by a created_at range; remote IDs start with cse_ and also filter by organization and user.

What comes back for organizations using customer-managed encryption keys?

Organizations on customer-managed encryption keys can still list and retrieve local sessions, but transcript content is not currently returned. Every message on the messages endpoint carries a provenance.type of content_unavailable with a reason of not_captured and an empty content array. Session metadata still returns normally, so the audit trail shows which sessions happened.

Anthropic · 2026-08-11 · major

Compliance API pulls local sessions — admins can read Claude Code transcripts

Anthropic's Compliance API now returns transcripts of Cowork and Claude Code sessions run on a user's own machine. Three beta endpoints let Claude Enterprise admins list sessions, read one session's metadata, and fetch its messages.

Claude Platform documentation cover card for retrieving chats, files, projects, and sessions

Claude Enterprise admins can now pull transcripts of Cowork and Claude Code sessions that ran on a user's own laptop.

Quick facts

Maker	Anthropic
Availability	Claude Enterprise organizations, beta
Endpoints	3, under /v1/compliance/apps/sessions/local
Scope required	read:compliance_user_data
Covers	Cowork and Claude Code on the user's machine
Retention	6 years, or the org's custom period
Rate limit	600 req/min per parent organization

What is it?

Three new Compliance API endpoints return local sessions — the Cowork and Claude Code conversations that happen on a user's own machine rather than in Anthropic's cloud. Admins can list sessions across the organization, retrieve one session's metadata, and read its full message history. All three are in beta.

How does it work?

Capture happens server-side: Anthropic records each conversation as its requests reach the Claude API, so nothing is installed on the device and nothing is collected beyond what the client already sends. The endpoints sit under /v1/compliance/apps/sessions/local and reuse the existing Compliance Access Key and the read:compliance_user_data scope. Local sessions carry a clls_ ID prefix and can be narrowed only by a created_at range.

Why does it matter?

Security, legal and compliance teams get a written record of what staff asked Claude Code to do and what came back — history that used to stay on the laptop. Tool calls and tool results appear in the transcript, so an admin can see which files and commands a session touched through the API. Work that never reached the API stays invisible.

Who is it for?

enterprise security and compliance teams

Frequently asked questions

Which Claude plans include the local session endpoints?: Local session endpoints are limited to Claude Enterprise organizations and are in beta. A standalone Claude Console organization with no parent organization cannot use them; that setup uses Admin API keys and can query the Activity Feed only. Organizations already running the Compliance API need no new key, scope, setting, or client update.
Can an admin delete a local session through the Compliance API?: Deletion through the API is not supported for local sessions, and the same holds for remote sessions. The Compliance API can delete chats, files, and projects on demand, but session transcripts are read-only. Local session content is kept for six years by default, or for a shorter window when an organization sets a finite conversation retention period.
Are all Claude Code sessions captured?: Several Claude Code setups are never captured. Sessions are skipped when Claude Code authenticates with a Claude Console API key or runs through Amazon Bedrock, Google Cloud, or Microsoft Foundry, and Claude Code on the web is not captured either. Organizations with HIPAA readiness enabled record no local session data at all.
How do local sessions differ from remote sessions?: Local sessions run on a user's own machine and cover both Cowork and Claude Code, while remote sessions run in Anthropic-managed cloud environments and cover Cowork only. Local session IDs start with clls_ and filter only by a created_at range; remote IDs start with cse_ and also filter by organization and user.
What comes back for organizations using customer-managed encryption keys?: Organizations on customer-managed encryption keys can still list and retrieve local sessions, but transcript content is not currently returned. Every message on the messages endpoint carries a provenance.type of content_unavailable with a reason of not_captured and an empty content array. Session metadata still returns normally, so the audit trail shows which sessions happened.

Try it

curl -sS -G "https://api.anthropic.com/v1/compliance/apps/sessions/local" -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY"