Jordan Ritter 01466e5629 fix: handle RunErrorEvent in proxy agent, state manager, angular agent, and node name hook ...

When the backend emits RunErrorEvent via the AG-UI protocol, several
components did not handle it:

- ProxiedCopilotRuntimeAgent: isRunning stayed true, causing
  data-copilot-running to never transition to false (infinite spinner)
- StateManager: activeRun entries were never cleaned up, runFinished
  flag never set (stale state on subsequent runs)
- Angular CopilotKitAgent: same isRunning bug as the proxy agent
- useAgentNodeName: node name stuck at last step instead of "end"

onRunErrorEvent is distinct from onRunFailed — the former handles
protocol-level RUN_ERROR events from the backend, the latter handles
local exceptions (network errors, deserialization failures).

2026-04-10 10:25:35 -07:00

..

lib

fix: handle RunErrorEvent in proxy agent, state manager, angular agent, and node name hook

2026-04-10 10:25:35 -07:00

styles

chore: migrate from eslint+prettier to oxlint+oxfmt

2026-04-02 16:39:05 +02:00

index.ts

refactor: consolidate V1/V2 packages into flat @copilotkit/* structure

2026-03-28 16:45:10 -07:00

public-api.ts

refactor: consolidate V1/V2 packages into flat @copilotkit/* structure

2026-03-28 16:45:10 -07:00

test-setup.ts

refactor: consolidate V1/V2 packages into flat @copilotkit/* structure

2026-03-28 16:45:10 -07:00