Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The October 8 addition covers unified chats: cloud continuation stays in one record, including tool calls and corresponding results.
- Activity Feed records events, not chat content. Access to it does not authorize message export.
- A Primary Owner enables it for Enterprise. Export requires read:compliance_user_data on a Compliance Access Key, not deletion permission.
- Unified-chat cloud continuation does not cover every cloud session. Standalone Claude Code cloud and cloud routines remain excluded.
Which part of the chat is newly included?
Anthropic's October 8, 2026 release notes say Compliance API chat endpoints now return unified Claude chats as Enterprise beta. Current help excludes Public Sector. No organization-specific activation instant, separate price, or beta-specific regional scope is given; this is not universal free access.
When a unified chat continues in the cloud, its record remains in the same chat. Tool calls include names and inputs; corresponding call identifiers connect results. Auditors can follow progression in one record rather than separate cloud continuation from the starting conversation.
Why does an Admin Key still return 403 for content?
An Admin API Key accesses only Activity Feed in this interface: events describing who did what and when, without user prompts or model answers. Content endpoints such as chats or files return 403 with that key. A chat-creation event does not provide message access. Older Admin Keys created before activation may also lack feed permission; check official guidance.
Use a Compliance Access Key created in claude.ai with read:compliance_user_data for content export. Ordinary model API and Analytics API Keys cannot substitute. Check key type, scopes, and target organization instead of repeatedly retrying a permission denial as a network fault.
Who activates it, and how much permission does export need?
The Enterprise Primary Owner enables Compliance API on the API page in claude.ai organization settings, with the parent setting covering associated organizations. Matching Owner roles then create keys: the Primary Owner can select parent or individual-organization scope, while an Organization Owner can create a key only for their own organization.
Chat- and file-reading programs need read:compliance_user_data. delete:compliance_user_data is separate and should not be added incidentally when integrating export. Store keys in team secret management, not article examples, source code, or forwarding configuration.
How do you export incrementally rather than download only a list?
Chat listings contain metadata; retrieve messages separately by chat ID. Organization-level synchronization can sort by updated_at and retain pagination cursors to follow new and updated chats. Deleted chats can appear as tombstones. A complete list is not a complete message export, and a rename alone is not guaranteed to appear in this incremental order.
For specified users, current documentation requires created_at sorting. Do not combine user_ids filtering with updated_at. Select organization-wide incremental synchronization or a member-specific query, then use its pagination rather than inventing a universal request.
Hypothetical example: an employee begins research in a unified chat and cloud tools continue retrieval. The exporter locates that chat, fetches messages, and connects tool inputs and results to the original conversation. This is conceptual, not an account test, and the record alone does not prove external-system actions succeeded.
Does cloud continuation include Claude Code cloud?
Distinguish session types. Unified-chat cloud continuation is newly included in chat endpoints, but the current FAQ still excludes standalone Claude Code cloud and cloud-executed Claude Code routines from session endpoints. Running in the cloud does not make them part of the addition.
Local application sessions such as Claude Code also require Enterprise account login. Sessions authenticated through Claude Console API keys or third-party cloud platforms are outside this capture scope. Inventory actual entry points and authentication methods before matching chat or session documentation.
Does export mean history stays complete forever?
Chats, files, and projects remain subject to organizational retention and user deletion. A deleted chat may retain a tombstone without message content; beyond retention or after compliance hard deletion, it is not retrievable. Record export time and missing-content reasons instead of treating an empty body as proof no conversation existed.
Compliance hard deletion is immediate and irreversible. Deleting a unified chat also deletes cloud sessions it started, but not further sessions those sessions started. Design export and deletion governance separately. This article explains scope without deletion execution examples.
Sources
- Claude Platform release notes: Unified-chat compliance beta, 2026-10-08
- Anthropic: Compliance API overview and key types
- Anthropic: Reading and deleting chats, files, and projects
- Anthropic: Enabling Compliance API and creating access keys
- Anthropic: Compliance FAQ and session coverage
- Claude Help Center: Enterprise eligibility and roles
Frequently Asked Questions
Must an existing Compliance Access Key be recreated for unified chats?
Not solely for this beta. Anthropic says existing keys can be reused; verify organization scope and read permission. Scopes cannot be edited after creation, so create a replacement through the documented process only when permissions need changing.
If the API page is missing, must I change plan or network?
Check Primary Owner activation, your key-creation role, and parent-organization association. Help explicitly says Admins cannot see the page. Ask the organization owner or Anthropic support about uncertain eligibility rather than inferring a plan change.
Are exported attachments exact original uploads?
Not necessarily. Content documentation says retrieval returns Claude's processed stored content; images may be adjusted and documents converted to text. Attachment export is not automatically a complete backup of original binaries.