fix(slack): trim DM reply overhead and restore Codex auto transport by vincentkoc · Pull Request #53957 · openclaw/openclaw

vincentkoc · 2026-03-24T21:02:47Z

Summary

Problem: Slack DM turns had avoidable hot-path overhead, and embedded Codex/OpenAI sessions silently inherited upstream transport: "sse" even when OpenClaw intended auto.
Why it matters: local Slack debugging felt slower than it should, DM preview setup was still being initialized on paths that never used it, and Codex was missing its intended transport path on embedded runs.
What changed: lazy-init Slack draft previews only on preview-only paths, cache Slack DM channel resolution, trim repeated runtime setup noise, preselect default web-search providers, and restore implicit Codex/OpenAI auto transport only when session settings did not explicitly pin transport.
What did NOT change (scope boundary): no prompt/context trimming, no non-Slack channel transport work, no model/provider swap.

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: embedded Pi sessions inherited SettingsManager.getTransport()'s implicit "sse" default, which overrode OpenClaw's OpenAI/Codex transport wrappers and model params on real runs. Slack also initialized draft preview plumbing on DM paths where preview streaming was disabled.
Missing detection / guardrail: unit tests only exercised wrapper-level stream options, not the full session path where the upstream agent default transport was injected.
Prior context (git blame, prior PR, issue, or refactor if known): recent Slack latency work exposed that reply.dispatch still dominated warm DM latency even after transport/send-path cleanup.
Why this regressed now: end-to-end Slack debugging made the hidden runtime transport mismatch visible.
If unknown, what was ruled out: ruled out Slack send/prepare as the main bottleneck after DM caching and preview-send removal dropped those phases substantially.

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/pi-embedded-runner-extraparams.test.ts
Scenario the test should lock in: prepared Codex/OpenAI transport defaults are surfaced for runtime sessions, but explicit session transport settings still win.
Why this is the smallest reliable guardrail: the bug sits at the seam between prepared extra params and session transport selection; this test covers that seam without spinning up full gateway/runtime integration.
Existing test that already covers this (if any): wrapper-level transport tests in the same file covered only direct streamFn options.
If no new test is added, why not: N/A

User-visible / Behavior Changes

Slack DM replies avoid unnecessary draft-preview initialization on non-preview paths.
Slack DM sends reuse DM channel resolution.
Embedded OpenAI/Codex runs now honor OpenClaw's implicit auto transport unless the session explicitly sets transport.
Default-enabled web-search providers stop redoing avoidable runtime selection work on these paths.

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: N/A

Repro + Verification

Environment

OS: macOS
Runtime/container: local gateway foreground run from dist/
Model/provider: openai-codex/gpt-5.4
Integration/channel (if any): Slack Socket Mode DM
Relevant config (redacted): Slack enabled locally

Steps

Run local gateway in foreground.
DM the Slack bot with ping on cold and warm paths.
Inspect Slack turn timing and embedded runner transport logs.

Expected

Slack prepare/send phases stay small.
Draft preview does not initialize on DM paths with preview streaming disabled.
Embedded OpenAI/Codex sessions use auto transport unless explicitly configured otherwise.

Actual

Before fixes: warm Slack turns were still dominated by reply/runtime overhead, and embedded sessions silently started at transport: "sse".
After fixes: warm DM turns dropped materially and runtime logs showed embedded agent transport override: sse -> auto.

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:
- live Slack DM ping/pong round-trips against a foreground gateway
- embedded Codex runtime log now shows embedded agent transport override: sse -> auto
- Slack DM warm path kept send/prepare overhead low after the cleanup
Edge cases checked:
- first cold DM after restart
- warm repeated DM with cache hit
- explicit session transport still suppresses the automatic override in unit coverage
What you did not verify:
- non-Slack channels on this branch
- non-Socket Slack pathways
- full pnpm test / pnpm check

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.

Compatibility / Migration

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

Failure Recovery (if this breaks)

