Run details

aiWorkspace

CI Pipeline Executions
- Current executionSucceeded
  compaction
- Runs and Agents
- Configuration
- Self-Healing CI
- Project Graph
- Resource Usage
- Analysis
- Conformance
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

feat(ai-persistence): stamp stable ids on persisted messages The chat engine ids assistant messages but leaves incoming user messages, engine-created tool messages, and compaction-injected messages without one. `withPersistence` now fills in an id for any message that lacks one, in place, before each `saveThread`. The same message keeps its id across a run's saves and, when the server owns the thread, across the next turn's reload. This lets a row-keyed persistence adapter reconcile by id (SELECT id, version then delete/insert/update) instead of rewriting the whole transcript. Order and version (content hash) stay the adapter's to own; see the new "Storing messages per row" section in the store reference. - ensureMessageIds() at all four save points (start, streaming snapshot, interrupt boundary, finish) plus the pending-turn seam. - Tests: every persisted message has an id, and earlier ids stay stable across a continuation turn. - Existing verbatim-transcript assertions relaxed to tolerate the added id. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

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

Succeeded

4 CPU cores

read-write access token used

a183deaf1235

77%

Cache hits

47 of 61 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

61 groups of tasks optimized.

© 2026 - Nx Cloud

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