chore(deps-dev): bump openclaw from 2026.3.24 to 2026.6.11

[dependabot]

Bumps openclaw from 2026.3.24 to 2026.6.11.

Release notes

Sourced from openclaw's releases.

openclaw 2026.6.11

We heard the feedback. v2026.6.11 focuses on the rough edges that make OpenClaw feel less dependable, with fixes for misplaced replies, stuck sends, reconnects, model setup failures, and safer admin defaults.

Full release notes

Highlights

Channel delivery reliability

Delivery and reconnect fixes span Telegram, WhatsApp, Matrix, Google Chat, iMessage, Feishu, Mattermost, WebChat, the Control UI, and the terminal UI.

• Fixes newer Google Chat direct messages sometimes being treated like group conversations, so they reach the correct one-to-one chat while Space and group-chat messages keep their existing routing. #58993 Thanks @​starhappysh, @​vincentkoc.
• Feishu voice replies from OpenClaw now show their duration in the chat bubble, so recipients can see how long the audio is before playing it. #89172 Related #53798. Thanks @​areslp, @​fxz26284407, @​kinrocw.
• Discord and Telegram replies and mirrored chat history stay tied to the intended conversation more consistently, including across repeated Telegram replies and session changes. #89911 Thanks @​jalehman.
• Background image, video, and music results now return to the chat that requested them when the task starts without a full conversation target, instead of appearing to fail after creation or being sent to the wrong peer as the session moves. #89949 Related #86034. Thanks @​tianxiaochannel-oss88, @​wangwllu.
• Telegram answers now stay attached to the user's current question when they quote an earlier bot message, while quotes of other people's messages still reply to the selected quote. #90475 Thanks @​moeedahmed.
• QQBot group admins can choose how broadly slash commands are available, and private-only commands now direct users to a private chat instead of being exposed or silently ignored in groups. #92154 Thanks @​sliverp.
• Heartbeat checks using reasoning-capable models now show the assistant's intended reply instead of exposing internal reasoning in Telegram, WhatsApp, and other channels, while opt-in Thinking messages still work. #92356 Related #92260. Thanks @​jmpei, @​tangtaizong666, @​vincentkoc.
• Telegram progress-mode chats now clear an old progress bubble before newer tool output or artifacts appear, keeping the conversation in a clean, readable order. #93002 Related #90753. Thanks @​shadow-enthusiast, @​zhangguiping-xydt.
• iMessage command-and-link messages now stay together as one OpenClaw turn when delayed link previews arrive, while unrelated quick messages remain separate for users who enabled same-sender DM coalescing. #93143 Thanks @​omarshahine.
• Successful Discord replies sent through the message tool no longer trigger a misleading failure warning in affected message_tool_only source-channel turns. #94072 Related #93875. Thanks @​chenyangjun-xy, @​hoyanhan, @​vincentkoc.
• WhatsApp group conversations now preserve the right message and group context more reliably during retries, reconnects, and group changes. #94338 Related #7433. Thanks @​mcaxtr, @​octopuslabs-fl, @​xialonglee.
• Fixes OpenClaw sometimes replying to its own delayed iMessage echoes when stray leading characters keep the sent message from being recognized. #94442 Thanks @​ly-wang19.
• Telegram webhook users can keep receiving DMs and group messages through brief channel restarts, configuration reloads, and recovery cycles without temporary message blackouts. #94506 Related #90254. Thanks @​obviyus, @​travellingsoldier85, @​xialonglee.
• Matrix E2EE gateways can stay online during long-running use instead of gradually consuming memory until a crash takes channels and in-flight work down. #94942 Related #90455. Thanks @​xzh-icenter, @​yar-sh.
• Telegram users now see the intended native reaction instead of leaked instructions or a dropped reaction-only reply, with success recorded only after Telegram accepts it. #94977 Related #71140. Thanks @​cuttingwater, @​hugenshen.
• Telegram progress updates for commands, searches, updates, and API activity now stay readable instead of exposing noisy HTML or code-style rows, with plain-text fallback when Telegram cannot parse the formatting. #95007 Related #95002.
• Telegram conversations continued in WebChat now show one assistant reply per turn and keep later replies with the active conversation instead of duplicating answers or sending them back to Telegram. #95069 Related #94930. Thanks @​heichaowo.
• Google Chat now hides misleading internal failure banners when a tool result is harmless, leaving users with the completed answer while normal assistant text remains unchanged. #95084 Related #90684. Thanks @​jailbirt, @​studentzhou-svg.
• Bound multi-agent channel conversations now load the workspace files for the configured agent instead of the default agent, though previously misfiled conversations may start fresh in the corrected agent store. #95118 Related #92903. Thanks @​849261680, @​axjing.
• People sharing an OpenClaw gateway can now assign different models to individual direct-message contacts across supported chat channels, while existing group and wildcard model choices keep working as before. #95120 Related #53638. Thanks @​gandalf-at-lerian, @​thomaszta, @​xydigit-zt.
• Telegram now shows that OpenClaw is still working during short initial previews or progress-mode replies instead of leaving the chat silent until the final message arrives. #95183 Related #95004. Thanks @​obviyus.
• Matrix users and operators now get a clear failure when a homeserver sends an oversized or stalled response, instead of OpenClaw continuing to buffer it and risking unbounded memory use. #95240 Thanks @​alix-007.
• Fixes delayed or missing Telegram and other queued channel replies in Kubernetes-style deployments with many injected environment variables, where opening the queue database could stall the gateway. #95278 Related #94571. Thanks @​kaka-srp.
• Telegram chats recover after one stuck message times out, allowing later messages in the same chat or topic to reach the agent without restarting the gateway. #95299 Related #95248. Thanks @​kriegerbangerz-ship-it, @​mikasa0818, @​obviyus.
• When people switch between Telegram and another OpenClaw client in a shared direct conversation, short Telegram replies now follow the latest conversation instead of responding to an older, unrelated Telegram proposal. #95390 Related #95378. Thanks @​maiduy708, @​mikasa0818, @​obviyus.
• Fixes completed assistant messages appearing twice in Telegram, Discord, Slack, and other streamed chats after a multi-message reply. #95432 Thanks @​vincentkoc, @​yetval.
• WhatsApp replies now stay attached to the direct or group message being answered instead of appearing as a separate message that loses the conversation context. #95483 Thanks @​mcaxtr.
• Telegram rich-message replies now keep paragraphs, bullets, and status lines separated instead of collapsing multi-line content into one run-on block, with no configuration change required. #95532 Related #95409. Thanks @​amknight.
• Mattermost operators who enable native slash commands can now use /oc_queue directly in Mattermost to tune active-run queuing, including its mode, debounce timing, cap, and drop handling. #95546 Thanks @​amknight.
• Previously allowed messages keep reaching named accounts after legacy multi-account channel upgrades, with inherited DM and group access rules preserved across Mattermost, Discord, Slack, Telegram, Signal, WhatsApp, iMessage, and IRC. #95550 Thanks @​amknight.
• Mattermost users can keep talking in a thread without mentioning the bot again after it replies, and that participation survives gateway restarts until the thread has been idle for seven days. #95552 Thanks @​amknight.
• Inbound Telegram messages now reach the configured OpenClaw session promptly instead of sitting unanswered until the next polling interval, a gateway restart, or manual intervention. #95577 Related #86957. Thanks @​freidrich-goldenflow, @​liuwqgit.
• QQBot users now receive complete markdown tables when valid separators use one or two dashes per column, instead of losing the header and all but the final row. #95637 Thanks @​ly-wang19.
• Synology Chat users can now receive agent replies that take more than 120 seconds when the configured core timeout allows it, instead of having the channel reject them early. #95707 Thanks @​sahibzada-allahyar, @​vincentkoc.
• Telegram forum-topic cron jobs now keep separately configured failure alerts going to their intended destination, even when the main announcement uses a topic in the same chat. #95794 Thanks @​vincentkoc.
• Fixes WhatsApp group replies that could quote an older OpenClaw message instead of the user's triggering message, so final answers stay attached to the intended message when a reply target is available and avoid pointing back to stale bot context when it is not. #95914 Thanks @​mcaxtr.
• WhatsApp users can approve or deny prompts by reaction without the prompt staying stuck when WhatsApp identifies the same direct chat differently, while group approvals remain tied to the correct group and person. #95935 Thanks @​mcaxtr.
• Final reply processing now uses less CPU when OpenClaw checks whether block text was already sent, without changing which reply reaches the chat or how duplicate text is suppressed. #96087 Thanks @​vincentkoc.
• Exec approval results from external channel plugins now return to the channel or DM where the command started instead of falling back to WebChat or seeming to disappear after approval. #96140 Related #96103. Thanks @​lansenger-pm, @​vincentkoc, @​yetval.

