fix(mattermost): keep default replies in existing threads by jacobtomlinson · Pull Request #91684 · openclaw/openclaw

jacobtomlinson · 2026-06-09T10:59:40Z

Summary

Fix a Mattermost regression from fix(mattermost): honor replyToMode off for threaded messages #52543 / aaba1ae653f where the default replyToMode: "off" discarded an existing Mattermost root_id.
Preserve existing channel/group thread roots so replies to messages inside a Mattermost thread stay in that thread.
Keep top-level messages top-level when replyToMode: "off" and keep DMs non-threaded.

Regression Context

#52543 fixed a real replyToMode: "off" failure, but it overcorrected by suppressing existing thread roots too. The latest docs say the default off behavior should not start new threads, but should still reply in a thread when the inbound post is already in one.

Reporter proof: on the latest OpenClaw release, starting a Mattermost thread and sending a message inside it causes the agent reply to land at the top level in the channel.

Latest stable checked: v2026.6.1 published 2026-06-03. In that tag, resolveMattermostEffectiveReplyToId still drops threadRootId when replyToMode is off, while docs/channels/mattermost.md documents the opposite default behavior.

Real behavior proof

Behavior addressed: Mattermost replies to messages sent inside an existing channel/group thread escape to the channel root under the default replyToMode: "off".

Real environment tested: Reporter manually reproduced on the latest OpenClaw release with a real Mattermost channel thread.

Exact steps or command run after this patch: node scripts/run-vitest.mjs extensions/mattermost/src/mattermost/monitor.test.ts

Evidence after fix: Focused tests now assert existing channel/group thread roots are preserved when replyToMode is off, while top-level off messages still do not start new threads and DMs remain non-threaded.

Observed result after fix: resolveMattermostEffectiveReplyToId and resolveMattermostThreadSessionContext keep the existing Mattermost thread root for threaded channel/group follow-ups.

What was not tested: Live Mattermost after the patch.

Verification

node scripts/run-vitest.mjs extensions/mattermost/src/mattermost/monitor.test.ts
pnpm exec oxfmt --check extensions/mattermost/src/mattermost/monitor.ts extensions/mattermost/src/mattermost/monitor.test.ts
git diff --check
.agents/skills/autoreview/scripts/autoreview --mode local --prompt 'Review the Mattermost regression fix...' - clean, no accepted/actionable findings

clawsweeper · 2026-06-09T11:01:50Z

Codex review: needs maintainer review before merge. Reviewed June 9, 2026, 12:06 PM ET / 16:06 UTC.

Summary
The PR changes Mattermost reply target resolution and regression tests so existing channel/group thread roots are preserved under default replyToMode: "off" while top-level messages and DMs stay unthreaded.

PR surface: Source 0, Tests +25. Total +25 across 2 files.

Reproducibility: yes. at source level: on current main, a channel/group call with replyToMode: "off" and a non-empty threadRootId returns undefined, which sends the reply to the channel root instead of the existing Mattermost thread. I did not run a live Mattermost instance in this read-only review.

Review metrics: none identified.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🦞 diamond lobster
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

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

Next step before merge

The PR has a protected maintainer label and no repairable review finding; a maintainer should handle merge approval after normal checks.

Security
Cleared: The diff only changes Mattermost reply-target logic and colocated tests; it does not touch secrets, dependencies, workflows, package resolution, or code-execution surfaces.

Review details

Best possible solution:

Land the focused Mattermost helper/test change after maintainer handling so documented default behavior preserves existing channel/group threads without starting new threads for top-level posts or DMs.

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

Yes, at source level: on current main, a channel/group call with replyToMode: "off" and a non-empty threadRootId returns undefined, which sends the reply to the channel root instead of the existing Mattermost thread. I did not run a live Mattermost instance in this read-only review.

Is this the best way to solve the issue?

Yes. The PR fixes the single shared Mattermost reply/session helper used by the affected runtime paths and keeps the top-level and direct-message exceptions covered by tests; adding a new config option or patching only send delivery would be broader and less consistent with the docs.

