docs(changelog): add [Unreleased] entry for #4771 local-approval 409 fix
AGENTS.md requires a CHANGELOG entry for user-visible behavior changes, and this is one (local-backend command approvals went from 409-on-every-click to working). The PR shipped the routes.py gate fix without a changelog note; this adds the [Unreleased] -> Fixed entry crediting b3nw / claw-io (#4948). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
bac8108b38
commit
bc12bb43c9
1 file changed
+4
@@ -3,6 +3,10 @@
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Command approvals work again on the default local backend (#4771 regression).** On the in-process WebUI chat runtime, clicking Approve/Deny on a guarded-command card failed with `Gateway approval could not be relayed because the active run is unavailable` (HTTP 409, `gateway_run_unavailable`) on every click — a regression from #4771 (v0.51.653), which surfaced that 409 for gateway approvals whose run had gone but emitted it regardless of backend. Local approvals have no gateway run by design, so the check always tripped. The 409 is now gated on the WebUI actually running the gateway chat backend; local approvals resolve in-process as before, and the gateway behavior is unchanged. Reported by b3nw and claw-io (#4948).
|
||||
|
||||
## [v0.51.665] — 2026-06-25 — Release XU (sidebar stops re-querying every poll during streaming)
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in new issue
Block a user