Claude Enterprise Can Retrieve Local Cowork and Claude Code Sessions

Anthropic’s August 2026 API release notes say the Compliance API beta can return local Cowork and Claude Code sessions and messages for Enterprise organizations. Editorial and research teams should therefore treat local AI work sessions as governed records: define ownership, workspace, project, data class, source permissions, retention, access, export reason, review, and deletion or correction handling.

This is a compliance and governance change, not a Claude Search crawler change. The endpoints require a Compliance Access Key and scoped permission. Anthropic also documented an anthropic-workspace-id response header for identifying the workspace that handled an API request; that identifies a workspace, not the provenance of every claim in an output.

Record the session boundary before the work begins

A minimum governance record for editorial AI sessions

Field	Record	Why
Owner	Person and responsible team	Assigns correction and access duties
Workspace and project	Workspace ID, project label, environment	Separates organizational contexts
Data class	Public, licensed, confidential, personal, restricted	Controls allowed inputs and exports
Sources	Files, URLs, databases, permissions, dates	Preserves evidence and rights
Retention	Policy, trigger, deletion hold	Prevents accidental indefinite storage
Compliance access	Role, key owner, purpose, reviewer	Limits powerful retrieval capability
Publication link	Draft, claim ledger, final URL, corrections	Connects process to accountable output

Separate five kinds of material

Web sources are external documents with their own authorship and freshness. Local files may contain licensed, confidential, or personal material. Prompts and instructions show the task but are not evidence. Generated output is a draft or analysis, not a source. Publication evidence is the verified material that supports the final claim.

Do not collapse these into one transcript label. A compliance export may reveal what was said, but it does not automatically prove that a source was authorized, current, correctly interpreted, or used in the published passage.

Restrict compliance access

1. Use a dedicated Compliance Access Key rather than an ordinary development secret.
2. Grant only the documented scopes required for the review.
3. Store keys in an approved secret manager and never in a transcript or repository.
4. Log who queried which session, when, and for what declared purpose.
5. Require a second reviewer for sensitive exports or investigations.
6. Test deletion, legal hold, and correction procedures before an incident.

Anthropic’s Compliance API documentation is the authority for current access requirements. Beta endpoints, scopes, and response structures can change, so record the documentation state and client version used.

Build an editorial release gate

• Every material factual claim maps to a primary or qualified source.
• Local files have an owner and an allowed-use record.
• Personal or confidential data is removed from publication artifacts.
• Generated quotations, citations, and numbers are opened and verified.
• The final article contains visible dates and limitations.
• The session record links to the claim ledger and correction owner.

The SEA publishing guide already requires a claim ledger and skeptical review. Add the session governance record beside that ledger; do not replace it with a transcript archive.

Handle corrections across both systems

If a source is withdrawn or a published claim is corrected, update the article and its evidence record. Preserve the correction reason and affected sessions according to policy. A deletion request may apply differently to a source file, model transcript, compliance export, and public article; name the system of record for each.

Finally, disclose AI assistance at the level useful to readers. A generic “AI was used” statement does not tell an editor whether local files, web research, or generated drafts were involved. Internal governance can be detailed while public disclosure stays concise and accurate.

Primary documentation

• Anthropic API release notes
• Anthropic: Claude Compliance API