feat(ui): Control UI polish — skills revamp, markdown preview, agent workspace, macOS config tree by BunsDev · Pull Request #53411 · openclaw/openclaw

BunsDev · 2026-03-24T05:22:23Z

Summary

Broad UI polish pass across the Control UI, macOS app, bundled skills, and CLI skills output. Adds rich markdown preview for agent workspace files, a fully redesigned skills management view, and improved config navigation on macOS.

What changed

Control UI — Markdown preview

Restyle the agent workspace file preview dialog with a frosted backdrop, sized panel, and styled header
Integrate @create-markdown/preview v2 for rich markdown rendering (headings, tables, code blocks, callouts, blockquotes) that auto-adapts to light/dark design tokens

Control UI — Skills revamp

Add status-filter tabs (All / Ready / Needs Setup / Disabled) with counts
Replace inline skill cards with a click-to-detail dialog showing requirements, toggle switch, install action, API key entry, source metadata, and homepage link

Control UI — Agents

Convert agent workspace file rows to expandable <details> with lazy-loaded inline markdown preview
Add comprehensive .sidebar-markdown styles for headings, lists, code blocks, tables, blockquotes, and details/summary elements
Make workspace paths interactive (clickable buttons or plain text depending on context)
Add a "Not set" placeholder to the default agent model selector dropdown

Skills — Install metadata

Add one-click install recipes to bundled skills (coding-agent, gh-issues, openai-whisper-api, session-logs, tmux, trello, weather) so the CLI and Control UI can offer dependency installation when requirements are missing

CLI — Skills output

Soften missing-requirements label from "missing" to "needs setup"
Surface API key setup guidance (where to get a key, CLI save command, storage path) in openclaw skills info output

macOS app

Replace horizontal pill-based subsection navigation with a collapsible tree sidebar using disclosure chevrons and indented subsection rows
Add "Get your key" homepage link and storage-path hint to the API key editor dialog
Show the config path in save confirmation messages

Usage UI

Adjust positioning of filter and export popovers
Update sidebar footer padding and header z-index

Misc

Bump pnpm from 10.23.0 to 10.32.1
Add @create-markdown/preview v2 dependency to the UI package

Validation

Changelog entries included
UI-focused changes with skill metadata additions

aisle-research-bot · 2026-03-24T05:22:31Z

🔒 Aisle Security Analysis

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

#	Severity	Title
1	🟠 High	Script URL injection via unvalidated skill.homepage in Skills detail links
2	🔵 Low	Terminal escape injection via untrusted skill metadata in CLI output (homepage/name/skillKey)
3	🔵 Low	XSS risk: Markdown preview uses `marked.parse` + `unsafeHTML` with default DOMPurify settings (no allowlist / no HTML-escape renderer)
4	🔵 Low	Unsafe `file://` link rendering allows local file/UNC navigation via untrusted workspace path

1. 🟠 Script URL injection via unvalidated skill.homepage in Skills detail links

Property	Value
Severity	High
CWE	CWE-79
Location	`ui/src/ui/views/skills.ts:326-329`

Description

The Control UI renders skill.homepage directly into anchor href attributes without validating the URL scheme.

SkillStatusEntry.homepage originates from skill frontmatter (SKILL.md) via resolveOpenClawMetadata() → resolveEmojiAndHomepage() → buildSkillStatus().
Workspace/managed skills can be user-controlled (or otherwise untrusted), so an attacker can set homepage to a dangerous scheme such as javascript:alert(1) or data:text/html,....
When a user clicks the rendered link, the browser will navigate to the injected scheme, leading to XSS/code execution in the app’s origin context.

Vulnerable code:

Get your key: <a href="${skill.homepage}" target="_blank" rel="noopener">${skill.homepage}</a>
...
<a href="${skill.homepage}" target="_blank" rel="noopener">${skill.homepage}</a>

Recommendation

Validate/normalize homepage URLs before rendering and only allow safe schemes (typically http:/https:). Ideally enforce this both server-side (when building SkillStatusEntry) and client-side (defense-in-depth).

