This commit is contained in:
parent
e67870caa5
commit
c0d65c8c2f
1 changed files with 6 additions and 0 deletions
|
|
@ -3,6 +3,12 @@
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
## [v0.51.653] — 2026-06-25 — Release XI (gateway approval failures stay actionable instead of dead-ending)
|
||||
|
||||
### Fixed
|
||||
|
||||
- **In gateway-backed sessions, an approval card no longer disappears when the backend can't relay your approve/deny click.** Previously the WebUI cleared the approval card as soon as you clicked, before knowing whether the backend actually relayed the response to the gateway run — so if the relay failed, the card vanished and the run was left blocked with no way to respond. Now `/api/approval/respond` returns an explicit relay-failure error and preserves the pending state, and the card stays visible and actionable (with the error surfaced) until the backend confirms acceptance. Re-renders and Enter no longer re-enable or duplicate-submit an in-flight approval. Thanks @rodboev. (#4917, closes #4771)
|
||||
|
||||
## [v0.51.652] — 2026-06-25 — Release XH (background subagent results return to chat)
|
||||
|
||||
### Fixed
|
||||
|
|
|
|||
Loading…
Reference in a new issue