Back to all releases

v1.27.0

Platform

// September 17, 2026

Claude Code and Codex tokens and cost reappear on usage, cost, and identity pages

Usage exported to the native OTLP ingest endpoint now reaches every usage surface, not just the event feed. Devices that switched to that endpoint had been showing tool calls with zero tokens and zero cost; those sessions are attributed to users and counted on the usage, cost, and identity pages again. Two dashboard surfaces also stop misreporting: a tool usage timeline whose buckets are all empty says so instead of drawing a labelled blank chart, and the log detail sheet no longer holds the previous record on screen while the next one is highlighted, which could show one call's arguments under another call's heading.

Features

  • Native OTLP exports counted on every usage surface #6525 - Exports accepted on /otel/v1/logs and /otel/v1/metrics now run the hooks telemetry writers, so Claude Code and Codex usage sent to the native ingest endpoint is attributed to users and counted on the usage, cost, tokens under management, and identity pages. Those exports previously reached only the event feed, leaving affected devices with tool calls but no tokens and no cost. (Author: @daviddanialy)
  • Pick the exact issuer and client for trusted identity provider login #6505 - Organization administrators can configure which remote session issuer and client pair backs trusted identity provider login. The API validates tenant scope, required upstream scopes, and token endpoint authentication, audits effective link changes, and stops a linked client from being invalidated or deleted. (Author: @bflad)

Bug fixes

  • Empty timelines and log payloads tell the truth #6532 - A tool usage timeline whose every bucket is empty shows the no-data state rather than a labelled but blank chart, and the log detail sheet stops holding the previous record's payload on screen while the next one is highlighted. (Author: @adaam2)
  • Caller cancellations no longer read as enforcement degradation #6531 - An enforcement lane failure caused by the caller canceling is not counted as degradation. Deadline and other lane failures still degrade. (Author: @vishalg0wda)
Sagar Batchu
Sagar Batchu
View on GitHub