fix(slack): improve interactive reply parity by vincentkoc · Pull Request #53389 · openclaw/openclaw

vincentkoc · 2026-03-24T04:51:48Z

Summary

Problem: Slack interactive replies had multiple parity gaps. Direct agent --deliver replies dropped Slack directive compilation, the Slack plugin runtime did not expose sendPayload, duplicate Block Kit action_ids caused invalid_blocks, and Slack setup/capability guidance made interactive replies too easy to miss.
Why it matters: Slack buttons/selects were unreliable for debugging and testing, and agents often fell back to plain text where other channels already had richer affordances.
What changed: restored Slack interactive delivery end-to-end, added unique Slack action ids, compiled simple trailing Options: ... lines into Slack buttons/selects, resolved interactive capability via the default Slack account, and added a setup-wizard prompt/quickstart default for interactive replies.
What did NOT change (scope boundary): no new Slack modal authoring surface, no new raw Block Kit authoring DSL beyond the existing blocks path, and no broad cross-channel UI refactor.

AI-assisted: yes. Testing: targeted + build/check locally; broad pnpm test deferred to PR CI at operator request.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Closes #
Related #
This PR fixes a bug or regression

Root Cause / Regression History (if applicable)

Root cause: Slack interactive replies were split across multiple seams and only some reply paths used the Slack-aware normalization/outbound adapters. Direct agent delivery normalized text without Slack interactive compilation, the Slack plugin runtime never surfaced sendPayload, and Block Kit rendering reused duplicate action_ids.
Missing detection / guardrail: no regression test covered direct agent --deliver Slack interactive payloads end-to-end, and no contract test enforced unique Slack action ids in rendered blocks.
Prior context (git blame, prior PR, issue, or refactor if known): Unknown; this appears to be accumulated drift between generic reply normalization, Slack outbound plumbing, and Slack interaction rendering.
Why this regressed now: richer Slack parity work existed in pieces, but the direct delivery path and plugin outbound path were not aligned, so the feature looked configured without actually being end-to-end reliable.
If unknown, what was ruled out: Slack app tokens/scopes/config were ruled out by live send probes; the failures reproduced in local code paths before the API boundary.

Regression Test Plan (if applicable)

Coverage level that should have caught this:
- Unit test
- Seam / integration test
- End-to-end test
- Existing coverage already sufficient
Target test or file: src/agents/command/delivery.test.ts, src/auto-reply/reply/reply-utils.test.ts, extensions/slack/src/channel.test.ts, extensions/slack/src/shared-interactive.test.ts, extensions/slack/src/monitor/events/interactions.test.ts, extensions/slack/src/setup-surface.test.ts
Scenario the test should lock in: direct Slack deliveries preserve interactive payloads, rendered Block Kit action ids stay unique, simple Options: replies compile into Slack controls, setup enables interactive replies intentionally, and default-account capability resolution keeps Slack interactive guidance available.
Why this is the smallest reliable guardrail: the bug crossed normalization, outbound adapter, render, and setup seams; these tests pin each seam without requiring live Slack in CI.
Existing test that already covers this (if any): prior Slack shared interactive and interaction tests covered parts of the render/ingress path only.
If no new test is added, why not: N/A

User-visible / Behavior Changes

Slack buttons/selects now work for direct agent deliveries, not just routed replies.
Simple trailing Options: a, b, c. lines now auto-render as Slack buttons/selects when Slack interactive replies are enabled.
Slack setup now prompts to enable interactive replies, and quickstart defaults enable them automatically.
Slack interactive capability resolution now follows the resolved default account instead of failing closed when multiple accounts exist.
Agent Slack guidance now explicitly prefers buttons/selects for small discrete choices.

Security Impact (required)

New permissions/capabilities? (Yes/No) No
Secrets/tokens handling changed? (Yes/No) No
New/changed network calls? (Yes/No) No
Command/tool execution surface changed? (Yes/No) No
Data access scope changed? (Yes/No) No
If any Yes, explain risk + mitigation:

Repro + Verification

Environment

OS: macOS
Runtime/container: Node 24.13.0 via nodenv
Model/provider: openai-codex/gpt-5.4
Integration/channel (if any): Slack (Socket Mode)
Relevant config (redacted): channels.slack.capabilities.interactiveReplies=true, Slack bot/app tokens configured

Steps

Configure Slack locally and enable Slack interactive replies.
Send a direct agent delivery or agent reply that contains [[slack_buttons: ...]], [[slack_select: ...]], or a simple trailing Options: ... line.
Inspect the delivered Slack message and interact with the buttons/select.

Expected

Slack renders Block Kit buttons/selects.
Buttons/selects carry unique action_ids.
Interaction callbacks route back into OpenClaw.

Actual

Before this change, direct delivery often fell back to plain text, or Slack rejected blocks with invalid_blocks due to duplicate action_ids.

Evidence

Attach at least one:

Failing test/log before + passing after
Trace/log snippets
Screenshot/recording
Perf numbers (if relevant)

Human Verification (required)

Verified scenarios: targeted Slack tests passed; pnpm build passed; pnpm check passed; live Slack DM delivery rendered Block Kit with unique action ids and stored real blocks instead of plain text.
Edge cases checked: direct agent delivery, default-account capability resolution, setup-wizard enable/decline behavior, simple-vs-complex Options: parsing, unique action ids for buttons/selects.
What you did not verify: broad pnpm test completion locally in this final cycle; operator asked to stop the long local run and rely on PR CI for the wide suite.

Review Conversations

I replied to or resolved every bot review conversation I addressed in this PR.
I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

Backward compatible? (Yes/No) Yes
Config/env changes? (Yes/No) No
Migration needed? (Yes/No) No
If yes, exact upgrade steps:

Failure Recovery (if this breaks)

How to disable/revert this change quickly: disable Slack interactive replies with channels.slack.capabilities.interactiveReplies=false (or the per-account equivalent), or revert commit b2b6b88106935d6e1423e11e3ca5f413a387ddc1.
Files/config to restore: Slack reply normalization/outbound files and Slack capability config in channels.slack.
Known bad symptoms reviewers should watch for: Slack messages showing literal Options: lines instead of controls, or Slack API invalid_blocks errors on button/select replies.

Risks and Mitigations

