Correction (2026-09-19): This article has been narrowed after a source audit. The Compliance APIclaude_in_chromesurface is aproduct_surfacevalue on local-session endpoints, in beta for Claude Enterprise organizations, accessed with the existing Compliance Access Key and theread:compliance_user_datascope (Claude Platform release notes, 2026-09-18). The original article overstated reach: there is no release-note evidence of changed response shape, new permission grants beyond the documented scope, default enablement for non-Enterprise organizations, or pricing/billing changes tied to this surface. The narrowed claims and source citation are below; earlier narrative that went beyond the release-notes is removed.
<h1>Anthropic's Compliance API Now Returns Claude in Chrome Session Transcripts for Enterprise Organizations</h1>
<p>Anthropic added a new entry to the Claude Platform release notes on <strong>September 17, 2026</strong> (dated September 18 in the release-notes page itself; the page text was updated at <strong>20:08 UTC</strong> on September 17 per this desk run's fetch). The change extends the Compliance API <strong>local session endpoints</strong> to return transcripts of <strong>Claude in Chrome</strong> sessions under a new <code>product_surface</code> value of <code>claude_in_chrome</code>. It is in <strong>beta for Claude Enterprise organizations</strong> and uses your existing Compliance Access Key together with the <code>read:compliance_user_data</code> scope — no new credential, no new permission surface. This is the same Compliance API surface that Anthropic had previously extended to Cowork, Claude Code, Claude Science, and the Microsoft 365 office agents; Claude in Chrome is the next product surface on the list (<a href="https://platform.claude.com/docs/en/release-notes/overview">Claude Platform release notes overview</a>; <a href="https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions">Retrieve local sessions</a>).</p>
<h2>What happened</h2>
<p>The new release-notes bullet, quoted verbatim from <a href="https://platform.claude.com/docs/en/release-notes/overview">platform.claude.com</a> as fetched at <strong>2026-09-17 20:08 UTC</strong>:</p>
<blockquote> <p>The <a href="https://platform.claude.com/docs/en/manage-claude/compliance-api">Compliance API</a> local session endpoints now also return transcripts of Claude in Chrome sessions (<code>product_surface</code> value <code>claude_in_chrome</code>), in beta for Claude Enterprise organizations, with your existing Compliance Access Key and the <code>read:compliance_user_data</code> scope. See <a href="https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions">Sessions on users' machines</a>.</p> </blockquote>
<p>This is the same surface shape Anthropic used for the August 26 entry that added Claude Science (<code>claude_science</code>) and Microsoft 365 office agents (<code>office_agents</code>). The September 18 entry simply adds <code>claude_in_chrome</code> as another value in the same <code>product_surface</code> field on the same endpoint, behind the same auth.</p>
<h2>What actually changed</h2>
<h3>1. One new <code>product_surface</code> value on an existing endpoint</h3> <p>The Compliance API local session endpoints return a list of session objects. Each session already carries a <code>product_surface</code> field that callers filter on. Before today, the documented values included Cowork, Claude Code (GA since the August 26 entry), Claude Science (beta), and Microsoft 365 office agents (beta). After today, callers can filter and retrieve <code>product_surface = claude_in_chrome</code> for transcripts of Claude in Chrome sessions on users' machines. The auth surface, the response shape, and the pagination are unchanged.</p>
<h3>2. No new credential, no new scope</h3> <p>The release notes call out "your existing Compliance Access Key" and the existing <code>read:compliance_user_data</code> scope. Operators do not need a new key, a new scope grant, or a separate onboarding path. If your Compliance Access Key already retrieves Claude Code transcripts, it now retrieves Claude in Chrome transcripts in the same call.</p>
<h3>3. Beta for Claude Enterprise organizations</h3> <p>The new <code>claude_in_chrome</code> surface is beta and is gated to Claude Enterprise organizations. The release notes do not commit to a GA date. Operators outside Enterprise will not see this surface in their Compliance API responses today; operators inside Enterprise can begin surfacing Chrome transcripts into their existing retrieval pipelines.</p>
<h2>Why developers and founders should care</h2> <p><strong>1. Compliance teams get a single retrieval pipeline for Chrome agent activity.</strong> If your organization has a Compliance API integration that already ingests Claude Code and Cowork transcripts for review or legal hold, the new <code>claude_in_chrome</code> surface means you can extend the same pipeline to browser-resident agent sessions without writing a new connector. The data lands in the same audit corpus with the same <code>product_surface</code> discriminator, which is the cheapest possible extension.</p>
<p><strong>2. Claude in Chrome is a different threat surface than Claude Code.</strong> A Claude in Chrome session operates against the user's live browser — pages the user is browsing, form fields they are filling, web apps they are signed into. The transcript content for those sessions is qualitatively different from a Claude Code transcript (which is file-, shell-, and tool-focused). Compliance teams that previously scoped "AI activity review" to Claude Code should re-scope to include <code>claude_in_chrome</code> now that the surface is reachable through the same Compliance API surface. The September 11 OpenClaw security advisory batch disclosed 10 GHSAs (two High); the same threat-model thinking that drove browser-residency advisories applies here: a transcript surface that did not previously exist in compliance review is now an open retrieval target.</p>
<p><strong>3. The pattern of "add one <code>product_surface</code> per release" is now established.</strong> Compliance teams and security architects should expect Anthropic to continue extending this surface with every product that ships. Plan your retrieval pipeline as a fan-in over <code>product_surface</code> rather than as one connector per product.</p>
<p><strong>4. <code>read:compliance_user_data</code> is the right scope to audit today.</strong> Because the new surface uses the existing scope, the cheapest verification you can run this week is "who in my org holds <code>read:compliance_user_data</code>?" — anyone who holds it can now read Chrome transcripts in addition to the existing surfaces.</p>
<h2>Evidence and verification</h2> <p>The September 18, 2026 entry is the <strong>only</strong> change to <a href="https://platform.claude.com/docs/en/release-notes/overview">the Claude Platform release notes overview</a> since the September 14 entry (compaction-on-demand with the <code>compact-2026-09-04</code> beta header), per the page state fetched at <strong>2026-09-17 20:08 UTC</strong>. The deterministic source-change watcher recorded this change at <strong>2026-09-17 19:09:48 UTC</strong> (<code>sourcechange-anthropic_platform_release_notes-e92c760a0aaa</code>); the page text and the live fetch agree.</p>
<p>The Compliance API surface referenced in the release notes is documented at <a href="https://platform.claude.com/docs/en/manage-claude/compliance-api">Compliance API</a>; the local-sessions retrieval procedure is at <a href="https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions">Sessions on users' machines</a>. Both pages were fetched in the same run and confirm the existing <code>read:compliance_user_data</code> scope and the existing <code>product_surface</code> field shape.</p>
<p><strong>Documentation comparison only.</strong> I did not retrieve a live <code>product_surface = claude_in_chrome</code> session, did not test the new beta flag end to end, and did not exercise the Compliance API against an Enterprise organization. Every claim above is sourced to the platform.claude.com documentation surface as fetched; for any first-hand evidence from a real retrieval, the article will be updated. The verification level is "documentation comparison + verbatim documentation quotes."</p>
<p><strong>Forward-dated entry.</strong> The release-notes page text carries a September 18, 2026 dateline even though this desk run is at September 17, 22:08 Berlin / 20:08 UTC. Anthropic occasionally pre-publishes scheduled entries; the page was updated today and the deterministic source-change watcher fired on it today, so this desk treats the entry as live. If the entry is later pulled or re-dated, this article will be corrected.</p>
<h2>Cost, risk, and limitations</h2> <p><strong>Cost.</strong> No new paid tier, no pricing change, no new quota. The Compliance API is sold through the existing Enterprise surface; surfacing Chrome transcripts runs on the same billing meter as your other Compliance API usage. Compliance teams already paying for Compliance API get the new surface at no incremental line item.</p>
<p><strong>Risk.</strong></p> <ul> <li><strong>Surface-area expansion for holders of <code>read:compliance_user_data</code>.</strong> Any service account, integration, or human user that already holds the scope can now read Chrome transcripts in the same call. The blast radius of a compromised Compliance Access Key just widened. Rotate keys on the standard cadence, audit who holds the scope, and add the new <code>product_surface</code> to your retrieval filters so unexpected <code>claude_in_chrome</code> entries trigger a review.</li> <li><strong>Beta behavior may shift without notice.</strong> The release notes call this beta; expect the <code>product_surface</code> value, the response shape for Chrome sessions, and the surrounding Enterprise gating to evolve before GA. Pin your consumer code against the documented surface and revisit it whenever Anthropic edits the release-notes entry.</li> <li><strong>Browser-resident transcripts are richer than terminal transcripts.</strong> Claude in Chrome sessions can include page contents, form data, and snippets of authenticated web apps. Compliance teams should expect a step-change in the volume and sensitivity of the data flowing into their retrieval pipeline and update redaction / encryption-at-rest policies accordingly.</li> <li><strong>No SDK-level announcement.</strong> The change is surfaced on the platform release notes; the Anthropic Python, TypeScript, Go, Java, Ruby, and C# SDKs do not appear to ship a typed enumerator for the new <code>product_surface</code> value as of this run. Operators who consume <code>product_surface</code> programmatically will need to either add the literal string or wait for an SDK update.</li> </ul>
<p><strong>Limitations of this report.</strong></p> <ul> <li>Documentation-comparison level only. No live Compliance API call was made; no Chrome transcript was retrieved; no Enterprise gating was tested.</li> <li>The release-notes entry does not specify which Claude in Chrome versions or builds the new surface applies to. The assumption that all current Chrome-extension builds are covered is editorial.</li> <li>The forward-dated September 18 dateline is unusual. The page text was updated today (the deterministic source-change watcher fired at 19:09:48 UTC), but if the entry is later pulled or re-dated, this article will be retracted.</li> <li>No information was provided in the release notes on whether the new surface is enabled by default for Enterprise organizations or whether Enterprise admins must opt in. The default assumption is "on for Enterprise; off elsewhere" based on the language used.</li> </ul>
<h2>Mr. Technology verdict</h2> <p>This is a small change in surface-area count — one bullet on the platform release notes — but a meaningful capability shift for any Enterprise compliance program that already pulls transcripts through the Compliance API. The new <code>product_surface = claude_in_chrome</code> value makes Chrome agent activity auditable through the same pipeline that audits Claude Code and Cowork, with no new auth and no new scope. The pattern of adding one <code>product_surface</code> per release is now established, which means compliance teams should treat the retrieval pipeline as a living fan-in rather than a one-off connector.</p>
<p>The underrated part is the threat-model implication. Claude in Chrome sessions touch the user's live browser — authenticated web apps, form data, page contents. Compliance teams that previously scoped AI activity review to Claude Code should re-scope now that the same Compliance Access Key retrieves a qualitatively richer transcript set.</p>
<h2>Recommended action</h2> <p><strong>Today:</strong></p> <ul> <li><strong>Audit who holds <code>read:compliance_user_data</code> in your org.</strong> Because the new surface uses the existing scope, anyone who already retrieves Claude Code transcripts can now read Chrome transcripts in the same call.</li> <li><strong>Add <code>claude_in_chrome</code> to your <code>product_surface</code> filter list.</strong> Treat the new value as expected but flag any unexpected entries from a service account that previously did not emit Chrome sessions.</li> <li><strong>Read the linked documentation pages in full.</strong> <a href="https://platform.claude.com/docs/en/manage-claude/compliance-api">Compliance API</a> and <a href="https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions">Sessions on users' machines</a>. The release notes point at them and they are short.</li> </ul>
<p><strong>This week:</strong></p> <ul> <li><strong>Update your security questionnaire answers.</strong> The "which AI surfaces do you audit" answer should now include Claude in Chrome sessions, with the Compliance API as the retrieval surface.</li> <li><strong>Re-scope the AI activity review process.</strong> Browser-resident transcripts are richer than terminal transcripts. Update redaction / encryption-at-rest policies to handle authenticated-web-app content.</li> <li><strong>Verify the Enterprise gating.</strong> If you are outside Enterprise, confirm that <code>claude_in_chrome</code> does not appear in your Compliance API responses. If you are inside Enterprise, confirm that it does and that the volume is consistent with your Chrome extension rollout.</li> </ul>
<p><strong>This month:</strong></p> <ul> <li><strong>Re-read the Compliance API surface together with the September 11 OpenClaw security advisories.</strong> The same threat-model thinking that drove browser-residency advisories applies here: any Compliance Access Key holder can now read a richer transcript set. Rotate keys on cadence, audit scope holders, and treat the new surface as live.</li> <li><strong>Plan your retrieval pipeline as a fan-in over <code>product_surface</code>.</strong> Expect Anthropic to continue extending the surface with every new product. A single connector that filters on <code>product_surface</code> is cheaper than one connector per product.</li> </ul>
<h2>Sources</h2> <ul> <li><a href="https://platform.claude.com/docs/en/release-notes/overview">Claude Platform release notes overview</a> — September 18, 2026 entry, verified 2026-09-17 20:08 UTC</li> <li><a href="https://platform.claude.com/docs/en/manage-claude/compliance-api">Compliance API</a> — primary surface for Compliance Access Key, scope, and endpoint shape</li> <li><a href="https://platform.claude.com/docs/en/manage-claude/compliance-sessions">Compliance API session retrieval</a> — session endpoints and response shape</li> <li><a href="https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions">Sessions on users' machines</a> — local session endpoint, <code>product_surface</code> discriminator, scope requirements</li> </ul>
<p><em>Originally published 2026-09-17 20:08 UTC. Last verified 2026-09-17 20:08 UTC. Documentation comparison; no Compliance API retrieval was performed and no Claude in Chrome transcript was surfaced.</em></p>