mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-19 23:05:21 +00:00
* fix(cli): fail agent wait when the daemon resolved no agent The daemon answers wait_for_finish with status "error" both when it could not resolve the identifier to an agent (final: null) and when the agent it did resolve finished in error (final: the agent payload). runWaitCommand handed both to buildWaitResult, which returns a normal result row, so `paseo agent wait <unknown id>` printed "Agent not found: ..." and exited 0 while every sibling command exits 1 with AGENT_NOT_FOUND (#9736). Throw AGENT_NOT_FOUND when the state is error and the payload is null, and let that command error through the inner catch instead of rewrapping it as WAIT_FAILED. A genuine agent failure still carries its payload, so it keeps printing its result row. The wire schema is unchanged. * test(cli): cover the agent wait not-found mapping without module mocks Move the not-found decision into buildWaitResult, which maps the daemon's wait reply to the command result, and test that function directly with plain reply objects instead of mocking the daemon client module. The e2e test in tests/11-agent-wait.test.ts still covers the command against a real daemon. Co-authored-by: Eapp1e <163811520+Eapp1e@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(cli): keep daemon errors during agent wait reported as WAIT_FAILED Map the wait reply to the result after the wait's try/catch, so the AGENT_NOT_FOUND error leaves without the inner catch passing every coded error through. Connection and RPC errors from waitForFinish are wrapped as WAIT_FAILED again, as on main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Eapp1e <163811520+Eapp1e@users.noreply.github.com> Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>