Risk: the new Options: compiler could over-eagerly convert freeform text that happens to end with a simple Options: line.
- Mitigation: conversion is intentionally narrow; it only triggers on a trailing line with 2-12 simple comma-separated tokens and skips complex grammar.
Risk: changing default-account capability resolution could surface interactive guidance in multi-account setups where the old behavior hid it.
- Mitigation: it now follows the repo’s existing resolved default-account behavior instead of guessing across all accounts.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 44a524f351

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

src/agents/command/delivery.ts

greptile-apps · 2026-03-24T16:55:38Z

Greptile Summary

This PR closes several Slack interactive reply parity gaps: it fixes duplicate action_ids in Block Kit rendering (which caused Slack to reject messages with invalid_blocks), surfaces sendPayload on the plugin's outbound adapter so direct agent --deliver flows correctly compile Slack directives and response prefixes, adds auto-compilation of simple trailing Options: a, b, c. lines into Slack buttons/selects, and improves the setup wizard to prompt for interactive-reply enablement.

Changes reviewed:

blocks-render.ts: Unique action_id fix — clean, tests updated accordingly.
interactive-replies.ts: Capability resolution now follows the resolved default account instead of failing closed on multi-account configs; deliberate and documented behavioral change.
channel.ts: New sendPayload bridge on slackPlugin.outbound.base wires resolveSlackSendContext into the standalone outbound adapter.
delivery.ts: normalizeAgentCommandReplyPayloads extracted and wired into the direct delivery path, fixing the normalization gap for agent --deliver.
slack-directives.ts: compileSlackInteractiveReplies and parseSlackOptionsLine are well-guarded; the trailing Options: compiler is intentionally narrow.
setup-core.ts: The finalize step has an inconsistency for array-style capability configs — declining interactive replies removes the string from the array, which looks identical to "never configured" to hasSlackInteractiveRepliesConfig, causing re-prompting on future wizard runs. Object-style caps (the normal modern path) are correct.
Interaction routing in interactions.block-actions.ts: startsWith check handles new namespaced IDs; exact-match cases kept for backward compatibility.
All changed files include targeted tests that lock in the expected behavior at each seam.

Confidence Score: 4/5

Safe to merge with one targeted fix: the array-capabilities branch in setSlackInteractiveReplies should record an explicit decline so finalize does not re-prompt on subsequent wizard runs.
The bulk of the PR is a clean, well-tested bug fix across several seams (duplicate action IDs, missing sendPayload on the plugin outbound, normalization gap in direct delivery). The only concrete issue found is the array-capabilities edge case in the new finalize step, which causes the setup wizard to re-prompt after a declined interactive-replies choice. This is a real UX regression for operators using array-style capabilities, but it doesn't break Slack interactive functionality itself — it only affects the setup flow, and object-style capabilities (the standard path) work correctly.
extensions/slack/src/setup-core.ts — the setSlackInteractiveReplies array branch for the false case.

Comments Outside Diff (1)

extensions/slack/src/setup-core.ts, line 287-302 (link)

Array-style capabilities: declining interactive replies is indistinguishable from "never configured"

setSlackInteractiveReplies(cfg, accountId, false) on an array-style capabilities config removes the "interactiveReplies" string from the array rather than adding a sentinel:

: capabilities.filter((entry) => String(entry).trim().toLowerCase() !== "interactivereplies")

After this, hasSlackInteractiveRepliesConfig calls:

capabilities.some((entry) => String(entry).trim().toLowerCase() === "interactivereplies")
// → false, because the string was removed

finalize then sees hasSlackInteractiveRepliesConfig === false on the next wizard run and prompts the operator again, even though they already explicitly declined. The operator's "no" is silently discarded.

Object-style capabilities don't have this problem because interactiveReplies: false is stored as an object key that "interactiveReplies" in capabilities correctly detects.

To fix this for the array branch, you could push a sentinel like "interactiveReplies:false" when declining, and extend hasSlackInteractiveRepliesConfig to recognise it — or convert array-style caps to object-style before writing the new key (the simpler approach).

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/slack/src/setup-core.ts
Line: 287-302

Comment:
**Array-style capabilities: declining interactive replies is indistinguishable from "never configured"**

`setSlackInteractiveReplies(cfg, accountId, false)` on an array-style capabilities config removes the `"interactiveReplies"` string from the array rather than adding a sentinel:

```ts
: capabilities.filter((entry) => String(entry).trim().toLowerCase() !== "interactivereplies")
```

After this, `hasSlackInteractiveRepliesConfig` calls:

```ts
capabilities.some((entry) => String(entry).trim().toLowerCase() === "interactivereplies")
// → false, because the string was removed
```

`finalize` then sees `hasSlackInteractiveRepliesConfig === false` on the **next** wizard run and prompts the operator again, even though they already explicitly declined. The operator's "no" is silently discarded.

Object-style capabilities don't have this problem because `interactiveReplies: false` is stored as an object key that `"interactiveReplies" in capabilities` correctly detects.

To fix this for the array branch, you could push a sentinel like `"interactiveReplies:false"` when declining, and extend `hasSlackInteractiveRepliesConfig` to recognise it — or convert array-style caps to object-style before writing the new key (the simpler approach).

How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/slack/src/setup-core.ts
Line: 287-302

Comment:
**Array-style capabilities: declining interactive replies is indistinguishable from "never configured"**

`setSlackInteractiveReplies(cfg, accountId, false)` on an array-style capabilities config removes the `"interactiveReplies"` string from the array rather than adding a sentinel:

```ts
: capabilities.filter((entry) => String(entry).trim().toLowerCase() !== "interactivereplies")
```

After this, `hasSlackInteractiveRepliesConfig` calls:

```ts
capabilities.some((entry) => String(entry).trim().toLowerCase() === "interactivereplies")
// → false, because the string was removed
```

`finalize` then sees `hasSlackInteractiveRepliesConfig === false` on the **next** wizard run and prompts the operator again, even though they already explicitly declined. The operator's "no" is silently discarded.

Object-style capabilities don't have this problem because `interactiveReplies: false` is stored as an object key that `"interactiveReplies" in capabilities` correctly detects.

To fix this for the array branch, you could push a sentinel like `"interactiveReplies:false"` when declining, and extend `hasSlackInteractiveRepliesConfig` to recognise it — or convert array-style caps to object-style before writing the new key (the simpler approach).

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/auto-reply/reply/slack-directives.ts
Line: 162-170