AGENTS.md: found and applied where relevant.

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

Label changes

Label changes:

add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
remove rating: 🐚 platinum hermit: Current PR rating is rating: 🦞 diamond lobster, so this older rating label is no longer current.

Label justifications:

P1: This fixes a shipped Mattermost regression that can route real channel/thread replies to the wrong visible location under the default configuration.
rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR body has the required proof fields and a follow-up comment reports PR-branch validation against a local Docker Mattermost instance with threaded replies staying in-thread and top-level messages staying top-level.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body has the required proof fields and a follow-up comment reports PR-branch validation against a local Docker Mattermost instance with threaded replies staying in-thread and top-level messages staying top-level.

Evidence reviewed

PR surface:

Source 0, Tests +25. Total +25 across 2 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	1	1	1	0
Tests	1	27	2	+25
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	2	28	3	+25

What I checked:

Repository policy read: Root AGENTS.md was present and read fully; the scoped extensions/AGENTS.md was also read for the touched bundled-plugin path, and its plugin-boundary guidance was applied. (AGENTS.md:1, 86bab9699d0d)
Current main drops existing thread roots: resolveMattermostEffectiveReplyToId currently returns an existing threadRootId only when replyToMode is not off, so the default path flattens already-threaded Mattermost channel/group replies. (extensions/mattermost/src/mattermost/monitor.ts:444, 86bab9699d0d)
Docs define the opposite default behavior: The Mattermost docs state that off is the default and should only reply in a thread when the inbound post is already in one, matching the PR's intended behavior. Public docs: docs/channels/mattermost.md. (docs/channels/mattermost.md:161, 86bab9699d0d)
Shared helper feeds the affected runtime paths: Inbound posts, interactions, and model-picker callbacks resolve their session and reply target through resolveMattermostThreadSessionContext, so fixing the helper updates the relevant Mattermost delivery/session path consistently. (extensions/mattermost/src/mattermost/monitor.ts:1424, 86bab9699d0d)
Latest release still has the bug: The latest release tag v2026.6.1 still has the same threadRootId && params.replyToMode !== "off" guard while the release docs still describe preserving existing threads, so this is not already fixed in a shipped release. (extensions/mattermost/src/mattermost/monitor.ts:443, 2e08f0f4221f)
Regression provenance: The related merged Mattermost PR at fix(mattermost): honor replyToMode off for threaded messages #52543 changed the helper from always preserving threadRootId to suppressing it when replyToMode is off; that explains the current regression shape. (extensions/mattermost/src/mattermost/monitor.ts:175, aaba1ae653f3)

Likely related people:

