taTanStackOSS
ta
  • Pipelines
  • Nx runs
Insights
  • Compare tasks
  • Analytics
aiai
  1. Pipelines
  2. fix(ai-client): coalesce the per-chunk snapshot storm while streaming A large tool-call stream re-rendered every useChat hook once per chunk. A Code Mode program arrives as thousands of TOOL_CALL_ARGS deltas in one burst, so the client published each delta to the snapshot atom synchronously and the tab locked up (the SSE read runs on the same thread and could abort). Message publishes made while the client processes a chunk now coalesce to about one per animation frame (setTimeout fallback off-DOM). Discrete changes (setMessages, clear, reload, status) stay synchronous, and getSnapshot() flushes any pending streamed messages so it is never stale. In development, the devtools bridge's per-event snapshot emit is likewise coalesced to one per microtask. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    nx run-many --targets=build --exclude=examples/**,testing/**
fix(ai-client): coalesce the per-chunk snapshot storm while streaming

Succeeded in 4s

Started
Linux4 CPU cores
read-write access token used

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

1956ebc12c9GitHubOpen on GitHub
TasksResource Usage
Resource usage reports are turned off for this workspace
Your organization has the Resource usage add-on, but this workspace does not collect metrics for non distributed runs. Turn it back on in workspace settings.

© 2026 Nx Cloud

  • Terms
  • Privacy
  • Changelog
  • Status
  • Docs
  • Contact
  • Pricing
  • Company
  • @NxDevTools
taTanStackOSS