Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.228 Home All releases ←olderv2.1.227 v2.1.229newer→
Claude Code v2.1.228

Gateway gains a second admission path for machine identities

Not switched on
Useful3 Signal5
Gateway Notable not in their notes

The self-hosted gateway can admit machine identities that skip managed-settings policy entirely, off by default.

A second admission path via the cri block is complete, including discovery and audit tagging, with cri.enabled false.

cri.enabled
What

The self-hosted gateway can accept callers that present an external identity token rather than a user sign-in, configured by a new cri block with enabled, audience, issuer and org_allowlist. It is off by default (cri.enabled false). When on, discovery advertises cri_enabled: true, audit and inference records are tagged with upstream_kind, and these callers skip managed-settings policy matching entirely.

Details
  • Minted principals carry the claims sub, cri: true, org and act.
  • The group and email-domain policy matcher returns no policy at all for an identity marked cri === true, so managed settings do not apply to these callers.
  • A loopback jwks_url exists for tests only and has two distinct refusal messages.
  • Entirely new in this build.
Evidence

cri_enabled

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.228 →