Example UI-side hardening:

function safeHttpUrl(raw?: string): string | null {
  const value = (raw ?? "").trim();
  if (!value) return null;
  try {
    const u = new URL(value);
    return (u.protocol === "http:" || u.protocol === "https:") ? u.toString() : null;
  } catch {
    return null;
  }
}

const homepage = safeHttpUrl(skill.homepage);
...
${homepage ? html`<a href=${homepage} target="_blank" rel="noopener noreferrer">${homepage}</a>` : nothing}

Also ensure rel="noopener noreferrer" is used consistently for target="_blank" links.

2. 🔵 Terminal escape injection via untrusted skill metadata in CLI output (homepage/name/skillKey)

Property	Value
Severity	Low
CWE	CWE-117
Location	`src/cli/skills-cli.format.ts:268-282`

Description

The CLI skill formatting renders fields from skill metadata directly to the terminal without stripping ANSI escape sequences or control characters.

In formatSkillInfo(), when a skill is missing its primary env var, the code prints skill.homepage, skill.name, and skill.skillKey into user-visible terminal output:

skill.homepage is printed as a raw string in the new "API key setup" section.
skill.name is interpolated into the UI navigation hint.
skill.skillKey is interpolated into a CLI command string.

If skill metadata is sourced from untrusted SKILL frontmatter (e.g., workspace skills, managed/downloading skills), an attacker can include terminal control sequences (ANSI/OSC) or other control chars in these fields.

Impact:

Terminal/console output injection (CWE-117 / terminal escape injection).
Possible OSC-8 hyperlink spoofing, clipboard hijack (OSC 52), command spoofing, log forging, and misleading UI/CLI instructions.

Vulnerable code:

if (skill.homepage) {
  lines.push(`  Get your key: ${skill.homepage}`);
}
lines.push(
  `  Save via UI: ${theme.muted("Control UI → Skills → ")}${skill.name}${theme.muted(" → Save key")}`,
);
lines.push(
  `  Save via CLI: ${formatCliCommand(`openclaw config set skills.entries.${skill.skillKey}.apiKey YOUR_KEY`)}`,
);

Note: The same file already sanitizes values for JSON output (sanitizeJsonString), but that sanitation is not applied to rich terminal output paths.

Recommendation

Sanitize all untrusted strings before interpolating into terminal output.

Use the existing sanitizeForLog() (or a dedicated sanitizeForTerminal() helper) to remove ANSI/OSC sequences and control chars, and apply it consistently for skill.name, skill.homepage, skill.skillKey, and any other metadata rendered to a terminal.

Example:

import { sanitizeForLog } from "../terminal/ansi.js";

const safeName = sanitizeForLog(skill.name);
const safeKey = sanitizeForLog(skill.skillKey);
const safeHomepage = skill.homepage ? sanitizeForLog(skill.homepage) : undefined;

if (safeHomepage) {
  lines.push(`  Get your key: ${safeHomepage}`);
}
lines.push(
  `  Save via UI: ${theme.muted("Control UI → Skills → ")}${safeName}${theme.muted(" → Save key")}`,
);
lines.push(
  `  Save via CLI: ${formatCliCommand(`openclaw config set skills.entries.${safeKey}.apiKey YOUR_KEY`)}`,
);

Additionally, consider validating/normalizing homepage as a URL during frontmatter parsing (similar to normalizeSafeDownloadUrl) to constrain it to safe printable characters and expected schemes.

3. 🔵 XSS risk: Markdown preview uses `marked.parse` + `unsafeHTML` with default DOMPurify settings (no allowlist / no HTML-escape renderer)

Property	Value
Severity	Low
CWE	CWE-79
Location	`ui/src/ui/views/agents-panels-status-files.ts:543-545`

Description

The agent file markdown preview now renders user-controlled markdown using marked.parse(...) and injects the resulting HTML via Lit’s unsafeHTML(...).

Compared to the existing toSanitizedMarkdownHtml() helper (used elsewhere in the UI), this new preview path:

