Langfuse 4.64 Extends Agent Gateway and Key Boundaries

What changed

Langfuse 4.64.0, published 19 October 2026, extends the boundary work covered in the earlier 4.63 note. The release makes project API-key permissions enabled by default, presents the Admin role as full access in the key UI, and adds page-based pagination for gateway API keys. It also makes legacy API deprecation notices visible to code agents rather than leaving them only in operator-facing surfaces.

On the AI Gateway path, 4.64 adds admission by memory budget and records more trace/session context around topic summary rows. On the telemetry and data paths, it hides soft-deleted rows from event reads, refuses project keys whose path names another project, drops non-numeric cost details on the direct events path, and preserves explicit user IDs during OpenTelemetry identity resolution. The release also limits active batch exports to one per user and project and disables blob exports automatically when the S3 bucket is in another region.

These are separate changes, not one universal security mode. The release notes establish the intended checks and defaults; they do not establish that every existing deployment has migrated configuration or that all failure paths emit the same telemetry.

What I verified

I fetched the official v4.64.0 release metadata and the v4.63.0...v4.64.0 comparison. The release is dated 19 October 2026 and links the pull requests for project-key permissions, gateway-key pagination, code-agent deprecation notices, memory-budget admission, soft-delete filtering, path validation, OTEL cost handling, identity preservation, and S3-region handling. The release page also records the v4.64.0 comparison target.

I did not run Langfuse, its AI Gateway, or an OpenTelemetry collector locally. These are source- and release-note-level observations, not end-to-end execution results.

Why it matters

Agent infrastructure needs controls that are both enforced at the boundary and legible to the software consuming them. Default key permissions, path validation, budget-based admission, and code-agent-visible deprecations reduce ambiguity between configuration, authorization, and capacity failures. The practical follow-up is to exercise key creation and path validation, memory-budget rejection, soft-deleted event reads, direct OTEL cost fields, and cross-region export behavior in the deployment before treating the upgrade as behaviorally neutral.