Repository navigation
fix(chat): keep the exchange open while paused at a debug breakpoint [JAR-10180] - #174
Merged
Merged
Conversation
Under `uipath debug` the chat runtime sits inside the debug runtime, so it sees each UiPathBreakpointResult first. A breakpoint result is SUSPENDED with no triggers, which fell through to the completion branch and sent endExchange to CAS. In step mode that closed the turn at the first pause, before the agent had replied, so the reply never showed in the chat. Pass breakpoint results up to the debugger without ending the exchange. JAR-10180 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
There was a problem hiding this comment.
🟢 Approval recommended
The focused fix has regression coverage for pausing, resuming, and normal completion, with no blocking issues identified.
No open issues 🎉
What changed in this PR
Keeps chat exchanges open while conversational agents pause at debug breakpoints, allowing replies to arrive before the exchange ends.
Changes:
- Passes breakpoint results through without ending the exchange.
- Adds regression coverage for pause/resume behavior and completion ordering.
- Bumps the package version to
0.13.6.
| File | Description |
|---|---|
uv.lock |
Updates the locked package version. |
tests/test_chat.py |
Tests breakpoint handling and single exchange completion. |
src/uipath/runtime/chat/runtime.py |
Preserves the open exchange at breakpoints. |
pyproject.toml |
Bumps the package version to 0.13.6. |
Review effort: Balanced
JoshParkSJ
changed the title
cristipufu
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes JAR-10180.
When stepping through a conversational agent in the debugger, the agent runs but its reply never appears in chat. The chat runtime treats a breakpoint as the end of the conversation turn and sends
endExchangebefore the agent has finished replying.This change keeps the exchange open while the agent is paused. The chat runtime passes the breakpoint to the debugger, and the exchange ends after the agent finishes replying. It also bumps the package version to
0.13.6.Testing
Added regression tests for pausing at a breakpoint and resuming through the debugger. They check that a pause leaves the exchange open and that resuming sends the reply before a single
endExchangeevent. Both tests fail without the fix. An existing test also checks that a normal run ends the exchange exactly once.The full test suite,
ruff, andmypypass.Also tested locally against alpha with a low-code conversational agent, a real LLM call, and
uipath debugin step mode. WithCAS_WEBSOCKET_DISABLED=true, the chat bridge logged fourendExchangeevents before the fix, starting at the first pause. After the fix, it logged one, after the reply.Validation in CAS and Studio Web chat is still pending. The cloud job uses the published package, so that check requires a release.