taTanStackOSS
ta
  • Pipelines
  • Nx runs
Insights
  • Compare tasks
  • Analytics
aiai
  1. Pipelines
  2. fix(ai): keep a router input on the server The plan on SUBAGENT_STARTED carried each router input to the client, and a resume read it back. A client could change an input that server code made, and a schema check does not find a changed value of the same shape. The plan now has the agent names and the order only. A turn whose plan names an agent with inputSchema cannot resume: the resume fails as a stale InterruptResumeValidationError. A routed turn with no such agent resumes as before. See #1740 for signing the state of a suspended run.
    nx run-many --targets=build --exclude=examples/**,testing/**
fix(ai): keep a router input on the server
Succeeded in 2m 23sStarted
Linux4 CPU cores
read-write access token used

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

17227c20289GitHubOpen 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