teconomix: The Mattermost replyToMode feature and docs were introduced in commit 171d2df9e0, and later Mattermost thread-context work also lists this contributor in the commit history. (role: introduced behavior and adjacent owner; confidence: high; commits: 171d2df9e0fe, 0c926a2c5e82; files: extensions/mattermost/src/mattermost/monitor.ts, extensions/mattermost/src/mattermost/accounts.ts, docs/channels/mattermost.md)
RichardCao: The linked merged Mattermost PR that added the current replyToMode !== "off" suppression is attributed to this author in the provided GitHub context. (role: related regression-change author; confidence: high; commits: aaba1ae653f3; files: extensions/mattermost/src/mattermost/monitor.ts, extensions/mattermost/src/mattermost/monitor.test.ts)
mukhtharcm: Recent Mattermost threading and reply-delivery commits list this handle as reviewer or co-author, including the original replyToMode feature and related delivery-context fixes. (role: reviewer and adjacent contributor; confidence: medium; commits: 171d2df9e0fe, 0c926a2c5e82, 39fbfd9b2854; files: extensions/mattermost/src/mattermost/monitor.ts, extensions/mattermost/src/mattermost/accounts.ts)
Vincent Koc: Recent Mattermost maintenance and the latest release/baseline commits touch the same channel area, making this a likely routing candidate for current maintainer review. (role: recent area contributor; confidence: medium; commits: a7ac3c666c4e, fad06f7c2126, 2e08f0f4221f; files: extensions/mattermost/src/mattermost/monitor.ts, extensions/mattermost/src/mattermost/monitor.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.

jacobtomlinson · 2026-06-09T11:40:09Z

Manual Mattermost validation completed by @jacobtomlinson on the PR branch.

Tested against the local Docker Mattermost instance with the @test bot and the default replyToMode: "off" behavior. Threaded channel replies stayed inside the existing Mattermost thread, while top-level channel messages stayed top-level.

No unexpected Mattermost reply-target behavior was observed after the fix.

jacobtomlinson · 2026-06-09T12:08:01Z

@clawsweeper re-review

clawsweeper · 2026-06-09T12:08:03Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27207032810
Updated: 2026-06-09T12:53:25.280Z

jacobtomlinson · 2026-06-09T12:44:42Z

@clawsweeper re-review

clawsweeper · 2026-06-09T12:44:45Z

🦞👀
ClawSweeper picked this up.

Command router queued. I will update this comment with the next step.

jacobtomlinson · 2026-06-09T16:08:42Z

Land-ready proof for 94d377fc2a41b804046b40b95715d14b592d15e9:

Local focused test: node scripts/run-vitest.mjs extensions/mattermost/src/mattermost/monitor.test.ts passed, 58 tests.
Local format/proof: pnpm exec oxfmt --check extensions/mattermost/src/mattermost/monitor.ts extensions/mattermost/src/mattermost/monitor.test.ts passed; git diff --check upstream/main...HEAD passed.
Local pre-merge review: .agents/skills/autoreview/scripts/autoreview --mode branch --base upstream/main ... returned clean with no accepted/actionable findings.
Manual behavior proof: tested against local Docker Mattermost with the @test bot; default replyToMode: "off" kept replies inside existing Mattermost threads and kept top-level channel messages top-level. Proof note: fix(mattermost): keep default replies in existing threads #91684 (comment)
ClawSweeper re-review: proof sufficient / ready for maintainer look; run https://github.com/openclaw/clawsweeper/actions/runs/27207032810.
GitHub CI on the refreshed SHA: clean, no pending checks and no failed checks. Main CI run: https://github.com/openclaw/openclaw/actions/runs/27218800458.

Known proof gaps: none for this scoped Mattermost reply-target regression.

…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 channel: mattermost Channel integration: mattermost size: XS maintainer Maintainer-authored PR labels Jun 9, 2026

clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Jun 9, 2026

fix(mattermost): keep default replies in existing threads

94d377f

jacobtomlinson force-pushed the fix/mattermost-thread-replies-default-off branch from 0fb0dd1 to 94d377f Compare June 9, 2026 15:57

clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels Jun 9, 2026

jacobtomlinson merged commit 8c3ba33 into openclaw:main Jun 9, 2026
162 of 164 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(mattermost): keep default replies in existing threads#91684

fix(mattermost): keep default replies in existing threads#91684
jacobtomlinson merged 1 commit into
openclaw:mainfrom
jacobtomlinson:fix/mattermost-thread-replies-default-off

jacobtomlinson commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

Uh oh!

jacobtomlinson commented Jun 9, 2026 •

edited

Loading

Uh oh!

jacobtomlinson commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

Uh oh!

jacobtomlinson commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026

Uh oh!

jacobtomlinson commented Jun 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

jacobtomlinson commented Jun 9, 2026

Summary

Regression Context

Real behavior proof

Verification

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!

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

Uh oh!

Uh oh!

jacobtomlinson 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!

jacobtomlinson commented Jun 9, 2026

Uh oh!

clawsweeper Bot commented Jun 9, 2026

Uh oh!

jacobtomlinson commented Jun 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading

jacobtomlinson commented Jun 9, 2026 •

edited

Loading

clawsweeper Bot commented Jun 9, 2026 •

edited

Loading