Comment:
**Redundant trailing-period strip in `parseSimpleSlackOptions`**

`SLACK_OPTIONS_LINE_RE` already excludes the trailing period from the capture group via `\s*\.?\s*$` at the end of the pattern, so `match[1]` never contains a trailing period. The subsequent `.replace(/\.\s*$/, "")` inside `parseSimpleSlackOptions` is therefore always a no-op.

```ts
// SLACK_OPTIONS_LINE_RE captures `on, full, off` from "Options: on, full, off."
// match[1] === "on, full, off"  (no period)
const entries = raw.replace(/\.\s*$/, "")  // ← no-op; raw already has no period
```

Consider removing the redundant replace to keep the code self-consistent and avoid implying that `raw` might still contain a trailing period.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "docs(changelog): note slack interactive ..." | Re-trigger Greptile}

src/auto-reply/reply/slack-directives.ts

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 38d80f7c22

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

src/agents/command/delivery.ts

aisle-research-bot · 2026-03-24T17:14:04Z

🔒 Aisle Security Analysis

We found 1 potential security issue(s) in this PR:

#	Severity	Title
1	🔵 Low	Ambiguous Slack account selection enables interactive replies when accountId is omitted

Vulnerabilities

1. 🔵 Ambiguous Slack account selection enables interactive replies when accountId is omitted

Property	Value
Severity	Low
CWE	CWE-840
Location	`extensions/slack/src/interactive-replies.ts:23-27`

Description

isSlackInteractiveRepliesEnabled previously failed closed when multiple Slack accounts were configured but no accountId was provided. After the change, it always resolves an account using resolveDefaultSlackAccountId, which can silently pick an arbitrary account (e.g., the first configured account) when channels.slack.defaultAccount is unset or invalid.

Security impact:

Call sites that omit accountId (e.g., capability discovery / tool hints) may now report interactive-replies support even in multi-account deployments where the caller did not intend to enable it.
If the resolved default account is not the intended workspace/bot, this can lead to cross-workspace/account confusion (wrong capability gating and potentially wrong downstream routing decisions in code that relies on the same default resolution pattern).

Vulnerable code (new behavior):

const account = resolveSlackAccount({
  cfg: params.cfg,
  accountId: params.accountId ?? resolveDefaultSlackAccountId(params.cfg),
});

This becomes risky because resolveDefaultSlackAccountId ultimately falls back to a listed account even when multiple are present and no valid defaultAccount is configured (see resolveListedDefaultAccountId, which returns accountIds[0] unless an explicit ambiguity fallback is configured).

Recommendation

Restore fail-closed behavior for ambiguous multi-account configurations, or require an explicit default.

Option A (fail closed when ambiguous and no explicit default):

import { listSlackAccountIds, resolveSlackAccount, resolveDefaultSlackAccountId } from "./accounts.js";

export function isSlackInteractiveRepliesEnabled({ cfg, accountId }: { cfg: OpenClawConfig; accountId?: string | null }): boolean {
  if (accountId) {
    return resolveInteractiveRepliesFromCapabilities(
      resolveSlackAccount({ cfg, accountId }).config.capabilities,
    );
  }

  const ids = listSlackAccountIds(cfg);
  const configuredDefault = cfg.channels?.slack && typeof cfg.channels.slack.defaultAccount === "string"
    ? cfg.channels.slack.defaultAccount
    : undefined;

  if (ids.length > 1 && !configuredDefault) {
    return false; // fail closed unless an explicit default is configured
  }

  const resolvedId = resolveDefaultSlackAccountId(cfg);
  return resolveInteractiveRepliesFromCapabilities(
    resolveSlackAccount({ cfg, accountId: resolvedId }).config.capabilities,
  );
}

Option B: Make resolveDefaultSlackAccountId throw (or return undefined) when multiple accounts exist and no valid defaultAccount is configured, and handle that explicitly.

Also add validation at startup / setup to warn or error when multiple accounts exist without channels.slack.defaultAccount.

Analyzed PR: #53389 at commit 2f1bf68

_{Last updated on: 2026-03-24T17:42:57Z}

* fix(slack): improve interactive reply parity * fix(slack): isolate reply interactions from plugins * docs(changelog): note slack interactive parity fixes * fix(slack): preserve preview text for local agent replies * fix(agent): preserve directive text in local previews

@drobison00

