Overview - Ai

aiWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

ai

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

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

aiWorkspace

Average execution time

6m 17s

903 CI pipeline executions

Computation time saved

13d 3h

Cache hit rate

55%

Time to Green

16m 26s

Was 19m 31s, improved by 16%

Succeeded
feat/truncated-tool-result
d6b938f4 fix(ai): warn instead of running a client tool of a cut answer, and expect finishReason in the persistence E2E Move the length guard into handlePendingToolCalls so the processor still warns 'Did not run tool call'. The sandbox persistence E2E now expects metadata.tanstack.finishReason on the saved assistant message.
by Alem Tuzlak
Succeeded
feat/truncated-tool-result
d6b938f4 Merge dd65fa4efeeaa4e2924444139be39331e395dea5 into 5bd27f2fc94ebfb6d11bfb28d46d5d858310805e
by Alem Tuzlak
Succeeded
feat/truncated-tool-result
af67bf5d feat(ai): never run the cut tool calls of an answer at the output limit, add chat({ truncatedToolResult }) - Assistant messages keep metadata.tanstack.finishReason. - A tool call of an answer that stopped at the output limit (finish reason length) never runs and asks for nothing. A stored cut call gets an error tool result, and a history call of a length message is skipped. The client processor runs no client tool after a length finish. - chat({ truncatedToolResult }) gives each cut call that text and calls the model again. Split out of #1555.
by Alem Tuzlak
Failed
feat/truncated-tool-result
af67bf5d Merge 362d2dc437080d93a22aaa1374b383972ced9ff8 into 5bd27f2fc94ebfb6d11bfb28d46d5d858310805e
by Alem Tuzlak