How to disable/revert this change quickly: revert this PR or temporarily pin agent transport explicitly in session settings/config.
Files/config to restore: revert extensions/slack/src/send.ts, extensions/slack/src/monitor/message-handler/dispatch.ts, src/agents/pi-embedded-runner/extra-params.ts, and src/agents/pi-embedded-runner/run/attempt.ts.
Known bad symptoms reviewers should watch for: Slack DM turns regressing upward again, draft preview waking up on top-level DMs, or explicit transport settings being ignored.

Risks and Mitigations

Risk: transport override could accidentally stomp explicit user transport settings.
- Mitigation: override only applies when raw session settings do not explicitly define transport; unit coverage locks that behavior.
Risk: DM channel cache could reuse stale Slack conversation IDs.
- Mitigation: cache is keyed per account+user and only stores conversations.open results for Slack DM channels.

AI-assisted. Lightly tested locally with targeted tests, build, and live Slack verification.

aisle-research-bot · 2026-03-24T21:10:05Z

🔒 Aisle Security Analysis

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

#	Severity	Title
1	🟡 Medium	Slack DM preview streaming can be enabled by computed thread hint, leaking partial drafts
2	🔵 Low	Slack bot token stored in plaintext as part of DM channel cache key
3	🔵 Low	Process-global deduplication of tool-policy warnings can suppress security-relevant logs across sessions/tenants

Vulnerabilities

1. 🟡 Slack DM preview streaming can be enabled by computed thread hint, leaking partial drafts

Property	Value
Severity	Medium
CWE	CWE-200
Location	`extensions/slack/src/monitor/message-handler/dispatch.ts:232-259`

Description

In dispatchPreparedSlackMessage, preview/draft streaming for Slack is gated by shouldEnableSlackPreviewStreaming. For direct messages, the intent (per tests/comments) is to keep preview streaming off unless the DM reply is actually threaded.

However:

dispatchPreparedSlackMessage passes streamThreadHint as threadTs into shouldEnableSlackPreviewStreaming.
streamThreadHint is computed via resolveSlackStreamingThreadHint() → resolveSlackThreadTs(...).
For replyToMode: "first" | "all" on a top-level DM (no incomingThreadTs), resolveSlackThreadTs returns the message timestamp (messageTs), which is not evidence of an existing thread—it's just a plan to create one.
Because shouldEnableSlackPreviewStreaming uses Boolean(threadTs), this computed hint enables preview/draft streaming in DMs.

When enabled, createSlackDraftStream will sendMessageSlack(...) draft updates (and later edit/delete) into Slack. This can expose partial or intermediate assistant content to DM participants (and potentially trigger notifications), contrary to the expectation that top-level DMs should not receive preview streaming.

Vulnerable code:

const streamThreadHint = resolveSlackStreamingThreadHint({ ... });
const previewStreamingEnabled = shouldEnableSlackPreviewStreaming({
  mode: slackStreaming.mode,
  isDirectMessage: prepared.isDirectMessage,
  threadTs: streamThreadHint,
});

Recommendation

Gate DM preview streaming on an actual existing thread, not on a computed thread hint that may be created for reply planning.

For example, pass only the incoming thread marker (or explicit isThreadReply) into the decision:

const previewStreamingEnabled = shouldEnableSlackPreviewStreaming({
  mode: slackStreaming.mode,
  isDirectMessage: prepared.isDirectMessage,
  // Only enable DM preview when we're replying in an existing thread
  threadTs: incomingThreadTs, // or: isThreadReply ? incomingThreadTs : undefined
});

Alternatively, change the API to make intent explicit:

export function shouldEnableSlackPreviewStreaming(params: {
  mode: "off" | "partial" | "block" | "progress";
  isDirectMessage: boolean;
  hasExistingThread: boolean;
}): boolean {
  if (params.mode === "off") return false;
  if (!params.isDirectMessage) return true;
  return params.hasExistingThread;
}

Add/adjust tests to cover dispatchPreparedSlackMessage behavior for DM + replyToMode="all"|"first" ensuring preview streaming remains off unless incomingThreadTs is present.

2. 🔵 Slack bot token stored in plaintext as part of DM channel cache key

Property	Value
Severity	Low
CWE	CWE-522
Location	`extensions/slack/src/send.ts:172-178`

Description

The Slack DM channel resolution cache key includes the full bot token string in plaintext:

