fix: require ACP metadata for deleted-agent bypass by shakkernerd · Pull Request #91763 · openclaw/openclaw

shakkernerd · 2026-06-09T20:24:55Z

Summary:

Tightens the deleted-agent guard for ACP-shaped session keys. ACP key shape alone is no longer treated as proof that a session is an ACP runtime session.
Preserves the existing fast path for configured agents. If the agent still exists in config, the guard returns before doing ACP metadata or SQLite work.
Keeps configured acp:binding:* sessions owner-scoped, so a deleted configured owner is still rejected instead of being exempted by ACP metadata.
Updates sessions.resolve, chat.send, sessions.send, and sessions.steer so deleted-agent validation sees the loaded session entry, not just the session key string.
Uses persisted ACP metadata to distinguish real ACP runtime sessions from ACP-shaped bridge sessions under missing agents.
Repairs legacy/case-canonicalized ACP metadata rows when a JSON session key has already moved to the canonical key but the ACP metadata row is still stored under the old key.
Bounds the metadata repair lookup: exact candidate keys are tried first, then normalized/lowercase lookup, with a case-insensitive SQLite fallback only for rare partial-migration states.

Why:

ACP bridge sessions can use agent:<id>:acp:... key shapes without persisted SessionAcpMeta.
Treating that shape as sufficient would let sessions under deleted configured agents bypass the deleted-agent guard incorrectly.
The fix makes the bypass depend on the runtime metadata that proves the session is actually ACP-owned.

Verification:

Rebased on latest origin/main.
Auto-review: clean, no accepted/actionable findings.
Crabbox AWS cbx_a603919bef5b, run run_15e01e46ecf9:
- Focused ACP/gateway tests passed: 18 files, 524 tests.
- pnpm check:changed passed.

clawsweeper · 2026-06-09T20:27:45Z

Codex review: needs maintainer review before merge. Reviewed June 9, 2026, 4:34 PM ET / 20:34 UTC.

Summary
The PR tightens Gateway deleted-agent validation so ACP-shaped session keys bypass only with loaded or persisted ACP metadata, threads session entries through resolve/send paths, and adds SQLite ACP metadata rekey repair coverage.

PR surface: Source +163, Tests +279. Total +442 across 9 files.

Reproducibility: yes. from source: current main returns null for non-binding ACP-shaped keys before checking agent existence, while existing command code says ACP key shape alone is not ownership proof. I did not execute tests because this review is read-only.

Review metrics: 2 noteworthy metrics.

Deleted-agent validation entry points: 4 updated. sessions.resolve, chat.send, sessions.send, and sessions.steer now pass loaded session evidence into the same guard.
Runtime ACP metadata repair: 1 added. The new SQLite rekey path changes persisted session metadata during lookup, which matters for upgrade safety.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🌊 off-meta tidepool
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

[P2] Confirm maintainer acceptance of runtime ACP metadata rekeying versus a doctor-only migration before merge.

Risk before merge

[P1] Merging intentionally changes existing behavior by rejecting ACP-shaped bridge sessions under deleted configured agents that current main allowed by key shape alone.
[P1] The guard can rekey persisted ACP SQLite metadata during runtime lookup, so maintainers should explicitly accept that upgrade/session-state repair path instead of a doctor-only migration.

Maintainer options:

Accept guarded hardening (recommended)
Treat the stricter deleted-agent rejection and bounded ACP metadata repair as the intended upgrade behavior because the patch aligns Gateway with existing metadata-based ACP classification.
Move repair out of the guard
If runtime state mutation during lookup is not acceptable, keep the metadata-gated deleted-agent decision but move ACP metadata rekeying into an explicit migration or doctor repair path.
Pause for compatibility policy
If existing ACP-shaped bridge sessions under deleted agents must remain reachable, pause this PR for a product decision on a separate compatibility mode.

Next step before merge

[P2] Protected maintainer-labeled PR with compatibility and session-state merge risk should stay in maintainer review rather than be auto-closed or routed to repair.

Security
Cleared: No dependency, CI, secret, permission, or supply-chain surface is broadened; the patch narrows a deleted-agent guard bypass while using existing SQLite state helpers.

Review details

Best possible solution:

Land after maintainer acceptance that metadata-gated ACP ownership and runtime metadata rekeying are the intended upgrade path; otherwise keep the metadata-gated guard and move rekeying to an explicit migration path.

Do we have a high-confidence way to reproduce the issue?

Yes, from source: current main returns null for non-binding ACP-shaped keys before checking agent existence, while existing command code says ACP key shape alone is not ownership proof. I did not execute tests because this review is read-only.

Is this the best way to solve the issue?

Yes for the guard logic: using loaded entry or persisted SessionAcpMeta is the narrowest fix and matches existing ACP runtime classification. The only solution-fit choice left is whether the metadata rekey belongs in this runtime path or an explicit migration path.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against a4e02cd1dd48.

Label changes

Label changes:

add P2: This is a normal-priority gateway/session bugfix with limited blast radius but meaningful deleted-agent guard impact.
add merge-risk: 🚨 compatibility: The PR deliberately changes existing ACP-shaped bridge sessions under deleted agents from allowed to rejected.
add merge-risk: 🚨 session-state: The PR adds runtime SQLite ACP metadata rekeying that can change persisted session-state rows during lookup.
add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The contributor proof gate is not applied to this maintainer/member PR; the PR body still records Crabbox validation for the touched behavior.