* Formatting fixes and remove trailing dash acceptance * Remove lower casing -- preserving prior behavior * fix: preserve legacy clawhub skill updates (openclaw#53206) (thanks @drobison00) * feat(csp): support inline script hashes in Control UI CSP (openclaw#53307) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]> * refactor: separate exec policy and execution targets * test: print failed test lane output tails * fix(cron): make --tz work with --at for one-shot jobs Previously, `--at` with an offset-less ISO datetime (e.g. `2026-03-23T23:00:00`) was always interpreted as UTC, even when `--tz` was provided. This caused one-shot jobs to fire at the wrong time. Changes: - `parseAt()` now accepts an optional `tz` parameter - When `--tz` is provided with `--at`, offset-less datetimes are interpreted in that IANA timezone using Intl.DateTimeFormat - Datetimes with explicit offsets (e.g. `+01:00`, `Z`) are unaffected - Removed the guard in cron-edit that blocked `--tz` with `--at` - Updated `--at` help text to mention `--tz` support - Added 2 tests verifying timezone resolution and offset preservation * fix: land cron tz one-shot handling and prerelease config warnings (openclaw#53224) (thanks @RolfHegr) * fix: clean changelog merge duplication (openclaw#53224) (thanks @RolfHegr) * test: isolate line jiti runtime smoke * refactor: harden extension runtime-api seams * tests: improve boundary audit coverage and safety (openclaw#53080) * tools: extend seam audit inventory * tools: tighten seam audit heuristics * tools: refine seam test matching * tools: refine seam audit review heuristics * style: format seam audit script * tools: widen seam audit matcher coverage * tools: harden seam audit coverage * tools: tighten boundary audit matchers * tools: ignore mocked import matches in boundary audit * test: include native command reply seams in audit * fix: command auth SecretRef resolution (openclaw#52791) (thanks @Lukavyi) * fix(command-auth): handle unresolved SecretRef in resolveAllowFrom * fix(command-auth): fall back to config allowlists * fix(command-auth): avoid duplicate resolution fallback * fix(command-auth): fail closed on invalid allowlists * fix(command-auth): isolate fallback resolution errors * fix: record command auth SecretRef landing notes (openclaw#52791) (thanks @Lukavyi) --------- Co-authored-by: Ayaan Zaidi <[email protected]> * refactor: extract cron schedule and test runner helpers * fix: populate currentThreadTs in threading tool context fallback for Telegram DM topics (openclaw#52217) When a channel plugin lacks a custom buildToolContext (e.g. Telegram), the fallback path in buildThreadingToolContext did not set currentThreadTs from the inbound MessageThreadId. This caused resolveTelegramAutoThreadId to return undefined, so message tool sends without explicit threadId would route to the main chat instead of the originating DM topic. Fixes openclaw#52217 * fix: unblock runtime-api smoke checks * refactor: split tracked ClawHub update flows * build: prepare 2026.3.23-2 * fix: preserve command auth resolution errors on empty inferred allowlists * docs: refresh plugin-sdk api baseline * test: harden linux runtime smoke guards * fix(runtime): anchor bundled plugin npm staging to active node * tests: cron coverage and NO_REPLY delivery fixes (openclaw#53366) * tools: extend seam audit inventory * tools: audit cron seam coverage gaps * test: add cron seam coverage tests * fix: avoid marking NO_REPLY cron deliveries as delivered * fix: clean up delete-after-run NO_REPLY cron sessions * fix: verify global npm correction installs * build: prepare 2026.3.24 * docs: update mac release automation guidance * fix: fail closed when provider inference drops errored allowlists * fix: reject nonexistent zoned cron at-times * fix: hash inline scripts with data-src attributes * ci: balance shards and reuse pr artifacts * refactor: simplify provider inference and zoned parsing helpers * fix: unify live model auth gating * tests: add boundary coverage for media delivery (openclaw#53361) * tests: add boundary coverage for media delivery * tests: isolate telegram outbound adapter transport * tests: harden telegram webhook certificate assertion * tests: fix guardrail false positives on rebased branch * msteams: extract structured quote/reply context (openclaw#51647) * msteams: extract structured quote/reply context from Teams HTML attachments * msteams: address PR openclaw#51647 review feedback * msteams: add message edit and delete support (openclaw#49925) - Add edit/delete action handlers with toolContext.currentChannelId fallback for in-thread edits/deletes without explicit target - Add editMessageMSTeams/deleteMessageMSTeams to channel runtime - Add updateActivity/deleteActivity to SendContext and MSTeamsTurnContext - Extend content param with text/content/message fallback chain - Update test mocks for new SendContext shape Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]> * fix(doctor): honor --fix in non-interactive mode Ensure repair-mode doctor prompts auto-accept recommended fixes even when running non-interactively, while still requiring --force for aggressive rewrites. This restores the expected behavior for upgrade/doctor flows that rely on 'openclaw doctor --fix --non-interactive' to repair stale gateway service configuration such as entrypoint drift after global updates. Co-authored-by: Copilot <[email protected]> * Preserve no-restart during update doctor fixes Co-authored-by: Copilot <[email protected]> * fix(doctor): skip service config repairs during updates Co-authored-by: Copilot <[email protected]> * fix: add config clobber forensics * fix(ui): resolve model provider from catalog instead of stale session default When the server returns a bare model name (e.g. "deepseek-chat") with a session-level modelProvider (e.g. "zai"), the UI blindly prepends the provider — producing "zai/deepseek-chat" instead of the correct "deepseek/deepseek-chat". This causes "model not allowed" errors when switching between models from different providers. Root cause: resolveModelOverrideValue() and resolveDefaultModelValue() in app-render.helpers.ts, plus the /model slash command handler in slash-command-executor.ts, all call resolveServerChatModelValue() which trusts the session's default provider. The session provider reflects the PREVIOUS model, not the newly selected one. Fix: for bare model names, create a raw ChatModelOverride and resolve through normalizeChatModelOverrideValue() which looks up the correct provider from the model catalog. Falls back to server-provided provider only if the catalog lookup fails. All 3 call sites are fixed. Closes openclaw#53031 Co-Authored-By: Claude Opus 4.6 <[email protected]> Signed-off-by: HCL <[email protected]> * style(ui): polish agent file preview and usage popovers (openclaw#53382) * feat: make workspace links clickable in agent context card and files list Updated the agent context card and files list to render workspace names as clickable links, allowing users to easily access the corresponding workspace files. This enhances usability by providing direct navigation to the workspace location. * style(ui): polish markdown preview dialog * style(ui): reduce markdown preview list indentation * style(ui): update markdown preview dialog width and alignment * fix(ui): open usage filter popovers toward the right * style(ui): adjust positioning of usage filter and export popovers * style(ui): update sidebar footer padding and modify usage header z-index * style(ui): adjust positioning of usage filter popover to the left and export popover to the right * style(ui): simplify workspace link rendering in agent context card * UI: make workspace paths interactive buttons or plain text Agent Context card workspace (Channels/Cron panels): replace non-interactive <div> with a real <button> wired to onSelectPanel('files'), matching the Overview panel pattern. Core Files footer workspace: drop workspace-link class since the user is already on the Files panel — keep as plain text. * fix(agents): suppress heartbeat prompt for cron-triggered embedded runs Prevent cron-triggered embedded runs from inheriting the default heartbeat prompt so non-cron session targets stop reading HEARTBEAT.md and polluting scheduled turns. Made-with: Cursor * test(agents): cover additional heartbeat prompt triggers Document that default-agent heartbeat prompt injection still applies to memory-triggered and triggerless runs while cron remains excluded. Made-with: Cursor * fix: land cron heartbeat prompt suppression (openclaw#53152) (thanks @Protocol-zero-0) * msteams: implement Teams AI agent UX best practices (openclaw#51808) Migrates the Teams extension from @microsoft/agents-hosting to the official Teams SDK (@microsoft/teams.apps + @microsoft/teams.api) and implements Microsoft's AI UX best practices for Teams agents. - AI-generated label on all bot messages (Teams native badge + thumbs up/down) - Streaming responses in 1:1 chats via Teams streaminfo protocol - Welcome card with configurable prompt starters on bot install - Feedback with reflective learning (negative feedback triggers background reflection) - Typing indicators for personal + group chats (disabled for channels) - Informative status updates (progress bar while LLM processes) - JWT validation via Teams SDK createServiceTokenValidator - User-Agent: teams.ts[apps]/<sdk-version> OpenClaw/<version> on outbound requests - Fix copy-pasted image downloads (smba.trafficmanager.net auth allowlist) - Pre-parse auth gate (reject unauthenticated requests before body parsing) - Reflection dispatcher lifecycle fix (prevent leaked dispatchers) - Colon-safe session filenames (Windows compatibility) - Cooldown cache eviction (prevent unbounded memory growth) Closes openclaw#51806 * refactor: tighten embedded prompt and sidecar guards * test: audit subagent seam coverage inventory * test: add exact-stem subagent seam tests * refactor: clarify doctor repair flow * fix(plugins): make Matrix recovery paths tolerate stale plugin config (openclaw#52899) * fix(plugins): address review feedback for Matrix recovery paths (openclaw#52899) 1. Narrow loadConfigForInstall() to catch only INVALID_CONFIG errors, letting real failures (fs permission, OOM) propagate. 2. Assert allow array is properly cleaned in stale-cleanup test. 3. Add comment clarifying version-resolution is already addressed via the shared VERSION constant. 4. Run cleanStaleMatrixPluginConfig() during install so persistPluginInstall() → writeConfigFile() does not fail validation on stale Matrix load paths. * fix(plugins): address review feedback for Matrix recovery paths (openclaw#52899) * fix: fetch model catalog for slash command updates * fix: restore teams sdk adapter contracts * fix: keep slash command model qualification on rebase * fix: clear production dependency advisories * fix: delete subagent runs after announce give-up * refactor: polish trigger and manifest seams * refactor(ui): extract chat model resolution state * fix(feishu): preserve docx block tree order (openclaw#40524) Verified: - pnpm install --frozen-lockfile - pnpm build - pnpm vitest run extensions/feishu/src/docx.test.ts Co-authored-by: Tao Xie <[email protected]> * fix: stabilize matrix and teams ci assertions * fix: preserve subagent ended hooks until runtime init * test: prune low-signal live model sweeps * test: harden parallels smoke harness * fix: preserve direct subagent dispatch failures on abort * fix: report dropped subagent announce queue deliveries * fix: unblock live harness provider discovery * fix: finalize resumed subagent cleanup give-ups * refactor: centralize plugin install config policy * fix: format subagent registry test * fix: finalize deferred subagent expiry cleanup * fix(tui): preserve user message during slow model responses (openclaw#53115) When a local run ends with an empty final event while another run is active, skip history reload to prevent clearing the user's pending message from the chat log. This fixes the 'message disappears' issue with slow models like Ollama. * fix: preserve deferred TUI history sync (openclaw#53130) (thanks @joelnishanth) * test: sync app chat model override expectation * feat(ui): Control UI polish — skills revamp, markdown preview, agent workspace, macOS config tree (openclaw#53411) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]> * fix(security): resolve Aisle findings — skill installer validation, terminal sanitization, URL scheme allowlisting (openclaw#53471) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]> * fix: widen installer regex allowlists and deduplicate safeExternalHref calls - SAFE_GO_MODULE: allow uppercase in module paths (A-Z) - SAFE_BREW_FORMULA: allow @ for versioned formulas ([email protected]) - SAFE_UV_PACKAGE: allow extras [standard] and equality pins == - Cache safeExternalHref result in skills detail API key section * docs: update CONTRIBUTING.md * test: continue vitest threads migration * test: continue vitest threads migration * test: harden threaded shared-worker suites * test: harden threaded channel follow-ups * test: defer slack bolt interop for helper-only suites * fix(agents): harden edit tool recovery (openclaw#52516) Merged via squash. Prepared head SHA: e23bde8 Co-authored-by: mbelinky <[email protected]> Co-authored-by: mbelinky <[email protected]> Reviewed-by: @mbelinky * fix(docs): correct json55 typo to json5 in IRC channel docs (openclaw#50831) (openclaw#50842) Merged via squash. Prepared head SHA: 0f743bf Co-authored-by: Hollychou924 <[email protected]> Co-authored-by: altaywtf <[email protected]> Reviewed-by: @altaywtf * fix(secrets): prevent unresolved SecretRef from crashing embedded agent runs Root cause: Telegram channel monitor captures config at startup before secrets are resolved and passes it as configOverride into the reply pipeline. Since getReplyFromConfig() uses configOverride directly (skipping loadConfig() which reads the resolved runtime snapshot), the unresolved SecretRef objects propagate into FollowupRun.run.config and crash runEmbeddedPiAgent(). Fix (defense in depth): - get-reply.ts: detect unresolved SecretRefs in configOverride and fall back to loadConfig() which returns the resolved runtime snapshot - message-tool.ts: try-catch around schema/description building at tool creation time so channel discovery errors don't crash the agent - message-tool.ts: detect unresolved SecretRefs in pre-bound config at tool execution time and fall back to gateway secret resolution Fixes: openclaw#45838 * fix: merge explicit reply config overrides onto fresh config * fix: clean up failed non-thread subagent spawns * fix: initialize plugins before killed subagent hooks * fix: report qmd status counts from real qmd manager (openclaw#53683) (thanks @neeravmakwana) * fix(memory): report qmd status counts from index * fix(memory): reuse full qmd manager for status * fix(memory): harden qmd status manager lifecycle * fix: ci * fix: finalize killed delete-mode subagent cleanup * fix: clean up attachments for killed subagent runs * feat(cli): support targeting running containerized openclaw instances (openclaw#52651) Signed-off-by: sallyom <[email protected]> * fix: ci * Telegram: recover General topic bindings (openclaw#53699) Merged via squash. Prepared head SHA: 546f0c8 Co-authored-by: huntharo <[email protected]> Co-authored-by: huntharo <[email protected]> Reviewed-by: @huntharo * fix: clean up attachments for released subagent runs * fix(ci): do not cancel in-progress main runs * fix: clean up attachments for orphaned subagent runs * test: speed up discord extension suites * test: speed up slack extension suites * test: speed up telegram extension suites * test: speed up whatsapp and shared test suites * fix(ci): do not cancel in-progress bun runs on main * fix: clean up attachments when replacing subagent runs * feat(discord): add autoThreadName 'generated' strategy (openclaw#43366) * feat(discord): add autoThreadName 'generated' strategy Adds async thread title generation for auto-created threads: - autoThread: boolean - enables/disables auto-threading - autoThreadName: 'message' | 'generated' - naming strategy - 'generated' uses LLM to create concise 3-6 word titles - Includes channel name/description context for better titles - 10s timeout with graceful fallback * Discord: support non-key auth for generated thread titles * Discord: skip fallback auto-thread rename * Discord: normalize generated thread title first content line * Discord: split thread title generation helpers * Discord: tidy thread title generation constants and order * Discord: use runtime fallback model resolution for thread titles * Discord: resolve thread-title model aliases * Discord: fallback thread-title model selection to runtime defaults * Agents: centralize simple completion runtime * fix(discord): pass apiKey to complete() for thread title generation The setRuntimeApiKey approach only works for full agent runs that use authStorage.getApiKey(). The pi-ai complete() function expects apiKey directly in options or falls back to env vars — it doesn't read from authStorage.runtimeOverrides. Fixes thread title generation for Claude/Anthropic users. * fix(agents): return exchanged Copilot token from prepareSimpleCompletionModel The recent thread-title fix (3346ba6) passes prepared.auth.apiKey to complete(). For github-copilot, this was still the raw GitHub token rather than the exchanged runtime token, causing auth failures. Now setRuntimeApiKeyForCompletion returns the resolved token and prepareSimpleCompletionModel includes it in auth.apiKey, so both the authStorage path and direct apiKey pass-through work correctly. * fix(agents): catch auth lookup exceptions in completion model prep getApiKeyForModel can throw for credential issues (missing profile, etc). Wrap in try/catch to return { error } for fail-soft handling rather than propagating rejected promises to callers like thread title generation. * Discord: strip markdown wrappers from generated thread titles * Discord/agents: align thread-title model and local no-auth completion headers * Tests: import fresh modules for mocked thread-title/simple-completion suites * Agents: apply exchanged Copilot baseUrl in simple completions * Discord: route thread runtime imports through plugin SDK * Lockfile: add Discord pi-ai runtime dependency * Lockfile: regenerate Discord pi-ai runtime dependency entries * Agents: use published Copilot token runtime module * Discord: refresh config baseline and lockfile * Tests: split extension runs by isolation * Discord: add changelog for generated thread titles (openclaw#43366) (thanks @davidguttman) --------- Co-authored-by: Onur Solmaz <[email protected]> Co-authored-by: Onur Solmaz <[email protected]> * add missing autoArchiveDuration to DiscordGuildChannelConfig type (openclaw#43427) * add missing autoArchiveDuration to DiscordGuildChannelConfig type The autoArchiveDuration field is present in the Zod schema (DiscordGuildChannelSchema) and actively used at runtime in threading.ts and allow-list.ts, but was missing from the canonical TypeScript type definition. Add autoArchiveDuration to DiscordGuildChannelConfig to align the type with the schema and runtime usage. * Discord: add changelog for config type fix (openclaw#43427) (thanks @davidguttman) --------- Co-authored-by: Onur Solmaz <[email protected]> * refactor: dedupe test and script helpers * test: speed up discord extension suites * test: speed up slack extension suites * test: speed up telegram extension suites * test: speed up signal and whatsapp extension suites * fix(discord): avoid bundling pi-ai runtime deps * fix(lockfile): sync discord dependency removal * test: speed up discord slack telegram suites * test: speed up whatsapp and signal suites * test: speed up google and twitch suites * test: speed up core unit suites * fix: preserve cleanup hooks after subagent register failure * fix: preserve session cleanup hooks after subagent announce * Feishu: avoid CLI startup failure on unresolved SecretRef * fix(doctor): add missing baseUrl and models when migrating nano-banana apiKey to google provider The legacy nano-banana-pro skill migration moves the Gemini API key to models.providers.google.apiKey but does not populate the required baseUrl and models fields on the provider entry. When the google provider object is freshly created (no pre-existing config), the resulting config fails Zod validation on write: Config validation failed: models.providers.google.baseUrl: Invalid input: expected string, received undefined Fix: default baseUrl to 'https://generativelanguage.googleapis.com' and models to [] when they are not already set, matching the defaults used elsewhere in the codebase (embeddings-gemini, pdf-native-providers). Fixes the 'doctor --fix' crash for users who only have a legacy nano-banana-pro skill entry and no existing models.providers.google. * fix: use v1beta for migrated google nano banana provider (openclaw#53757) (thanks @mahopan) * docs: add changelog for PR openclaw#53675 (thanks @hpt) * fix(msteams): harden feedback reflection follow-ups * test: stabilize preaction process title assertion (openclaw#53808) Regeneration-Prompt: | Current origin/main fails src/cli/program/preaction.test.ts because the test asserts on process.title directly inside Vitest, where that runtime interaction is not stable enough to observe the write reliably. Keep the production preaction behavior unchanged. Make the test verify that the hook assigns the expected title by wrapping process.title with a local getter/setter during each test and restoring the original descriptor afterward so other tests keep the real process object behavior. * fix(auth): protect fresher codex reauth state - invalidate cached Codex CLI credentials when auth.json changes within the TTL window - skip external CLI sync when the stored Codex OAuth credential is newer - cover both behaviors with focused regression tests Refs openclaw#53466 Co-authored-by: Copilot <[email protected]> * fix: return structured errors for subagent control send failures * refactor: centralize google API base URL handling * refactor(msteams): split reply and reflection helpers * refactor(auth): unify external CLI credential sync * refactor: split feishu runtime and inspect secret resolution * test(memory): clear browser and plugin caches between cases * fix(types): add workspace module shims * fix: avoid duplicate orphaned subagent resumes * test(memory): enable lower-interval heap snapshots * fix: audit clobbered config reads * fix(whatsapp): filter fromMe messages in groups to prevent infinite loop (openclaw#53386) * fix: suppress only recent whatsapp group echoes (openclaw#53624) (thanks @w-sss) * test: speed up slack and telegram suites * test: speed up cli and model command suites * test: speed up command runtime suites * test: speed up backup and doctor suites * fix(memory): avoid caching status-only managers * fix: stabilize logging config imports * fix(slack): improve interactive reply parity (openclaw#53389) * fix(slack): improve interactive reply parity * fix(slack): isolate reply interactions from plugins * docs(changelog): note slack interactive parity fixes * fix(slack): preserve preview text for local agent replies * fix(agent): preserve directive text in local previews * test: preserve child_process exports in restart bun mock * fix(memory): avoid caching qmd status managers * test: speed up browser and gateway suites * test: speed up media fetch suite * fix(acp): deliver final result text as fallback when no blocks routed - Check routedCounts.final to detect prior delivery - Skip fallback for ttsMode='all' to avoid duplicate TTS processing - Use delivery.deliver for proper routing in cross-provider turns - Fixes openclaw#46814 where ACP child run results were not delivered * fix: tighten ACP final fallback semantics (openclaw#53692) (thanks @w-sss) * fix: unify pi runner usage snapshot fallback * refactor: isolate ACP final delivery flow * fix(ci): stop dropping pending main workflow runs * test(memory): isolate new unit hotspot files * test(memory): isolate browser remote-tab hotspot * test(memory): isolate plugin-core hotspot * test(memory): isolate telegram bot hotspot * fix: continue subagent kill after session store write failures * test(memory): isolate telegram fetch hotspot * test: speed up plugin-sdk and cron suites * test: speed up browser suites * test(memory): isolate telegram monitor hotspot * test(memory): isolate slack action-runtime hotspot * test(memory): recycle shared channels batches * fix: fail closed when subagent steer remap fails * Providers: fix kimi-coding thinking normalization * Providers: fix kimi fallback normalization * Plugins: resolve sdk aliases from the running CLI * Plugins: trust only startup cli sdk roots * Plugins: sanitize sdk export subpaths * Webchat: handle bare /compact as session compaction * Chat UI: tighten compact transport handling * Chat UI: guard compact retries * fix: ignore stale subagent steer targets * fix(discord): notify user on discord when inbound worker times out (openclaw#53823) * fix(discord): notify user on discord when inbound worker times out. * fix(discord): notify user on discord when inbound worker times out. * Discord: await timeout fallback reply * Discord: add changelog for timeout reply fix (openclaw#53823) (thanks @Kimbo7870) --------- Co-authored-by: VioGarden <[email protected]> Co-authored-by: Onur Solmaz <[email protected]> * refactor(channels): route registry lookups through runtime * refactor(plugins): make runtime registry lazy * refactor(plugins): make hook runner global lazy * refactor(plugins): make command registry lazy * fix: allow compact retry after failed session compaction (openclaw#53875) * refactor(gateway): make plugin fallback state lazy * refactor(plugins): make interactive state lazy * fix(memory): align status manager concurrency test * fix(runtime): stabilize dist runtime artifacts (openclaw#53855) * fix(build): stabilize lazy runtime entry paths * fix(runtime): harden bundled plugin npm staging * docs(changelog): note runtime artifact fixes * fix(runtime): stop trusting npm_execpath * fix(runtime): harden Windows npm staging * fix(runtime): add safe Windows npm fallback * ci: start required checks earlier (openclaw#53844) * ci: start required checks earlier * ci: restore pnpm in security-fast * ci: skip docs-only payloads in early check jobs * ci: harden untrusted pull request execution * ci: pin gradle setup action * ci: normalize pull request concurrency cancellation * ci: remove duplicate early-lane setup * ci: keep install-smoke push runs unique * fix: unblock supervisor and memory gate failures * test: stabilize low-profile parallel gate * refactor(core): make event and queue state lazy * fix(ci): refresh plugin sdk baseline and formatting * chore: refresh plugin sdk api baseline * fix: ignore stale subagent kill targets * perf(plugins): scope web search plugin loads * fix: ignore stale subagent send targets * fix: validate agent workspace paths before writing identity files (openclaw#53882) * fix: validate agent workspace paths before writing identity files * Feedback updates and formatting fixes * refactor: dedupe tests and harden suite isolation * test: fix manifest registry fixture typing * fix: ignore stale bulk subagent kill targets * fix(cli): precompute bare root help startup path * fix(test): stabilize npm runner path assertion * test(gateway): align safe open error code * test: speed up targeted unit suites * fix: prefer current subagent targets over stale rows * fix(ci): use target-platform npm path semantics * Adjust CLI backend environment handling before spawn (openclaw#53921) security(agents): sanitize CLI backend env overrides before spawn * fix: surface finished subagent send targets * perf(memory): avoid eager provider init on empty search * fix(test): satisfy cli backend config typing * fix: let subagent kill cascade through ended parents * perf(sqlite): use existence probes for empty memory search * fix: allow follow-up sends to finished subagents * fix: steer ended subagent orchestrators with live descendants * test: speed up browser pw-tools-core suites * test: speed up memory and secrets suites * fix(ci): align lazy memory provider tests * fix(test): stabilize memory vector dedupe assertion * fix(test): isolate github copilot token imports * fix: keep active-descendant subagents visible in reply status * refactor: dedupe helpers and source seams * test: fix rebase gate regressions * Adjust Feishu webhook request body limits (openclaw#53933) * fix: dedupe stale subagent rows in reply views * ci: batch shared extensions test lane * fix: report deduped subagent totals * fix: dedupe verbose subagent status counts * fix: align /agents ids with subagent targets * refactor: dedupe test helpers and harnesses * perf(memory): builtin sqlite hot-path follow-ups (openclaw#53939) * chore(perf): start builtin sqlite hotpath workstream * perf(memory): reuse sqlite statements during sync * perf(memory): snapshot file state during sync * perf(memory): consolidate status sqlite reads * docs(changelog): note builtin sqlite perf work * perf(memory): avoid session table scans on targeted sync * test: speed up memory provider suites * test: speed up slack monitor suites * test: speed up discord channel suites * test: speed up telegram and whatsapp suites * ci: increase test shard fanout * fix: clean up matrix /agents binding labels * fix: dedupe active child session counts * fix: dedupe restarted descendant session counts * fix: blcok non-owner authorized senders from chaning /send policy (openclaw#53994) * fix(slack): trim DM reply overhead and restore Codex auto transport (openclaw#53957) * perf(slack): instrument runtime and trim DM overhead * perf(slack): lazy-init draft previews * perf(slack): add turn summary diagnostics * perf(core): trim repeated runtime setup noise * perf(core): preselect default web search providers * perf(agent): restore OpenAI auto transport defaults * refactor(slack): drop temporary perf wiring * fix(slack): address follow-up review notes * fix(security): tighten slack and runtime defaults * style(web-search): fix import ordering * style(agent): remove useless spread fallback * docs(changelog): note slack runtime hardening * test: speed up discord monitor suites * test: speed up cli and command suites * test: speed up slack monitor suites * fix: ignore stale rows in subagent activity checks * fix: prefer latest subagent rows for session control * fix: ignore stale rows in subagent admin kill * fix: dedupe stale child completion announces * fix: ignore stale rows in subagent steer * fix: cascade bulk subagent kills past stale rows * fix: address FootGun's PR #8 review — regenerate metadata + fix Zulip imports 1. Regenerated bundled-plugin-metadata.generated.ts (stale after upstream merge) 2. Fixed Zulip extension monolithic plugin-sdk imports: - OpenClawPluginApi → openclaw/plugin-sdk/plugin-entry - emptyPluginConfigSchema, PluginRuntime, OpenClawConfig → openclaw/plugin-sdk/core - ChannelAccountSnapshot inline imports → openclaw/plugin-sdk/zulip 3. Added ChannelAccountSnapshot re-export to src/plugin-sdk/zulip.ts --------- Signed-off-by: HCL <[email protected]> Signed-off-by: sallyom <[email protected]> Co-authored-by: Devin Robison <[email protected]> Co-authored-by: Peter Steinberger <[email protected]> Co-authored-by: Val Alexander <[email protected]> Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]> Co-authored-by: Rolfy <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> Co-authored-by: Taras Lukavyi <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> Co-authored-by: Vincent Koc <[email protected]> Co-authored-by: sudie-codes <[email protected]> Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]> Co-authored-by: giulio-leone <[email protected]> Co-authored-by: Copilot <[email protected]> Co-authored-by: HCL <[email protected]> Co-authored-by: Protocol-zero-0 <[email protected]> Co-authored-by: Sid Uppal <[email protected]> Co-authored-by: Catalin Lupuleti <[email protected]> Co-authored-by: Tao Xie <[email protected]> Co-authored-by: Tao Xie <[email protected]> Co-authored-by: joelnishanth <[email protected]> Co-authored-by: Mariano <[email protected]> Co-authored-by: HollyChou <[email protected]> Co-authored-by: altaywtf <[email protected]> Co-authored-by: Neerav Makwana <[email protected]> Co-authored-by: Sally O'Malley <[email protected]> Co-authored-by: Harold Hunt <[email protected]> Co-authored-by: huntharo <[email protected]> Co-authored-by: David Guttman <[email protected]> Co-authored-by: Onur Solmaz <[email protected]> Co-authored-by: Onur Solmaz <[email protected]> Co-authored-by: Han Pingtian <[email protected]> Co-authored-by: Maho Pan <[email protected]> Co-authored-by: Josh Lehman <[email protected]> Co-authored-by: w-sss <[email protected]> Co-authored-by: scoootscooob <[email protected]> Co-authored-by: Bob <[email protected]> Co-authored-by: VioGarden <[email protected]> Co-authored-by: scoootscooob <[email protected]> Co-authored-by: Devin Robison <[email protected]>

* fix(slack): improve interactive reply parity * fix(slack): isolate reply interactions from plugins * docs(changelog): note slack interactive parity fixes * fix(slack): preserve preview text for local agent replies * fix(agent): preserve directive text in local previews

fix(slack): improve interactive reply parity

b2b6b88

vincentkoc self-assigned this Mar 24, 2026

openclaw-barnacle bot added channel: slack Channel integration: slack agents Agent runtime and tooling size: L maintainer Maintainer-authored PR labels Mar 24, 2026

vincentkoc marked this pull request as ready for review March 24, 2026 16:38

Merge branch 'main' into fix/slack-interactive-parity

44a524f

chatgpt-codex-connector bot reviewed Mar 24, 2026

View reviewed changes

src/agents/command/delivery.ts Show resolved Hide resolved

vincentkoc added 2 commits March 24, 2026 09:50

fix(slack): isolate reply interactions from plugins

2dd6f6c

docs(changelog): note slack interactive parity fixes

76067f4

greptile-apps bot reviewed Mar 24, 2026

View reviewed changes

src/auto-reply/reply/slack-directives.ts Show resolved Hide resolved

fix(slack): preserve preview text for local agent replies

38d80f7

chatgpt-codex-connector bot reviewed Mar 24, 2026

View reviewed changes

src/agents/command/delivery.ts Outdated Show resolved Hide resolved

vincentkoc added 2 commits March 24, 2026 10:21

fix(agent): preserve directive text in local previews

e37879f

Merge branch 'main' into fix/slack-interactive-parity

2f1bf68

vincentkoc merged commit f2475a7 into main Mar 24, 2026
8 checks passed

vincentkoc deleted the fix/slack-interactive-parity branch March 24, 2026 17:23

github-actions bot mentioned this pull request Mar 24, 2026

📡 Upstream Digest — 2026-03-24 18:52 UTC curtismercier/openclaw-mods#352

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(slack): improve interactive reply parity#53389

fix(slack): improve interactive reply parity#53389
vincentkoc merged 7 commits intomainfrom
fix/slack-interactive-parity

vincentkoc commented Mar 24, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

greptile-apps bot commented Mar 24, 2026 •

edited

Loading

Comments Outside Diff (1)

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

aisle-research-bot bot commented Mar 24, 2026 •

edited

Loading

1. 🔵 Ambiguous Slack account selection enables interactive replies when accountId is omitted

Description

Recommendation

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

vincentkoc commented Mar 24, 2026

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Root Cause / Regression History (if applicable)

Regression Test Plan (if applicable)

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Review Conversations

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

greptile-apps bot commented Mar 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 4/5

Comments Outside Diff (1)

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

aisle-research-bot bot commented Mar 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Aisle Security Analysis

1. 🔵 Ambiguous Slack account selection enables interactive replies when accountId is omitted

Description

Recommendation

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

greptile-apps bot commented Mar 24, 2026 •

edited

Loading

aisle-research-bot bot commented Mar 24, 2026 •

edited

Loading