createSlackDmCacheKey() concatenates accountId, raw token, and recipientId into the key.
The process-global slackDmChannelCache retains these keys in heap memory (up to 1024 entries) for the lifetime of the process (unless clearSlackDmChannelCache() is called).
While the code shown does not explicitly log the cache, storing secrets verbatim in long-lived in-memory structures increases the blast radius of accidental disclosure (e.g., heap dumps, crash reports, debugging/inspection tooling).

Vulnerable code:

return `${params.accountId ?? "default"}:${params.token}:${params.recipientId}`;

Recommendation

Avoid embedding the raw token value in cache keys. Use a non-secret identifier for the token (preferred), or hash the token before using it as a key component.

Example (hash token before keying):

import { createHash } from "node:crypto";

function tokenKey(token: string): string {
  return createHash("sha256").update(token).digest("hex");
}

function createSlackDmCacheKey(params: {
  accountId?: string;
  token: string;
  recipientId: string;
}): string {
  return `${params.accountId ?? "default"}:${tokenKey(params.token)}:${params.recipientId}`;
}

This keeps tenant isolation (per-account/per-token separation) without retaining the secret itself in the Map key.

3. 🔵 Process-global deduplication of tool-policy warnings can suppress security-relevant logs across sessions/tenants

Property	Value
Severity	Low
CWE	CWE-778
Location	`src/agents/tool-policy-pipeline.ts:12-27`

Description

A process-global seenToolPolicyWarnings cache is used to dedupe identical tool-policy warnings.

applyToolPolicyPipeline() is invoked in request/session contexts (e.g., gateway HTTP tool invocation and agent tool construction).
The dedupe key is the full warning string and the cache is shared across the entire Node.js process, so a warning emitted in one session/tenant can prevent the same warning from being logged for other independent sessions/tenants.
These warnings are security-relevant (unknown allowlist entries) and are part of the operator’s signal for tool-policy misconfiguration; suppressing them can reduce detection/monitoring and complicate incident response.

Vulnerable behavior:

const seenToolPolicyWarnings = new Set<string>();
...
const warning = `tools: ${step.label} allowlist contains unknown entries (${entries}). ${suffix}`;
if (rememberToolPolicyWarning(warning)) {
  params.warn(warning);
}

While the cache is bounded (256), it still creates cross-session interference because it is not scoped by tenant/session/request, and it can be influenced by configuration-specific values (e.g., profile/agent labels), which may vary per user/account in multi-tenant deployments.

Recommendation

Scope warning deduplication to a request/session/tenant context, or move dedupe to the logging layer with structured fields rather than a process-global Set.

Options:

Pass a per-session/per-request cache into applyToolPolicyPipeline:

export function applyToolPolicyPipeline(params: {
  ...
  warningCache?: Set<string>; // per request/session
}) {
  const cache = params.warningCache;
  ...
  if (!cache || !cache.has(warning)) {
    cache?.add(warning);
    params.warn(warning);
  }
}

Include a tenant/session key in the dedupe key (only if you truly want per-tenant dedupe):

const key = `${params.tenantId ?? ""}:${warning}`;

Remove global dedupe and instead rely on logger rate limiting/throttling that does not suppress cross-tenant signals.

If dedupe is kept, ensure it cannot hide warnings across unrelated principals and consider emitting a periodic summary (e.g., "N warnings suppressed") for observability.

Analyzed PR: #53957 at commit b86aa07

_{Last updated on: 2026-03-24T22:08:12Z}

greptile-apps · 2026-03-24T21:14:46Z

Greptile Summary

This PR delivers targeted performance and correctness fixes across three areas: Slack DM turn overhead, embedded Codex/OpenAI transport selection, and web-search provider auto-detection. The changes are well-scoped, well-tested, and backwards-compatible.

Key changes:

dispatch.ts — createSlackDraftStream is now lazy-initialised only when preview streaming is actually needed (shouldUseDraftStream), avoiding unnecessary object setup on plain DM reply paths.
send.ts — Slack DM channel resolution (conversations.open) is now cached per accountId:userId using a resolveGlobalMap-backed store, eliminating redundant API calls on warm DM paths.
extra-params.ts / attempt.ts — applyExtraParamsToAgent now returns effectiveExtraParams; a new resolveAgentTransportOverride function reads those params and restores the implicit auto transport for OpenAI/Codex sessions unless the user's global or project settings explicitly pin transport. This fixes the silent sse inheritance from SettingsManager.getTransport().
runtime-web-tools.ts — Provider resolution now runs even when the tools.web.search config block is absent, enabling auto-detection of a default provider (e.g. DuckDuckGo) without requiring explicit config.
tool-policy-pipeline.ts — Identical unknown-allowlist warnings are now deduplicated via a module-level Set, reducing log noise on repeated tool pipeline evaluations.

Minor issues found:

An indentation regression in dispatch.ts inside updateDraftFromPartial and the adjacent onDraftBoundary declaration shifts several lines by 2 extra spaces after the refactor. Execution is unaffected but the visual scoping is misleading.
resolveExtraParams is called twice on the agent hot path (once directly in applyExtraParamsToAgent and once inside resolvePreparedExtraParams). This is correct but slightly inefficient; a future cleanup could unify the calls.

Confidence Score: 4/5

Safe to merge; all changes are backwards-compatible and the two minor issues found are non-blocking style/efficiency improvements.
The transport-override logic is the most sensitive change, but it is correctly guarded (only fires when neither global nor project settings explicitly set transport) and is backed by dedicated unit test coverage. The Slack lazy-init and caching changes are well-isolated and tested. The one concrete code quality issue (indentation regression in dispatch.ts) is cosmetic and does not affect runtime behaviour. The duplicate resolveExtraParams call is a minor inefficiency that can be cleaned up separately.
extensions/slack/src/monitor/message-handler/dispatch.ts (indentation regression around updateDraftFromPartial / onDraftBoundary)

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/slack/src/monitor/message-handler/dispatch.ts
Line: 444-472

Comment:
**Indentation regression in `updateDraftFromPartial` / `onDraftBoundary`**

The refactor accidentally shifted several lines by an extra 2 spaces. `draftStream?.update(...)` at lines 444 and 454 are indented at 8 spaces instead of 6 (inside their respective `if` blocks). The fall-through `draftStream?.update(trimmed)` and `hasStreamedMessage = true` at lines 459-460 are at 6 spaces instead of 4 (body of the arrow function). The closing `};` of `updateDraftFromPartial` (line 461) is at 4 spaces instead of 2. As a result, `const onDraftBoundary` (line 462) is also indented 2 spaces too deep, making it look like it is declared inside the callback rather than alongside it.

Execution is correct — JavaScript ignores indentation — but the visual nesting is misleading, especially the `onDraftBoundary` declaration appearing to be inside `updateDraftFromPartial`.

```suggestion
        draftStream?.update(next.rendered);
      hasStreamedMessage = true;
      return;
    }

    if (streamMode === "status_final") {
      statusUpdateCount += 1;
      if (statusUpdateCount > 1 && statusUpdateCount % 4 !== 0) {
        return;
      }
      draftStream?.update(buildStatusFinalPreviewText(statusUpdateCount));
      hasStreamedMessage = true;
      return;
    }

    draftStream?.update(trimmed);
    hasStreamedMessage = true;
  };
  const onDraftBoundary =
    !shouldUseDraftStream
      ? undefined
      : async () => {
          if (hasStreamedMessage) {
            draftStream?.forceNewMessage();
            hasStreamedMessage = false;
            appendRenderedText = "";
            appendSourceText = "";
```

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/agents/pi-embedded-runner/extra-params.ts
Line: 281-300

Comment:
**`resolveExtraParams` called twice on the hot path**

After the refactor, `applyExtraParamsToAgent` calls `resolveExtraParams` twice with the same arguments: once directly (line 281, to keep `resolvedExtraParams` and `override` available for the `resolveAliasedParamValue` / `parallel_tool_calls` logic further down), and a second time inside `resolvePreparedExtraParams` (line 293). The result is functionally correct since the inputs are identical, but it doubles the config-parse work on every agent invocation.