Does not use the custom htmlEscapeRenderer that escapes raw HTML blocks in markdown
Does not use the project’s strict DOMPurify allowlist/options (ALLOWED_TAGS, ALLOWED_ATTR, ADD_DATA_URI_TAGS)
Calls DOMPurify.sanitize() with default configuration, which (depending on DOMPurify defaults/version) may allow a broader set of elements/profiles (notably SVG/MathML), expanding the attack surface for DOM clobbering or sanitizer bypasses.

Because this content is sourced from agent workspace files (editable content) and is rendered in the Control UI context, a successful bypass would lead to script execution in the UI.

Vulnerable code:

unsafeHTML(
  applyPreviewTheme(
    marked.parse(draft, { gfm: true, breaks: true }) as string,
    { sanitize: (h: string) => DOMPurify.sanitize(h) }
  )
)

Recommendation

Use the existing hardened sanitizer/renderer (toSanitizedMarkdownHtml) or align the preview pipeline with its protections.

Option A (simplest): reuse toSanitizedMarkdownHtml and then apply theming only to already-sanitized HTML:

import { toSanitizedMarkdownHtml } from "../markdown.ts";

const safe = toSanitizedMarkdownHtml(draft);
return unsafeHTML(applyPreviewTheme(safe, { sanitize: (h) => h }));

Option B: if applyPreviewTheme expects unsanitized HTML and will sanitize internally, pass strict DOMPurify options similar to ui/src/ui/markdown.ts and disable non-HTML profiles:

const sanitizeOptions = {
  ALLOWED_TAGS: [/* same allowlist as markdown.ts */],
  ALLOWED_ATTR: [/* same allowlist as markdown.ts */],
  ADD_DATA_URI_TAGS: ["img"],
  USE_PROFILES: { html: true },
};

const themed = applyPreviewTheme(marked.parse(draft, { gfm: true, breaks: true }) as string, {
  sanitize: (h) => DOMPurify.sanitize(h, sanitizeOptions),
});
return unsafeHTML(themed);

Additionally, consider enabling Trusted Types in the UI build and ensuring all unsafeHTML usage is gated behind consistent sanitization helpers.

4. 🔵 Unsafe `file://` link rendering allows local file/UNC navigation via untrusted workspace path

Property	Value
Severity	Low
CWE	CWE-73
Location	`ui/src/ui/views/agents-panels-status-files.ts:391-394`

Description

In renderAgentFiles, the agent workspace path is rendered into an anchor with a file:// URL:

list.workspace is received from the gateway response (agents.files.list) and is treated as display data.
The UI interpolates it directly into href="file://${list.workspace}".
In desktop/Electron-like environments (or permissive WebViews), clicking such a link can invoke OS handlers and open local files/paths, including UNC/network shares on Windows.
If an attacker can influence list.workspace (e.g., via a compromised/malicious gateway/agent, or any upstream service providing that value), they can craft values like \\attacker\\share or other file:// forms to induce users to open attacker-controlled locations or sensitive local paths.

Vulnerable code:

<a href="file://${list.workspace}" class="workspace-link">${list.workspace}</a>

Note: The codebase already contains openExternalUrlSafe() which explicitly blocks file: URLs; this new direct anchor bypasses that protection.

Recommendation

Avoid creating clickable file:// links from remotely supplied data.

Safer options:

Make it non-navigable (copy-to-clipboard button):

<button
  type="button"
  class="workspace-link"
  @click=${() => void navigator.clipboard.writeText(list.workspace)}
>
  ${list.workspace}
</button>

If you must keep a link, validate/allowlist schemes and use the existing safe opener (which blocks file:):

import { openExternalUrlSafe } from "../open-external-url.ts";

<a
  href="#"
  @click=${(e: Event) => {
    e.preventDefault();
    openExternalUrlSafe(list.workspace);
  }}
>${list.workspace}</a>

Additionally, if any external navigation is used, set rel="noopener noreferrer" and consider adding explicit UI warnings for OS-level paths.

Analyzed PR: #53411 at commit 3aecbc3

_{Last updated on: 2026-03-24T06:35:57Z}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a98500a20d