Label justifications:

P2: This is a normal-priority gateway/session bugfix with limited blast radius but meaningful deleted-agent guard impact.
merge-risk: 🚨 compatibility: The PR deliberately changes existing ACP-shaped bridge sessions under deleted agents from allowed to rejected.
merge-risk: 🚨 session-state: The PR adds runtime SQLite ACP metadata rekeying that can change persisted session-state rows during lookup.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The contributor proof gate is not applied to this maintainer/member PR; the PR body still records Crabbox validation for the touched behavior.

Evidence reviewed

PR surface:

Source +163, Tests +279. Total +442 across 9 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	5	183	20	+163
Tests	4	287	8	+279
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	9	470	28	+442

What I checked:

Current main behavior: Current main returns null for any non-binding ACP-shaped session key before checking whether the owning agent still exists, so ACP-shaped bridge keys can bypass the deleted-agent guard by shape alone. (src/gateway/session-utils.ts:929, 52154eda0dd1)
PR guard behavior: The PR moves the configured-agent fast path before ACP handling and only exempts non-binding ACP keys when loaded entry ACP data or persisted SessionAcpMeta is found. (src/gateway/session-utils.ts:983, 8765f5a545d8)
Gateway callers pass loaded entry evidence: The PR updates sessions.resolve, chat.send, sessions.send, and sessions.steer to pass the loaded session entry and legacy metadata key into the deleted-agent guard. (src/gateway/server-methods/chat.ts:3083, 8765f5a545d8)
Metadata repair implementation: The new repair helper only rekeys ACP metadata rows that case-normalize to the target key and whose stored session_id still matches the loaded session entry. (src/acp/runtime/session-meta.ts:254, 8765f5a545d8)
Regression coverage: Added tests cover confirmed ACP runtime sessions, ACP-shaped bridge sessions without metadata, migrated/case-canonicalized ACP metadata, and key/sessionId/label resolve paths. (src/gateway/sessions-resolve-store.test.ts:352, 8765f5a545d8)
Existing invariant: Current command/runtime code already documents that ACP key shape alone is not sufficient because ACP bridge sessions can use ACP-shaped keys without SessionAcpMeta. (src/commands/sessions.ts:55, a4e02cd1dd48)

Likely related people:

scotthuang: git blame and log show the ACP harness bypass and configured ACP binding preservation in the current deleted-agent guard history. (role: introduced current ACP guard behavior; confidence: high; commits: 696c1ecd2068, 52154eda0dd1, 3853eb15af5e; files: src/gateway/session-utils.ts, src/gateway/session-utils.test.ts, src/gateway/sessions-resolve-store.test.ts)
vincentkoc: git blame shows the core deleted-agent guard skeleton and ACP metadata read helpers came through the recent session/gateway import history. (role: adjacent session and ACP metadata owner; confidence: medium; commits: 25160515e05e; files: src/gateway/session-utils.ts, src/acp/runtime/session-meta.ts)
shakkernerd: Current-main history includes prior ACP metadata test/helper work in the same runtime metadata files, beyond this PR branch. (role: recent adjacent ACP metadata contributor; confidence: medium; commits: 24da2c39f3b5; files: src/acp/runtime/session-meta.ts, src/acp/runtime/session-meta.test.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

…26.6.6) (#1040) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040

openclaw-barnacle Bot added app: web-ui App: web-ui gateway Gateway runtime size: M maintainer Maintainer-authored PR labels Jun 9, 2026

shakkernerd added 14 commits June 9, 2026 22:01

fix: require ACP metadata for deleted-agent bypass

a709dc9

fix: read canonical ACP metadata for deleted-agent guard

1d0b79f

fix: align session resolve deleted-agent entry type

26eefd5

fix: preserve ACP metadata key during deleted-agent checks

b4c9e8d

fix: rekey ACP metadata during session key migration

4059b81

fix: validate migrated ACP metadata at canonical key

a7bd1fe

fix: make ACP metadata key repair idempotent

cc2293f

fix: repair ACP metadata in deleted-agent guard

9929aac

test: require ACP metadata in resolve unit fixture

7dda025

fix: skip ACP metadata probe for configured agents

a679122

test: use valid configured ACP bridge fixture

55dbe93

test: use valid deleted ACP bridge fixture

3a3a92f

perf: bound ACP metadata key repair lookup

a237a8c

chore: fix ACP guard lint issues

b8ac76c

shakkernerd force-pushed the fix/acp-bridge-deleted-agent branch from 8765f5a to b8ac76c Compare June 9, 2026 21:06

shakkernerd merged commit 4648701 into main Jun 9, 2026
157 checks passed

shakkernerd deleted the fix/acp-bridge-deleted-agent branch June 9, 2026 21:07

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix: require ACP metadata for deleted-agent bypass#91763

fix: require ACP metadata for deleted-agent bypass#91763
shakkernerd merged 14 commits into
mainfrom
fix/acp-bridge-deleted-agent

shakkernerd commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

shakkernerd commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading