Run details

aiWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/bedrock-converse-cache-usage
- Runs and Agents
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

fix(ai-bedrock): forward Converse cache token counts to TokenUsage The Converse stream processor and the two structuredOutput paths copied only inputTokens, outputTokens and totalTokens out of metadata.usage. Bedrock reports cacheReadInputTokens and cacheWriteInputTokens beside them, and inputTokens counts only the uncached remainder, so a cached request looked like a near-zero-input call and the cache write and read costs had no field. buildConverseUsage() in converse/usage.ts now maps both counts to promptTokensDetails.cachedTokens / cacheWriteTokens, the same builder shape as ai-anthropic and openai-base, and omits the details object when Bedrock omits the counters. Docs say where the counts appear. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

nx run-many --targets=build --exclude=examples/**,testing/**

Succeeded

4 CPU cores

read access token used

4e5adbb91300

98%

Cache hits

62 of 63 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

63 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

aiWorkspace