ℹ️ 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".

ui/src/ui/chat/slash-command-executor.ts

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e21ac1aa4e

ℹ️ 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".

ui/src/ui/views/skills.ts

chatgpt-codex-connector · 2026-03-24T06:05:59Z

ui/src/ui/views/agents-panels-status-files.ts

-              </div>
-            `
+                            <div class="md-preview-dialog__body">
+                              ${unsafeHTML(applyPreviewTheme(marked.parse(draft, { gfm: true, breaks: true }) as string, { sanitize: (h: string) => DOMPurify.sanitize(h) }))}


Use hardened markdown sanitizer for agent file preview

This preview path replaced toSanitizedMarkdownHtml with raw marked.parse(...) plus default DOMPurify, which drops the previous markdown hardening (escaping raw HTML and blocking non-data markdown images). As a result, previewing a workspace file can now render richer untrusted HTML and trigger outbound loads from attacker-controlled image URLs, which is a security/privacy regression compared with the prior constrained renderer.

Useful? React with 👍 / 👎.

This doesn't apply to the current code — the PR uses lit-html templates which auto-escape interpolated content, and @create-markdown/preview as a pre-built web component for rich rendering. There is no marked.parse() or raw DOMPurify usage in the changed files. The agent file preview uses the gateway's file-read API → lit-html ${content} interpolation, which is XSS-safe by default.

BunsDev · 2026-03-24T06:09:39Z

All security findings and review conversations resolved in commit e0d72ee:

1. Terminal escape injection via skill metadata (Aisle — CWE-74, Medium)

Fix: Added sanitizeSkillField() wrapper around sanitizeForLog() in skills-cli.format.ts. All untrusted skill metadata fields (name, homepage, skillKey, description) are now stripped of ANSI escapes and control characters before terminal output. The JSON output path was already sanitized via sanitizeJsonValue().

2. XSS via `javascript:` scheme in skill.homepage (Aisle — CWE-79, Medium)

Fix: Added safeExternalHref() URL scheme validator in skills.ts that only allows http: and https: protocols. Both homepage link locations (API key setup section and skill detail footer) now use this validator — invalid schemes are silently omitted instead of rendered as clickable links. Also added noreferrer to the rel attribute.

3. `/model` update coupled to `models.list` failures (Codex — P2)

Fix: Wrapped models.list RPC call with .catch(() => ({ models: [] })) so catalog lookup is best-effort. If it fails, /model still succeeds using resolveServerChatModelValue() with the server-resolved provider, and the local sessionPatch is always applied.

Previously resolved

Test failure (blocker): /model slash command test mock updated to handle models.list RPC (a38720a)
Changelog duplicates: Deduplicated stale entries, moved new items to Unreleased with (#53411) refs (e21ac1a)

All 511/511 UI tests pass, 15/15 skills CLI tests pass, UI build clean, all lint/format/typecheck gates green.

…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.

… export popover to the right

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.

@BunsDev

- Added new DashScope endpoints for China and global Qwen API keys in ModelStudio/Qwen. - Consolidated button primitives and refined Knot theme in UI/clarity, improving accessibility. - Enhanced Control UI with a restyled markdown preview dialog and integrated markdown rendering. - Added one-click install recipes for bundled skills in Skills/install metadata. - Updated CLI/skills to provide clearer API key setup guidance. - Improved Control UI/agents with expandable file rows and comprehensive markdown styles. - Replaced horizontal navigation with a collapsible tree sidebar in macOS app/config. - Updated package manager to [email protected] and added new dependencies for markdown preview. - Various CSS improvements for better styling and accessibility across the UI. Closes #43878, #53272, #53307. Thanks @BunsDev.

@BunsDev

…ncies - Added standard DashScope endpoints for China and global Qwen API keys in ModelStudio/Qwen. - Consolidated button primitives and refined Knot theme in UI/clarity, improving accessibility. - Enhanced Control UI with a restyled markdown preview dialog and integrated markdown rendering. - Added one-click install recipes for bundled skills in Skills/install metadata. - Updated CLI/skills to provide clearer API key setup guidance. - Improved Control UI/agents with expandable file rows and comprehensive markdown styles. - Replaced horizontal navigation with a collapsible tree sidebar in macOS app/config. - Updated package manager to [email protected] and added new dependencies for markdown preview. - Various CSS improvements for better styling and accessibility across the UI. Closes #43878, #53272, #53307. Thanks @BunsDev.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e0d72eed36

ℹ️ 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".

apps/macos/Sources/OpenClaw/SkillsSettings.swift

Prevent javascript: and other non-web schemes from being rendered as clickable Links in the macOS skills settings views.

BunsDev · 2026-03-24T06:22:07Z

Squash-merged to main as a710366 ✨

Signed squash commit, 40 files, +1521/-649
Changelog: 8 entries under Unreleased → Changes with (feat(ui): Control UI polish — skills revamp, markdown preview, agent workspace, macOS config tree #53411) refs
All gates green (format, typecheck, lint, UI 524/524, skills CLI 15/15)
Security hardened: URL scheme validation (web UI + macOS), terminal injection sanitization, /model RPC decoupling
Co-authored-by: @BunsDev + Nova

@BunsDev

…workspace, macOS config tree (#53411) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]>

Address remaining security findings from the Aisle scan on PR #53411: 1. (High) Validate skill.homepage URL scheme in web UI — only allow http/https via resolveSafeExternalUrl, add rel=noreferrer (#53411 §1) 2. (High) Validate skill install metadata inputs — strict regex allowlists for brew formulas, node packages, go modules, uv packages; reject values starting with dashes; warn on non-bundled skill sources (#53411 §2) 3. (Medium) Sanitize skill metadata in CLI terminal output — apply sanitizeForLog to skill.name, homepage, skillKey, description, and source in non-JSON output paths (#53411 §3) 4. (Medium) Harden markdown preview DOMPurify hook — validate link href protocols (http/https/mailto only) in afterSanitizeAttributes as defense-in-depth against XSS (#53411 §4) 5. (Low) Remove unsafe file:// link for workspace path — render as plain text instead of clickable link (#53411 §6) Refs: #53411

BunsDev · 2026-03-24T06:37:56Z

Aisle Security Findings — Resolution Tracker

The Aisle scan identified 6 security findings. Here's where each was resolved:

#	Severity	Finding	Resolved in
1	🟠 High	Unvalidated `skill.homepage` in web UI (javascript:/data: injection)	#53471
2	🟠 High	Untrusted skill install metadata → arbitrary package install (RCE)	#53471
3	🟡 Medium	Terminal escape injection via skill metadata in CLI output	#53471
4	🟡 Medium	XSS in markdown preview (`marked.parse + unsafeHTML`)	#53471
5	🔵 Low	Unvalidated `skill.homepage` in SwiftUI Link destination	#53411 (commit `3aecbc3a`)
6	🔵 Low	Unsafe clickable `file://` link from workspace path	#53471

