Run details

aiWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/ai-review-fork-triggers
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

feat(ai-persistence): show run timings on reconstructed messages (#1504) * feat(ai-persistence): list finished run timings in reconstructChat Add an opt-in includeRuns option. The response then has runs: the thread's finished runs with runId, status, startedAt, and finishedAt, read through the existing optional runs.listByThread. Refs #1061 * feat(ai-persistence): stamp run timings on reconstructed messages withPersistence records the run that produced each assistant message on metadata.tanstack.run.id, and the message converters keep that id on the client round trip. reconstructChat with includeRuns adds the finished run's startedAt and finishedAt to it, so a client can show how long each turn took after a reload. Refs #1061 * test(ai-persistence): add opt-in conformance checks for run timings runPersistenceConformance gets a checks option. 'messages.metadata' checks that stores keep message metadata, and 'runs.listByThread.state' checks that listByThread returns current status and finishedAt. Both are off by default, so existing adapters keep passing. The memory and sandbox snapshot stores opt in. Refs #1061 * docs(persistence): make the includeRuns snippet a complete handler kiira rejected the top-level return. Wrap it in a GET handler with imports. Refs #1061

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

Succeeded

4 CPU cores

fbde89e31380

3%

Cache hits

2 of 70 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

70 groups of tasks optimized.

© 2026 - Nx Cloud

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

aiWorkspace