... (truncated)

Commits

• e085fa1 ci(release): stabilize anthropic live smoke selection
• cf64cf7 test(qa): make memory channel scenario wait for final answer
• 848c4e6 test(qa): accept crabline multi-channel capabilities
• d377c0f fix(release): use workspace host deps in release lockfile
• 9b703d0 test(qa): accept async image fixture coverage
• 5f4fa97 test(codex): harden run-attempt temp cleanup
• 65e4b0a chore(release): prepare 2026.6.11
• 4e8ddf7 ci: bump ClawHub package publish workflow (#97909)
• 9c154ff ci(release): restore plugin npm token env
• 866fc34 ci(release): restore trusted plugin npm publishing
• Additional commits viewable in compare view

Install script changes

This version adds preinstall, postinstall scripts and modifies prepare script that run during installation. Review the package contents before updating.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	openclaw@​2026.3.24 ⏵ 2026.6.11	-25	+76		+1	+31

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm openclaw is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/openclaw@2026.6.11 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/openclaw@2026.6.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm typebox is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/openclaw@2026.6.11 → npm/typebox@1.1.39 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typebox@1.1.39. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[evaos-code-review-bot]

evaOS review status: completed

PR: #53 - chore(deps-dev): bump openclaw from 2026.3.24 to 2026.6.11
Head: 1c1b86f16f8feaf852ac58d445d104e50829b614
Updated: 2026-07-02T19:55:41.163Z

evaOS review completed for this PR head.

Automation note: agents should wait for this comment to reach completed, stale_head, closed_or_merged_before_review, skipped, or failed before treating evaOS review as settled for this head. provider_deferred means evaOS still intends to retry.

PR URL: #53

Review URL: #53 (review)

[evaos-code-review-bot]

Walkthrough

PR: #53 - chore(deps-dev): bump openclaw from 2026.3.24 to 2026.6.11
Head: 1c1b86f16f8feaf852ac58d445d104e50829b614 into main. Review event: COMMENT.

Estimated review effort: 5/5 (~52 min)

Changed Files

File	Status	Churn	Purpose	Risk
package-lock.json	modified	+1249/-4747	Configuration	Elevated: large change

Review Signal

No validated inline findings.
Dropped findings before posting: 0. High-severity findings: 0.

Risk Taxonomy

No finding categories.

Validation and Proof

1 required validation/proof recommendation(s) selected from changed files.

• required: TypeScript/web build or CI proof - Runtime TypeScript/web files or package/config files changed. Proof: npm run build; typecheck; focused Vitest; green GitHub check.
  Proof status: missing - 1 required validation/proof recommendation(s) missing from PR metadata.
  Profile validation hints: Call out tool permission widening, prompt injection, and stale context risks.
  Profile proof expectations: Look for focused plugin contract or tool-call evidence.

Related Context

Related issues/PRs: #58993, #89172, #53798, #89911, #89949, #86034, #90475, #92154.
Suggested labels: none.
Suggested reviewers: none from current metadata.

Pre-merge checklist

• Inline comments target current RIGHT-side diff lines.
• No secret-like content survived into posted inline comments.
• REQUEST_CHANGES is only used when eligible P0/P1 findings survive validation.
• Required behavior proof is present or not applicable.
• Labels and reviewers are suggestions only; the bot did not auto-apply them.