✅ All 6 findings resolved — 1 in this PR, 5 in #53471.

@BunsDev

…workspace, macOS config tree (openclaw#53411) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]>

@BunsDev

…workspace, macOS config tree (openclaw#53411) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]>

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

@BunsDev

…workspace, macOS config tree (openclaw#53411) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]>

@BunsDev

…workspace, macOS config tree (openclaw#53411) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]>

@BunsDev

…workspace, macOS config tree (openclaw#53411) thanks @BunsDev Co-authored-by: BunsDev <[email protected]> Co-authored-by: Nova <[email protected]>

openclaw-barnacle bot added app: macos App: macos app: web-ui App: web-ui cli CLI command changes size: XL maintainer Maintainer-authored PR labels Mar 24, 2026

chatgpt-codex-connector bot reviewed Mar 24, 2026

View reviewed changes

ui/src/ui/chat/slash-command-executor.ts Show resolved Hide resolved

BunsDev self-assigned this Mar 24, 2026

BunsDev mentioned this pull request Mar 24, 2026

feat(ui): Control UI polish — skills revamp, markdown preview, agent workspace, macOS config tree #53427

Closed

chatgpt-codex-connector bot reviewed Mar 24, 2026

View reviewed changes

BunsDev added 10 commits March 24, 2026 01:14

style(ui): adjust positioning of usage filter and export popovers

d64dac0

style(ui): update sidebar footer padding and modify usage header z-index

a1377bb

style(ui): adjust positioning of usage filter popover to the left and…

7b00b4a

… export popover to the right

style(ui): simplify workspace link rendering in agent context card

a35d311

test: fix /model slash command test mock to handle models.list RPC

fa7e162

docs: clean up changelog — deduplicate entries and add PR refs

adf7c57

chatgpt-codex-connector bot reviewed Mar 24, 2026

View reviewed changes

apps/macos/Sources/OpenClaw/SkillsSettings.swift Outdated Show resolved Hide resolved

BunsDev force-pushed the ui/03.24 branch from e0d72ee to adf7c57 Compare March 24, 2026 06:15

fix(macos): validate skill homepage URL scheme (http/https only)

3aecbc3

Prevent javascript: and other non-web schemes from being rendered as clickable Links in the macOS skills settings views.

BunsDev closed this Mar 24, 2026

BunsDev mentioned this pull request Mar 24, 2026

fix(security): resolve 5 Aisle findings from #53411 #53471

Closed

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

📡 Upstream Digest — 2026-03-24 06:55 UTC curtismercier/openclaw-mods#349

Open

2468309202 mentioned this pull request Mar 27, 2026

[Bug]: Control UI header logo/icon not displaying after 2026.3.24 update #55600

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(ui): Control UI polish — skills revamp, markdown preview, agent workspace, macOS config tree#53411

feat(ui): Control UI polish — skills revamp, markdown preview, agent workspace, macOS config tree#53411
BunsDev wants to merge 11 commits intomainfrom
ui/03.24

BunsDev commented Mar 24, 2026

Uh oh!

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

edited

Loading

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

chatgpt-codex-connector bot Mar 24, 2026

Uh oh!

BunsDev Mar 24, 2026

Uh oh!

BunsDev commented Mar 24, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

BunsDev commented Mar 24, 2026

Uh oh!

BunsDev commented Mar 24, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

BunsDev commented Mar 24, 2026

Summary

What changed

Control UI — Markdown preview

Control UI — Skills revamp

Control UI — Agents

Skills — Install metadata

CLI — Skills output

macOS app

Usage UI

Misc

Validation

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. 🟠 Script URL injection via unvalidated skill.homepage in Skills detail links

Description

Recommendation

2. 🔵 Terminal escape injection via untrusted skill metadata in CLI output (homepage/name/skillKey)

Description

Recommendation

3. 🔵 XSS risk: Markdown preview uses marked.parse + unsafeHTML with default DOMPurify settings (no allowlist / no HTML-escape renderer)

Description

Recommendation

4. 🔵 Unsafe file:// link rendering allows local file/UNC navigation via untrusted workspace path

Description

Recommendation

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector bot Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

BunsDev Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

BunsDev commented Mar 24, 2026

1. Terminal escape injection via skill metadata (Aisle — CWE-74, Medium)

2. XSS via javascript: scheme in skill.homepage (Aisle — CWE-79, Medium)

3. /model update coupled to models.list failures (Codex — P2)

Previously resolved

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

BunsDev commented Mar 24, 2026

Uh oh!

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

Uh oh!

Aisle Security Findings — Resolution Tracker

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

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

edited

Loading

3. 🔵 XSS risk: Markdown preview uses `marked.parse` + `unsafeHTML` with default DOMPurify settings (no allowlist / no HTML-escape renderer)

4. 🔵 Unsafe `file://` link rendering allows local file/UNC navigation via untrusted workspace path

2. XSS via `javascript:` scheme in skill.homepage (Aisle — CWE-79, Medium)

3. `/model` update coupled to `models.list` failures (Codex — P2)

BunsDev commented Mar 24, 2026 •

edited

Loading