A small follow-up refactor could accept the already-computed `resolvedExtraParams` as an optional input to `resolvePreparedExtraParams`, or inline the `parallel_tool_calls` resolution into `resolvePreparedExtraParams` so the call can be unified. Not blocking, but worth a follow-up to avoid unnecessary repetition.

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

_{Reviews (1): Last reviewed commit: "Merge branch 'main' into fix/slack-perf-..." | Re-trigger Greptile}

extensions/slack/src/monitor/message-handler/dispatch.ts

src/agents/pi-embedded-runner/extra-params.ts

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7e9a072494

ℹ️ 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/secrets/runtime-web-tools.ts

extensions/slack/src/send.ts

@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]>

…penclaw#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

vincentkoc added 6 commits March 24, 2026 14:02

perf(slack): instrument runtime and trim DM overhead

f2a32dd

perf(slack): lazy-init draft previews

233ab3c

perf(slack): add turn summary diagnostics

f99dd7f

perf(core): trim repeated runtime setup noise

523c2ac

perf(core): preselect default web search providers

cdb6441

perf(agent): restore OpenAI auto transport defaults

03d90d7

vincentkoc self-assigned this Mar 24, 2026

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

refactor(slack): drop temporary perf wiring

f328cd6

vincentkoc changed the title ~~perf(slack): trim reply overhead and restore Codex auto transport~~ fix(slack): trim DM reply overhead and restore Codex auto transport Mar 24, 2026

openclaw-barnacle bot added size: L and removed size: XL labels Mar 24, 2026

vincentkoc marked this pull request as ready for review March 24, 2026 21:09

vincentkoc requested a review from a team as a code owner March 24, 2026 21:09

Merge branch 'main' into fix/slack-perf-pass-1

7e9a072

greptile-apps bot reviewed Mar 24, 2026

View reviewed changes

extensions/slack/src/monitor/message-handler/dispatch.ts Outdated Show resolved Hide resolved

src/agents/pi-embedded-runner/extra-params.ts Show resolved Hide resolved

chatgpt-codex-connector bot reviewed Mar 24, 2026

View reviewed changes

src/secrets/runtime-web-tools.ts Outdated Show resolved Hide resolved

extensions/slack/src/send.ts Outdated Show resolved Hide resolved

vincentkoc added 5 commits March 24, 2026 14:22

fix(slack): address follow-up review notes

fcebac2

fix(security): tighten slack and runtime defaults

336de76

style(web-search): fix import ordering

6991eda

style(agent): remove useless spread fallback

9f50b5f

docs(changelog): note slack runtime hardening

b86aa07

vincentkoc merged commit e28b516 into openclaw:main Mar 24, 2026
9 checks passed

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

📡 Upstream Digest — 2026-03-24 22:23 UTC curtismercier/openclaw-mods#354

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(slack): trim DM reply overhead and restore Codex auto transport#53957

fix(slack): trim DM reply overhead and restore Codex auto transport#53957
vincentkoc merged 13 commits intoopenclaw:mainfrom
vincentkoc:fix/slack-perf-pass-1

vincentkoc commented Mar 24, 2026 •

edited

Loading

Uh oh!

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

edited

Loading

1. 🟡 Slack DM preview streaming can be enabled by computed thread hint, leaking partial drafts

Description

Recommendation

2. 🔵 Slack bot token stored in plaintext as part of DM channel cache key

Description

Recommendation

3. 🔵 Process-global deduplication of tool-policy warnings can suppress security-relevant logs across sessions/tenants

Description

Recommendation

Uh oh!

greptile-apps bot commented Mar 24, 2026

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

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

Uh oh!

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!

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. 🟡 Slack DM preview streaming can be enabled by computed thread hint, leaking partial drafts

Description

Recommendation

2. 🔵 Slack bot token stored in plaintext as part of DM channel cache key

Description

Recommendation

3. 🔵 Process-global deduplication of tool-policy warnings can suppress security-relevant logs across sessions/tenants

Description

Recommendation

Uh oh!

greptile-apps bot commented Mar 24, 2026

Greptile Summary

Confidence Score: 4/5

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

vincentkoc commented Mar 24, 2026 •

edited

Loading

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

edited

Loading