fix: ensure env proxy dispatcher before MiniMax and OpenAI Codex OAuth flows by openperf · Pull Request #52228 · openclaw/openclaw

openperf · 2026-03-22T12:09:04Z

Summary

This PR fixes a regression where the environment-based proxy (HTTP_PROXY/HTTPS_PROXY) is ignored during the MiniMax and OpenAI Codex OAuth flows, causing them to fail in environments that require a proxy (e.g., mitmproxy debugging or corporate networks).

This addresses both #51619 and #51569.

Root Cause

The root cause was identified in #51569: The import path change from @mariozechner/pi-ai to @mariozechner/pi-ai/oauth dropped the implicit http-proxy.js side-effect import that previously called setGlobalDispatcher(new EnvHttpProxyAgent( )).

Since loginMiniMaxPortalOAuth and loginOpenAICodex execute outside the runEmbeddedAttempt lifecycle (which handles proxy initialization for normal LLM requests), the global fetch falls back to the default dispatcher, ignoring proxy environment variables.

Changes

src/plugin-sdk/infra-runtime.ts: Exported undici-global-dispatcher.js so extension plugins can access it.
extensions/minimax/oauth.ts: Added ensureGlobalUndiciEnvProxyDispatcher() before loginMiniMaxPortalOAuth makes any outbound fetch calls.
src/plugins/provider-openai-codex-oauth.ts: Added the same initialization before loginOpenAICodex.
src/agents/minimax-vlm.ts: Added defensive proxy initialization before the VLM fetch call.

Note: While investigating #51619, I also noticed that the MiniMax plugin currently lacks a refreshOAuth implementation (unlike OpenAI Codex). When a MiniMax token expires, the refresh silently fails, which might also manifest as an "LLM ERROR" to the user. I've kept this PR strictly focused on the proxy initialization regression, but the missing refresh hook should probably be addressed in a follow-up PR.

Fixes

Fixes #51619
Fixes #51569

aisle-research-bot · 2026-03-22T12:09:28Z

🔒 Aisle Security Analysis

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

#	Severity	Title
1	🔵 Low	SSRF via configurable MiniMax API host in minimaxUnderstandImage
2	🔵 Low	Plugin SDK exposes global Undici dispatcher mutation (process-wide proxy hijack)

1. 🔵 SSRF via configurable MiniMax API host in minimaxUnderstandImage

Property	Value
Severity	Low
CWE	CWE-918
Location	`src/agents/minimax-vlm.ts:71-92`

Description

minimaxUnderstandImage builds the request URL from a configurable apiHost / modelBaseUrl (and MINIMAX_API_HOST) and then performs a direct fetch() to that URL without SSRF protections.

Input: params.apiHost / params.modelBaseUrl (and environment variable MINIMAX_API_HOST) can point to arbitrary origins.
Sink: fetch(url, ...) is executed without using the project’s SSRF guard (fetchWithSsrFGuard).
Impact: If an attacker can influence these settings (e.g., via user-controlled config, plugin settings, or environment injection), they can trigger outbound requests to internal hosts/IPs (e.g., http://127.0.0.1:..., cloud metadata endpoints, internal services), potentially accessing sensitive internal resources.

Vulnerable code:

const host = coerceApiHost({ apiHost: params.apiHost, modelBaseUrl: params.modelBaseUrl });
const url = new URL("/v1/coding_plan/vlm", host).toString();
const res = await fetch(url, { ... });

Recommendation

Treat apiHost / modelBaseUrl as untrusted and enforce an SSRF policy.

Recommended options:

Use the existing SSRF-guarded fetch (fetchWithSsrFGuard) and optionally a hostname allowlist:

import { fetchWithSsrFGuard } from "../infra/net/fetch-guard.js";

const url = new URL("/v1/coding_plan/vlm", host).toString();
const { response, release } = await fetchWithSsrFGuard({
  url,
  init: {
    method: "POST",
    headers: {
      Authorization: `Bearer ${apiKey}`,
      "Content-Type": "application/json",
      "MM-API-Source": "OpenClaw",
    },
    body: JSON.stringify({ prompt, image_url: imageDataUrl }),
  },
  // Strongly consider restricting hosts if overrides are supported:
  policy: { hostnameAllowlist: ["api.minimax.io"] },
});
try {
  // handle response
} finally {
  await release();
}

If host overrides must exist, validate host against an allowlist and reject IP literals/private hostnames before issuing the request.

2. 🔵 Plugin SDK exposes global Undici dispatcher mutation (process-wide proxy hijack)

Property	Value
Severity	Low
CWE	CWE-15
Location	`src/plugin-sdk/infra-runtime.ts:25-30`

Description

src/plugin-sdk/infra-runtime.ts now re-exports ensureGlobalUndiciEnvProxyDispatcher (and related helpers) from infra/net/undici-global-dispatcher, making it directly available to plugins.

If third-party plugins are not fully trusted, this broadens the attack surface because it enables process-wide mutation of Undici's global dispatcher:

A plugin can set process.env.HTTPS_PROXY/HTTP_PROXY (or rely on existing env) and then call ensureGlobalUndiciEnvProxyDispatcher().
This calls undici.setGlobalDispatcher(new EnvHttpProxyAgent()), affecting all subsequent Undici-based traffic in the host process, including other plugins and core components that use Undici/global fetch without an explicit dispatcher.
Result: traffic can be forced through an attacker-controlled proxy, enabling credential/header leakage and request/response manipulation for unrelated components.

Vulnerable enabling change (re-export):

export * from "../infra/net/undici-global-dispatcher.js";

Underlying global mutation:

setGlobalDispatcher(new EnvHttpProxyAgent());

Recommendation

Do not expose process-global network mutators to untrusted plugins.

Recommended options:

Remove the re-export from the plugin SDK runtime.
If plugins must be able to use a proxy, provide a scoped fetch/client factory that returns a dispatcher/fetch instance for that plugin only (no global mutation):

import { EnvHttpProxyAgent } from "undici";

export function createPluginFetchWithEnvProxy() {
  const dispatcher = new EnvHttpProxyAgent();
  return (input: RequestInfo | URL, init?: RequestInit) =>
    fetch(input, { ...init, dispatcher });
}

If a global dispatcher is unavoidable, gate it behind a trusted-only capability (e.g., only core/bundled plugins, or require an explicit config allowlist), and prevent plugins from toggling it at runtime.

Analyzed PR: #52228 at commit 764a2a1

_{Last updated on: 2026-03-23T14:35:14Z}

greptile-apps · 2026-03-22T12:12:14Z

Greptile Summary

This PR fixes a proxy initialization regression for MiniMax and OpenAI Codex OAuth flows by calling ensureGlobalUndiciEnvProxyDispatcher() in the appropriate places before outbound fetch calls that previously ran outside the runEmbeddedAttempt lifecycle. The approach is sound and the changes are targeted.

The fix is correctly applied in extensions/minimax/oauth.ts (before any fetch in loginMiniMaxPortalOAuth), src/agents/minimax-vlm.ts (before the VLM fetch), and src/plugins/provider-openai-codex-oauth.ts (before loginOpenAICodex).
One ordering issue in provider-openai-codex-oauth.ts: ensureGlobalUndiciEnvProxyDispatcher() is called after runOpenAIOAuthTlsPreflight(), which itself makes an outbound fetch to auth.openai.com. On a proxy-required network the TLS preflight will silently fail as kind: "network" (non-fatal, execution continues), so the OAuth itself works. However, on a corporate MITM proxy that also injects a custom TLS certificate, the preflight will report kind: "network" instead of kind: "tls-cert", suppressing the helpful TLS diagnostic. Moving ensureGlobalUndiciEnvProxyDispatcher() to before runOpenAIOAuthTlsPreflight() is a one-line fix consistent with the PR's own stated goal.
The export * from undici-global-dispatcher.js in infra-runtime.ts also exposes resetGlobalUndiciStreamTimeoutsForTests, a test-only helper, via the public plugin SDK — low risk, but worth noting.

Confidence Score: 4/5

Safe to merge after moving ensureGlobalUndiciEnvProxyDispatcher() to before the TLS preflight fetch in provider-openai-codex-oauth.ts
The fix is well-targeted and the approach is correct. Three of the four changes are cleanly placed before any outbound network calls. The one issue (proxy not set before the TLS preflight fetch in the OpenAI Codex flow) is a one-line ordering fix — it doesn't break the primary OAuth path (the OAuth itself works), but silently misdirects TLS cert diagnostics for users on corporate MITM proxies. That single targeted fix is all that stands between this and a 5.
src/plugins/provider-openai-codex-oauth.ts — ensureGlobalUndiciEnvProxyDispatcher() should be moved before runOpenAIOAuthTlsPreflight() at line 21

Comments Outside Diff (1)

src/plugins/provider-openai-codex-oauth.ts, line 21-60 (link)

Proxy not set before TLS preflight fetch

runOpenAIOAuthTlsPreflight() at line 21 makes an outbound fetch to https://auth.openai.com (see OPENAI_AUTH_PROBE_URL in provider-openai-codex-oauth-tls.ts) before ensureGlobalUndiciEnvProxyDispatcher() is called on line 60. On a proxy-required network this means:

The preflight fetch fires without the proxy and receives a network error.
Since preflight.kind === "network" (not "tls-cert"), execution silently continues — the OAuth itself works fine with the proxy.
However, if the user is on a corporate MITM proxy that also injects a custom certificate (proxy-required network and TLS cert issue), the preflight returns kind: "network" instead of "tls-cert", suppressing the helpful TLS diagnostic message. The user then hits loginOpenAICodex which fails with a TLS cert error but receives no guidance.

ensureGlobalUndiciEnvProxyDispatcher() should be called before runOpenAIOAuthTlsPreflight() — consistent with the PR's own stated goal of ensuring the proxy dispatcher is active before any outbound fetch calls.

// Ensure env-based proxy dispatcher is active before any outbound fetch calls.
ensureGlobalUndiciEnvProxyDispatcher();

const preflight = await runOpenAIOAuthTlsPreflight();

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/plugins/provider-openai-codex-oauth.ts
Line: 21-60

Comment:
**Proxy not set before TLS preflight fetch**

`runOpenAIOAuthTlsPreflight()` at line 21 makes an outbound `fetch` to `https://auth.openai.com` (see `OPENAI_AUTH_PROBE_URL` in `provider-openai-codex-oauth-tls.ts`) before `ensureGlobalUndiciEnvProxyDispatcher()` is called on line 60. On a proxy-required network this means:

1. The preflight fetch fires without the proxy and receives a network error.
2. Since `preflight.kind === "network"` (not `"tls-cert"`), execution silently continues — the OAuth itself works fine with the proxy.
3. **However**, if the user is on a corporate MITM proxy that also injects a custom certificate (proxy-required network **and** TLS cert issue), the preflight returns `kind: "network"` instead of `"tls-cert"`, suppressing the helpful TLS diagnostic message. The user then hits `loginOpenAICodex` which fails with a TLS cert error but receives no guidance.

`ensureGlobalUndiciEnvProxyDispatcher()` should be called **before** `runOpenAIOAuthTlsPreflight()` — consistent with the PR's own stated goal of ensuring the proxy dispatcher is active before any outbound fetch calls.

```
// Ensure env-based proxy dispatcher is active before any outbound fetch calls.
ensureGlobalUndiciEnvProxyDispatcher();

const preflight = await runOpenAIOAuthTlsPreflight();
```

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

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/plugins/provider-openai-codex-oauth.ts
Line: 21-60

Comment:
**Proxy not set before TLS preflight fetch**

`runOpenAIOAuthTlsPreflight()` at line 21 makes an outbound `fetch` to `https://auth.openai.com` (see `OPENAI_AUTH_PROBE_URL` in `provider-openai-codex-oauth-tls.ts`) before `ensureGlobalUndiciEnvProxyDispatcher()` is called on line 60. On a proxy-required network this means:

1. The preflight fetch fires without the proxy and receives a network error.
2. Since `preflight.kind === "network"` (not `"tls-cert"`), execution silently continues — the OAuth itself works fine with the proxy.
3. **However**, if the user is on a corporate MITM proxy that also injects a custom certificate (proxy-required network **and** TLS cert issue), the preflight returns `kind: "network"` instead of `"tls-cert"`, suppressing the helpful TLS diagnostic message. The user then hits `loginOpenAICodex` which fails with a TLS cert error but receives no guidance.

`ensureGlobalUndiciEnvProxyDispatcher()` should be called **before** `runOpenAIOAuthTlsPreflight()` — consistent with the PR's own stated goal of ensuring the proxy dispatcher is active before any outbound fetch calls.

```
// Ensure env-based proxy dispatcher is active before any outbound fetch calls.
ensureGlobalUndiciEnvProxyDispatcher();

const preflight = await runOpenAIOAuthTlsPreflight();
```

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

_{Reviews (1): Last reviewed commit: "fix: ensure env proxy dispatcher before ..." | Re-trigger Greptile}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6fb7ea4881

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

src/plugins/provider-openai-codex-oauth.ts

openperf · 2026-03-22T12:46:50Z

🔒 Aisle Security Analysis

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

Severity Title

1 🟡 Medium OAuth/token requests routed via env-controlled HTTP(S) proxy (global Undici dispatcher)

1. 🟡 OAuth/token requests routed via env-controlled HTTP(S) proxy (global Undici dispatcher)

Property Value
Severity Medium
CWE CWE-15
Location src/plugins/provider-openai-codex-oauth.ts:56-72

Description

ensureGlobalUndiciEnvProxyDispatcher() installs undici’s EnvHttpProxyAgent as the global dispatcher when HTTP_PROXY/HTTPS_PROXY is set, causing subsequent fetch() calls to be routed through the environment-configured proxy.

In the changed code, this bootstrap is performed immediately before sensitive OAuth/token exchange logic:

Proxy selection is controlled by process environment (HTTP_PROXY, HTTPS_PROXY, http_proxy, https_proxy).

If those env vars are attacker-influenced (e.g., untrusted plugin/skill config that can mutate process.env, or multi-tenant/service environments with user-controlled env), OAuth authorization codes, refresh/access tokens, and API credentials may be sent via an attacker-controlled proxy.

For HTTPS, a proxy can still enable credential interception in environments where TLS is terminated/inspected (custom root CAs) or where TLS verification is weakened (e.g., NODE_TLS_REJECT_UNAUTHORIZED=0).

Vulnerable code (changed):
// Ensure env-based proxy dispatcher is active before the OAuth token exchange.
ensureGlobalUndiciEnvProxyDispatcher();

const creds = await loginOpenAICodex({ /* performs token exchange via fetch */ });
Other newly-added call sites that similarly impact sensitive requests:

extensions/minimax/oauth.ts (MiniMax OAuth code + token polling)

src/agents/minimax-vlm.ts (MiniMax API key sent in Authorization: Bearer ... header)

Recommendation

Avoid enabling env-proxy behavior globally for sensitive authentication/token exchanges unless it is explicitly trusted/operator-controlled.

Options:

Make env-proxy opt-in for OAuth/token flows, gated by an explicit config flag (not just presence of HTTP(S)_PROXY).

Use a per-request dispatcher/fetch instead of mutating undici’s global dispatcher, so only the intended calls are proxied.

Example approach (per-request proxy fetch only when explicitly allowed):
import { resolveProxyFetchFromEnv } from "../infra/net/proxy-fetch.js";

const proxyFetch = (runtime.config?.network?.allowEnvProxyForOAuth)
  ? resolveProxyFetchFromEnv(process.env)
  : undefined;

const fetchImpl = proxyFetch ?? globalThis.fetch;
// pass fetchImpl into the OAuth library if supported, or wrap the token exchange call sites
If untrusted components can influence process.env, block proxy-related env keys (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, lowercase variants) from those override mechanisms.

Analyzed PR: #52228 at commit 6fb7ea4

Last updated on: 2026-03-22T12:34:02Z

The ensureGlobalUndiciEnvProxyDispatcher() pattern is already used in the codebase (e.g., attempt.ts:1635 on main) — this PR simply extends the same pattern to OAuth flows that were missing it. The CWE-15 scenario assumes an attacker can control process.env, which is outside the threat model for a CLI tool where env vars are set by the operator. No changes needed here.

openperf · 2026-03-22T12:48:24Z

Greptile Summary

This PR fixes a proxy initialization regression for MiniMax and OpenAI Codex OAuth flows by calling ensureGlobalUndiciEnvProxyDispatcher() in the appropriate places before outbound fetch calls that previously ran outside the runEmbeddedAttempt lifecycle. The approach is sound and the changes are targeted.

The fix is correctly applied in extensions/minimax/oauth.ts (before any fetch in loginMiniMaxPortalOAuth), src/agents/minimax-vlm.ts (before the VLM fetch), and src/plugins/provider-openai-codex-oauth.ts (before loginOpenAICodex).

One ordering issue in provider-openai-codex-oauth.ts: ensureGlobalUndiciEnvProxyDispatcher() is called after runOpenAIOAuthTlsPreflight(), which itself makes an outbound fetch to auth.openai.com. On a proxy-required network the TLS preflight will silently fail as kind: "network" (non-fatal, execution continues), so the OAuth itself works. However, on a corporate MITM proxy that also injects a custom TLS certificate, the preflight will report kind: "network" instead of kind: "tls-cert", suppressing the helpful TLS diagnostic. Moving ensureGlobalUndiciEnvProxyDispatcher() to before runOpenAIOAuthTlsPreflight() is a one-line fix consistent with the PR's own stated goal.

The export * from undici-global-dispatcher.js in infra-runtime.ts also exposes resetGlobalUndiciStreamTimeoutsForTests, a test-only helper, via the public plugin SDK — low risk, but worth noting.

Confidence Score: 4/5

Safe to merge after moving ensureGlobalUndiciEnvProxyDispatcher() to before the TLS preflight fetch in provider-openai-codex-oauth.ts

The fix is well-targeted and the approach is correct. Three of the four changes are cleanly placed before any outbound network calls. The one issue (proxy not set before the TLS preflight fetch in the OpenAI Codex flow) is a one-line ordering fix — it doesn't break the primary OAuth path (the OAuth itself works), but silently misdirects TLS cert diagnostics for users on corporate MITM proxies. That single targeted fix is all that stands between this and a 5.

src/plugins/provider-openai-codex-oauth.ts — ensureGlobalUndiciEnvProxyDispatcher() should be moved before runOpenAIOAuthTlsPreflight() at line 21

Comments Outside Diff (1)
src/plugins/provider-openai-codex-oauth.ts, line 21-60 (link)
Proxy not set before TLS preflight fetch
runOpenAIOAuthTlsPreflight() at line 21 makes an outbound fetch to https://auth.openai.com (see OPENAI_AUTH_PROBE_URL in provider-openai-codex-oauth-tls.ts) before ensureGlobalUndiciEnvProxyDispatcher() is called on line 60. On a proxy-required network this means:

The preflight fetch fires without the proxy and receives a network error.

Since preflight.kind === "network" (not "tls-cert"), execution silently continues — the OAuth itself works fine with the proxy.

However, if the user is on a corporate MITM proxy that also injects a custom certificate (proxy-required network and TLS cert issue), the preflight returns kind: "network" instead of "tls-cert", suppressing the helpful TLS diagnostic message. The user then hits loginOpenAICodex which fails with a TLS cert error but receives no guidance.

ensureGlobalUndiciEnvProxyDispatcher() should be called before runOpenAIOAuthTlsPreflight() — consistent with the PR's own stated goal of ensuring the proxy dispatcher is active before any outbound fetch calls.
// Ensure env-based proxy dispatcher is active before any outbound fetch calls.
ensureGlobalUndiciEnvProxyDispatcher();

const preflight = await runOpenAIOAuthTlsPreflight();
Prompt To Fix With AI
This is a comment left during a code review.
Path: src/plugins/provider-openai-codex-oauth.ts
Line: 21-60

Comment:
**Proxy not set before TLS preflight fetch**

`runOpenAIOAuthTlsPreflight()` at line 21 makes an outbound `fetch` to `https://auth.openai.com` (see `OPENAI_AUTH_PROBE_URL` in `provider-openai-codex-oauth-tls.ts`) before `ensureGlobalUndiciEnvProxyDispatcher()` is called on line 60. On a proxy-required network this means:

1. The preflight fetch fires without the proxy and receives a network error.
2. Since `preflight.kind === "network"` (not `"tls-cert"`), execution silently continues — the OAuth itself works fine with the proxy.
3. **However**, if the user is on a corporate MITM proxy that also injects a custom certificate (proxy-required network **and** TLS cert issue), the preflight returns `kind: "network"` instead of `"tls-cert"`, suppressing the helpful TLS diagnostic message. The user then hits `loginOpenAICodex` which fails with a TLS cert error but receives no guidance.

`ensureGlobalUndiciEnvProxyDispatcher()` should be called **before** `runOpenAIOAuthTlsPreflight()` — consistent with the PR's own stated goal of ensuring the proxy dispatcher is active before any outbound fetch calls.
// Ensure env-based proxy dispatcher is active before any outbound fetch calls.
ensureGlobalUndiciEnvProxyDispatcher();

const preflight = await runOpenAIOAuthTlsPreflight();
How can I resolve this? If you propose a fix, please make it concise.
Prompt To Fix All With AI
This is a comment left during a code review.
Path: src/plugins/provider-openai-codex-oauth.ts
Line: 21-60

Comment:
**Proxy not set before TLS preflight fetch**

`runOpenAIOAuthTlsPreflight()` at line 21 makes an outbound `fetch` to `https://auth.openai.com` (see `OPENAI_AUTH_PROBE_URL` in `provider-openai-codex-oauth-tls.ts`) before `ensureGlobalUndiciEnvProxyDispatcher()` is called on line 60. On a proxy-required network this means:

1. The preflight fetch fires without the proxy and receives a network error.
2. Since `preflight.kind === "network"` (not `"tls-cert"`), execution silently continues — the OAuth itself works fine with the proxy.
3. **However**, if the user is on a corporate MITM proxy that also injects a custom certificate (proxy-required network **and** TLS cert issue), the preflight returns `kind: "network"` instead of `"tls-cert"`, suppressing the helpful TLS diagnostic message. The user then hits `loginOpenAICodex` which fails with a TLS cert error but receives no guidance.

`ensureGlobalUndiciEnvProxyDispatcher()` should be called **before** `runOpenAIOAuthTlsPreflight()` — consistent with the PR's own stated goal of ensuring the proxy dispatcher is active before any outbound fetch calls.
// Ensure env-based proxy dispatcher is active before any outbound fetch calls.
ensureGlobalUndiciEnvProxyDispatcher();

const preflight = await runOpenAIOAuthTlsPreflight();
How can I resolve this? If you propose a fix, please make it concise.
Reviews (1): Last reviewed commit: "fix: ensure env proxy dispatcher before ..." | Re-trigger Greptile

runOpenAIOAuthTlsPreflight() fires an outbound fetch to auth.openai.com before the dispatcher is set. I've moved ensureGlobalUndiciEnvProxyDispatcher() to the top of loginOpenAICodexOAuth, before the preflight call. Fixed in the latest commit.

…h flows (openclaw#51619, openclaw#51569)

Takhoffman · 2026-03-23T14:26:56Z

Merged in 4e849ac after verification with pnpm install --frozen-lockfile, NPM_CONFIG_CACHE=/tmp/openclaw-npm-cache-52228 pnpm build, and pnpm check.
I added the Unreleased changelog entry on the PR branch before merge; the OAuth proxy-dispatch changes landed in CHANGELOG.md under ### Fixes.
pnpm test:macmini hit an inherited pre-existing failure in src/plugins/contracts/registry.contract.test.ts outside this PR surface (deepseek missing from the bundled provider contract registry), so I did not broaden this PR to fix that unrelated contract drift.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 764a2a11f1

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-23T14:31:35Z

src/plugins/provider-openai-codex-oauth.ts

+
+  // Ensure env-based proxy dispatcher is active before any outbound fetch calls,
+  // including the TLS preflight check.
+  ensureGlobalUndiciEnvProxyDispatcher();


Bootstrap the OpenAI Codex refresh flow as well

This only fixes the interactive login path. Expired OpenAI Codex profiles are refreshed from extensions/openai/openai-codex-provider.ts:139-154, which calls getOAuthApiKey() via extensions/openai/openai-codex-provider.runtime.ts:1 from the same @mariozechner/pi-ai/oauth module, but that path still never initializes the env proxy dispatcher. In proxy-required environments, sign-in will succeed now, but the first token refresh outside runEmbeddedAttempt can still fail once the stored access token expires, leaving users locked out again.

Useful? React with 👍 / 👎.

…h flows (openclaw#52228) Verified: - pnpm install --frozen-lockfile - NPM_CONFIG_CACHE=/tmp/openclaw-npm-cache-52228 pnpm build - pnpm check - pnpm test:macmini (failed on inherited pre-existing plugin contract test: src/plugins/contracts/registry.contract.test.ts missing deepseek in bundled provider contract registry outside this PR surface) Co-authored-by: openperf <[email protected]> Co-authored-by: Tak Hoffman <[email protected]>

@CodeForgeNet

…d off (#2) * refactor(plugins): move remaining channel and provider ownership out of src * refactor(plugins): finish provider and whatsapp cleanup * fix(gateway): pass process.env in status command probe auth to resolve SecretRef Fixes openclaw#52360 resolveGatewayProbeAuthSafe was called from status-all.ts without an env argument, causing the credential resolution chain to fall back to an empty object instead of process.env. This made env-backed SecretRef tokens (gateway.auth.token, Telegram botToken, etc.) appear unresolved in the status command path even when the runtime was healthy. Added process.env as default fallback in buildGatewayProbeCredentialPolicy and passed env explicitly from status-all.ts callers. Related: openclaw#33070, openclaw#38973, openclaw#39415, openclaw#46014, openclaw#49730 * fix(status): resolve only selected probe-auth branch and fix plain status path Address two Codex P1/P2 issues: 1. (P1) Plain 'openclaw status' and 'openclaw status --json' still went through the sync resolveGatewayProbeAuthSafe path in status.gateway-probe.ts, which cannot expand SecretRef objects. Switched to async resolveGatewayProbeAuthSafeWithSecretInputs. 2. (P2) status-all.ts was eagerly resolving both local and remote probe auth before deciding which to use. A stale SecretRef in the unused branch could abort the command. Collapsed to a single resolution call using the correct mode upfront. Updated status.scan.test.ts to use mockResolvedValue since resolveGatewayProbeAuthResolution is now async. * fix(status): await resolveGatewayProbeAuthResolution in scan.shared Function is now async after switching to resolveGatewayProbeAuthSafeWithSecretInputs. Missing await caused TS error: Property 'auth' does not exist on type 'Promise<...>'. * fix: finish gateway probe auth landing (openclaw#52513) (thanks @CodeForgeNet) * fix: finish gateway probe auth landing (openclaw#52513) (thanks @CodeForgeNet) * test: clear msteams gate drift for gateway probe auth landing (openclaw#52513) (thanks @CodeForgeNet) * fix(exec): return plain-text tool result on failure instead of raw JSON When an exec command fails (e.g. timeout), the tool previously rejected with an Error, which the tool adapter caught and wrapped in a JSON object ({ status, tool, error }). The model then received this raw JSON as the tool result and could parrot it verbatim to the user. Now exec failures resolve with a proper tool result containing the error as human-readable text in content[], matching the success path structure. The model sees plain text it can naturally incorporate into its reply. Also fixes a pre-existing format issue in update-cli.test.ts. Fixes openclaw#52484 Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * fix: finish exec tool failure landing (openclaw#52508) (thanks @martingarramon) * fix(openshell): bundle upstream cli fallback * perf(reply): lazy-load session store writes * fix(build): restore plugin-sdk and line compat after refactor * refactor(kilocode): route shared model constants through core seam * refactor(plugin-sdk): route core provider and telegram seams through sdk barrels * fix(acp): preserve hidden thought chunks from gateway chat * fix(docs): rename 'Channel Options' to 'Options' in sdk-entrypoints This heading labels definePluginEntry options (generic, not channel-specific). Another agent reverted the previous fix during a merge. * fix(line): narrow plugin-sdk seams after refactor * test(voice-call): cover helper utilities * test(voice-call): cover manager and api helpers * fix(acp): preserve hidden thought replay on session load * test(voice-call): cover twilio and reaper helpers * docs(changelog): note ACP hidden thought replay fix * test(voice-call): cover utility and tailscale helpers * fix(ci): resync generated baselines and line runtime seam * fix(docs): remove duplicate '### Options' headings (MD024) * fix(ci): restore plugin manifests and boundary tests * style(docs): format sdk entrypoints doc * docs(config): refresh generated baseline * test(voice-call): cover outbound call flow helpers * fix(ci): repair tts and matrix refactor fallout * fix(ci): repair voice-call typing and provider contracts * fix(ci): satisfy voice-call typing and extension boundaries * Remove personal references from docs (openclaw#25260) * docs: remove personal references from AGENTS.md * docs: remove personal reference from sag skill * docs: note generic agent guidance cleanup * Update CHANGELOG.md --------- Co-authored-by: Josh Lehman <[email protected]> Co-authored-by: Vincent Koc <[email protected]> * fix(plugins): route keyed queue imports through core (openclaw#52608) * fix(matrix): preserve send aliases and voice intent * fix(build): repair stale plugin sdk surfaces * fix(plugin-sdk): export line runtime subpath * fix(auth): route copilot login through sdk seam * feat(web-search): add bundled Exa plugin (openclaw#52617) * test(msteams): await async setup status lines * fix(whatsapp): remove outbound runtime cycle * fix(plugin-sdk): fast-path root diagnostic subscriptions * fix(exa): align freshness typing and config docs * fix(matrix): avoid touching dropped room bindings * fix(web-search): align Exa plugin with current API * docs(tools): add DuckDuckGo Search provider page New page: tools/duckduckgo-search.md - Key-free fallback provider, no API key needed - Clear Warning about unofficial HTML-based integration - Limitations section covering bot-challenge risk and reliability - CardGroup showing good-for vs not-recommended-for use cases Updated: tools/web.md with DuckDuckGo in CardGroup and comparison table Updated: docs.json nav and redirect * test(telegram): align webhook grammy mock * docs(tools): add Exa Search page, align all search provider docs New page: tools/exa-search.md - Neural/keyword/hybrid search modes with content extraction - Tool parameters including contents (highlights, text, summary) - Search mode reference table Rewritten: tools/duckduckgo-search.md - Aligned to consistent template (Setup, Config, Tool parameters, Notes, Related) - Simplified from previous version Aligned across all providers: - Every search page now ends with a consistent ## Related section - Replaced 'See [Web tools]' with proper Related links - Added Exa + DuckDuckGo to web.md overview CardGroup and comparison table - Added Exa to docs.json nav and redirects * fix(telegram): inject media loader through bot deps * fix(ci): harden telegram seams and cap job timeouts * docs(tools): update Exa Search notes for current API behavior Add notes about default highlights contents, highlightScores/summary preservation from responses, description resolution order, and 100-result cap. * perf: add vitest test perf workflows * fix(ci): harden changed extension diff fallback * fix(telegram): harden grammy seams across tests * refactor: extract exec outcome and tool result helpers * test: isolate exec foreground failure coverage * fix(test): allow empty extension lane * perf: enable vitest fs module cache by default * fix(cli): route plugin logs to stderr during --json output * fix(cli): route deferred plugin logs to stderr in status --json * fix: keep status --json stdout clean (openclaw#52449) (thanks @cgdusek) * refactor(ci): collapse fast setup jobs into preflight * fix(exec): accept runtime failure kind in formatter * fix: include .env file vars in gateway service environment on install When building the gateway install plan, read and parse ~/.openclaw/.env (or $OPENCLAW_STATE_DIR/.env) and merge those key-value pairs into the service environment at the lowest priority — below config env vars, auth-profile refs, and the core service environment (HOME, PATH, OPENCLAW_*). This ensures that user-defined secrets stored in .env (e.g. BRAVE_API_KEY, OPENROUTER_API_KEY, DISCORD_BOT_TOKEN) are embedded in the LaunchAgent plist (macOS), systemd unit (Linux), and Scheduled Task (Windows) at install time, rather than relying solely on the gateway process loading them via dotenv.config() at startup. Previously, on macOS the LaunchAgent plist never included .env vars, which meant: - launchctl print did not show user secrets (hard to debug) - Child processes spawned before dotenv loaded had no access - If the same key existed in both .env and the plist, the stale plist value won via dotenv override:false semantics Dangerous host env vars (NODE_OPTIONS, LD_PRELOAD, etc.) are filtered using the same security policy applied to config env vars. Fixes openclaw#37101 Relates to openclaw#22663 * fix: normalize env var keys and isolate tests from real .env - Apply normalizeEnvVarKey({ portable: true }) before security filtering, matching the established pattern in env-vars.ts. Rejects non-portable key names (spaces, special chars) that would produce invalid plist/systemd syntax. - Isolate existing tests from the developer's real ~/.openclaw/.env by providing a temp HOME directory, preventing flaky failures when the test machine has a populated .env file. * fix: narrow exec exit failure kind typing * fix(test): isolate flaky extension lanes * feat(web-search): add DuckDuckGo bundled plugin (openclaw#52629) * feat(web-search): add DuckDuckGo bundled plugin * chore(changelog): restore main changelog * fix(web-search): harden DuckDuckGo challenge detection * refactor: split durable service env helpers * refactor: extract gateway install token helpers * fix(web-search): mark DuckDuckGo experimental * docs(tools): update DuckDuckGo Search for landed plugin code - Mark as experimental (not just unofficial) - Add region and safeSearch tool parameters (from DDG schema) - Add plugin config example for region/safeSearch defaults - Document auto-detection order (100 = last) - Note SafeSearch defaults to moderate - Verified against extensions/duckduckgo/src/ * fix(agents): deny local MEDIA paths for MCP results * Usage: include reset and deleted session archives (openclaw#43215) Merged via squash. Prepared head SHA: 49ed6c2 Co-authored-by: rcrick <[email protected]> Co-authored-by: frankekn <[email protected]> Reviewed-by: @frankekn * docs(tools): soften DDG wording (scrapes -> pulls/gathers) * fix(build): add stable memory-cli dist entry (openclaw#51759) Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: Frank <[email protected]> * refactor!: drop legacy CLAWDBOT env compatibility * refactor!: remove moltbot state-dir migration fallback * fix(gateway): preserve async hook ingress provenance * fix(ci): write dist build stamp after builds * perf: trim vitest hot imports and refresh manifests * fix(security): unwrap time dispatch wrappers * fix(plugin-sdk): fall back to src root alias files * fix(ci): skip docs-only preflight pnpm audit * docs(changelog): note time exec approval fix * docs: refresh plugin-sdk api baseline * fix(runtime): make dist-runtime staging idempotent * fix(media): bound remote error-body snippet reads * fix(gateway): gate internal command persistence mutations * fix: restrict remote marketplace plugin sources * fix(runtime): skip peer resolution for bundled plugin deps * docs(agents): prefer current test model examples * fix(exec): escape invisible approval filler chars * test(models): refresh example model fixtures * fix(security): unify dispatch wrapper approval hardening * fix(security): harden explicit-proxy SSRF pinning * fix: gate synology chat reply name matching * docs: clarify sessions_spawn ACP vs subagent policies * refactor(exec): split wrapper resolution modules * refactor(exec): make dispatch wrapper semantics spec-driven * refactor(exec): share wrapper trust planning * refactor(exec): rename wrapper plans for trust semantics * fix: include .npmrc in onboard docker build * test: trim docker live auth mounts * Docs: refresh config baseline for Synology Chat * refactor: clarify synology delivery identity names * refactor: centralize synology dangerous name matching * refactor: narrow synology legacy name lookup * refactor: audit synology dangerous name matching * refactor: dedupe synology config schema * fix: normalize scoped vitest filter paths * fix(voice-call): harden webhook pre-auth guards * fix(synology-chat): fail closed shared webhook paths * docs: credit nexrin in synology changelog * test: fix base vitest thread regressions * test: finish base vitest thread fixture fixes * test(voice-call): accept oversize webhook socket resets * test: honor env auth in gateway live probes * fix: harden plugin docker e2e * Docs: align MiniMax examples with M2.7 * fix(ci): restore stale guardrails and baselines * Test: isolate qr dashboard integration suite * Gateway: resolve fallback plugin context lazily * fix: bind bootstrap setup codes to node profile * fix(tlon): unify settings reconciliation semantics * refactor(synology-chat): type startup webhook path policy * docs(synology-chat): clarify multi-account webhook paths * refactor: unify minimax model and failover live policies * docs: sync minimax m2.7 references * fix: harden Windows Parallels smoke installs * docs: reorder unreleased changelog by user impact * refactor: remove embedded runner cwd mutation * Infra: support shell carrier allow-always approvals * refactor: centralize bootstrap profile handling * refactor: reuse canonical setup bootstrap profile * fix(plugin-sdk): resolve hashed diagnostic events chunks * fix(plugin-sdk): normalize hashed diagnostic event exports * test: fix ci env-sensitive assertions * fix(gateway): fail closed on unresolved discovery endpoints * feat: add slash plugin installs * fix(media): block remote-host file URLs in loaders * fix(media): harden secondary local path seams * test: harden no-isolate reply teardown * docs(changelog): add Windows media security fix * refactor(gateway): centralize discovery target handling * test: narrow live transcript scaffolding strip * test: fix ci docs drift and bun qr exit handling * fix(browser): enforce node browser proxy allowProfiles * refactor(media): share local file access guards * test: stabilize ci test harnesses * test: harden no-isolate test module resets * fix(plugins): preserve live hook registry during gateway runs * test: fix channel summary registry setup * test: harden isolated test mocks * chore(plugins): remove opik investigation checkpoints * ACPX: align pinned runtime version (openclaw#52730) * ACPX: align pinned runtime version * ACPX: drop version example from help text * test: stop leaking image workspace temp dirs * fix(android): gate canvas bridge to trusted pages (openclaw#52722) * fix(android): gate canvas bridge to trusted pages * fix(changelog): note android canvas bridge gating * Update apps/android/app/src/main/java/ai/openclaw/app/node/CanvasActionTrust.kt Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * fix(android): snapshot canvas URL on UI thread --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * test: isolate base vitest thread blockers * fix: sync agent and autoreply e2e updates * test: harden no-isolate mocked module resets * docs: reorder unreleased changelog * fix(changelog): note windows media path guardrails (openclaw#52738) * fix: alphabetize web search provider listings * docs: clarify unreleased breaking changes * test: harden ci isolated mocks * fix: align websocket stream fallback types * test: finish no-isolate suite hardening * style: format image-generation runtime tests * fix(memory-core): register memory tools independently to prevent coupled failure (openclaw#52668) Merged via admin squash because current required CI failures are inherited from base and match latest `main` failures outside this PR's `memory-core` surface. Prepared head SHA: df7f968 Co-authored-by: artwalker <[email protected]> Reviewed-by: @frankekn * fix(status): recompute fallback context window (openclaw#51795) * fix(status): recompute fallback context window * fix(status): keep live context token caps on fallback * fix(status): preserve fallback runtime context windows * fix(status): preserve configured fallback context caps * fix(status): keep provider-aware transcript context lookups * fix(status): preserve explicit fallback context caps * fix(status): clamp fallback configured context caps * fix(status): keep raw runtime slash ids * fix(status): refresh plugin-sdk api baseline * fix(status): preserve fallback context lookup * test(status): refresh plugin-sdk api baseline * fix(status): keep runtime slash-id context lookup --------- Co-authored-by: create <[email protected]> Co-authored-by: Frank Yang <[email protected]> Co-authored-by: RichardCao <[email protected]> * fix(telegram): make buttons schema optional in message tool The Telegram plugin injects a `buttons` property into the message tool schema via `createMessageToolButtonsSchema()`, but without wrapping it in `Type.Optional()`. This causes TypeBox to include `buttons` in the JSON Schema `required` array. In isolated sessions (e.g. cron jobs) where no `currentChannel` is set, all plugin schemas are merged into the message tool. When the LLM calls the message tool without a `buttons` parameter, AJV validation fails with: `buttons: must have required property 'buttons'`. Wrap the buttons schema in `Type.Optional()` so it is not required. * fix: keep message-tool buttons optional for Telegram and Mattermost (openclaw#52589) (thanks @tylerliu612) * test: update codex test fixtures to gpt-5.4 * fix: repair runtime seams after rebase * fix: restore Telegram topic announce delivery (openclaw#51688) (thanks @mvanhorn) When `replyLike.text` or `replyLike.caption` is an unexpected non-string value (edge case from some Telegram API responses), the reply body was coerced to "[object Object]" via string concatenation. Add a `typeof === "string"` guard to gracefully fall back to empty string, matching the existing pattern used for `quoteText` in the same function. Co-authored-by: Penchan <[email protected]> * docs: sync generated release baselines * test: isolate pi embedded model thread fixtures * fix: restore provider runtime lazy boundary * fix: preserve Telegram reply context text (openclaw#50500) (thanks @p3nchan) * fix: guard Telegram reply context text (openclaw#50500) (thanks @p3nchan) * fix: preserve Telegram reply caption fallback (openclaw#50500) (thanks @p3nchan) --------- Co-authored-by: Ayaan Zaidi <[email protected]> * fix: harden gateway SIGTERM shutdown (openclaw#51242) (thanks @juliabush) * fix: increase shutdown timeout to avoid SIGTERM hang * fix(telegram): abort polling fetch on shutdown to prevent SIGTERM hang * fix(gateway): enforce hard exit on shutdown timeout for SIGTERM * fix: tighten gateway shutdown watchdog * fix: harden gateway SIGTERM shutdown (openclaw#51242) (thanks @juliabush) --------- Co-authored-by: Ayaan Zaidi <[email protected]> * build: prepare 2026.3.22-beta.1 * fix: restore provider runtime lazy boundary * test: add parallels npm update smoke * test: split pi embedded model thread fixtures * fix: stop browser server tests from launching real chrome * test: stabilize live provider docker probes * fix: restart windows gateway after npm update * test: isolate server-context browser harness imports * test: inject model runtime hooks for thread-safe tests * test: snapshot ci timeout investigation * test: target gemini 3.1 flash alias * test: stabilize trigger handling and hook e2e tests * build: prepare 2026.3.22 * test: harden channel suite isolation * test: inject thread-safe deps for agent tools * test: raise timeout for slow provider auth normalization * ci: stabilize windows and bun unit lanes * test: inject thread-safe gateway and ACP seams * test: isolate pi model and reset-model thread fixtures * build: prepare 2026.3.23 * test: inject image-tool provider deps for raw threads * test: stabilize e2e module isolation * test: decouple vitest config checks from ambient env * fix: harden parallels smoke agent invocation * test: avoid repo-root perf profile artifacts * test: inject thread-safe base seams * fix: document Telegram asDocument alias (openclaw#52461) (thanks @bakhtiersizhaev) * feat(telegram): add asDocument param to message tool Adds `asDocument` as a user-facing alias for the existing `forceDocument` parameter in the message tool. When set to `true`, media files (images, videos, GIFs) are sent via `sendDocument` instead of `sendPhoto`/ `sendVideo`/`sendAnimation`, preserving the original file quality without Telegram compression. This is useful when agents need to deliver high-resolution images or uncompressed files to users via Telegram. `asDocument` is intentionally an alias rather than a replacement — the existing `forceDocument` continues to work unchanged. Changes: - src/agents/tools/message-tool.ts: add asDocument to send schema - src/agents/tools/telegram-actions.ts: OR asDocument into forceDocument - src/infra/outbound/message-action-runner.ts: same OR logic for outbound path - extensions/telegram/src/channel-actions.ts: read and forward asDocument - src/channels/plugins/actions/actions.test.ts: add test case * fix: restore channel-actions.ts to main version (rebase conflict fix) * fix(test): match asDocument test payload to actual params structure * fix(telegram): preserve forceDocument alias semantics * fix: document Telegram asDocument alias (openclaw#52461) (thanks @bakhtiersizhaev) --------- Co-authored-by: Бахтиер Сижаев <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> * fix: refactor deepseek bundled plugin (openclaw#48762) (thanks @07akioni) * fix: declare typebox runtime dep for mattermost plugin * test: reset line webhook mocks between cases * test: split attempt spawn-workspace thread fixtures * test: remove replaced spawn-workspace monolith * refactor: isolate attempt context engine thread helpers * CI: remove npm release preview workflow (openclaw#52825) * CI: remove npm release preview workflow * Docs: align release maintainer skill with manual publish * Docs: expand release maintainer skill flow * test: stabilize gateway thread harness * test: fix status plugin pagination expectation * test: harden channel suite isolation * build: sync lockfile for mattermost plugin * fix: ensure env proxy dispatcher before MiniMax and OpenAI Codex OAuth flows (openclaw#52228) Verified: - pnpm install --frozen-lockfile - NPM_CONFIG_CACHE=/tmp/openclaw-npm-cache-52228 pnpm build - pnpm check - pnpm test:macmini (failed on inherited pre-existing plugin contract test: src/plugins/contracts/registry.contract.test.ts missing deepseek in bundled provider contract registry outside this PR surface) Co-authored-by: openperf <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> * fix: restore ci gates * test: stabilize channel ci gate * docs: refresh generated config baseline * release: verify control-ui assets are included in npm tarball * release-check: include stderr/stdout when npm pack fails * release: add changelog for control UI tarball check * fix: keep session transcript pointers fresh after compaction (openclaw#50688) Co-authored-by: Frank Yang <[email protected]> * fix(msteams): isolate probe test env credentials * release: automate macOS publishing (openclaw#52853) * release: automate macOS publishing * release: keep mac appcast in openclaw repo * release: add preflight-only release workflow runs * release: keep appcast updates manual * release: generate signed appcast as workflow artifact * release: require preflight before publish * release: require mac app for every release * docs: clarify every release ships mac app * release: document Sparkle feed and SHA rules * release: keep publish flow tag-based * release: stabilize mac appcast flow * release: document local mac fallback * Update CHANGELOG.md * Improve PR template regression prompts * fix(agents): preserve anthropic thinking block order (openclaw#52961) * fix(release): ship bundled plugins in pack artifacts * fix(config): keep built-in channels out of plugin allowlists (openclaw#52964) * fix(config): keep built-in channels out of plugin allowlists * docs(changelog): note doctor whatsapp allowlist fix * docs(changelog): move doctor whatsapp fix to top * Update CHANGELOG.md * fix(config): keep built-in auto-enable idempotent * fix(release): preserve shipped channel surfaces in npm tar (openclaw#52913) * fix(channels): ship official channel catalog (openclaw#52838) * fix(release): keep shipped bundles in npm tar (openclaw#52838) * build(release): fix rebased release-check helpers (openclaw#52838) * fix(gateway): harden supervised lock and browser attach readiness * fix(matrix): avoid duplicate runtime api exports * fix(gateway): avoid probe false negatives after connect * docs(changelog): note release and matrix fixes * fix(plugins): unblock Discord/Slack message tool sends and Feishu media (openclaw#52991) * fix(plugins): unblock Discord and Slack message tool payloads * docs(changelog): note Discord Slack and Feishu message fixes * fix(channels): preserve external catalog overrides (openclaw#52988) * fix(channels): preserve external catalog overrides * fix(channels): clarify catalog precedence * fix(channels): respect overridden install specs * fix(gateway): require admin for agent session reset * fix(voice-call): stabilize plivo v2 replay keys * fix(gateway): require auth for canvas routes * feat(context-pruning): cache media to disk during pruning instead of stripping When cacheMedia is enabled, pruned image blocks are saved to ~/.openclaw/media/cache/ and replaced with a file path reference so the agent can re-read them on demand. Includes TTL cleanup and session-scoped cache management. * feat(media): add media cache module for context pruning * feat(whatsapp): make block streaming configurable instead of hardcoded off --------- Co-authored-by: Vincent Koc <[email protected]> Co-authored-by: CodeForgeNet <[email protected]> Co-authored-by: Peter Steinberger <[email protected]> Co-authored-by: Martin Garramon <[email protected]> Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]> Co-authored-by: François Martin <[email protected]> Co-authored-by: Josh Lehman <[email protected]> Co-authored-by: Charles Dusek <[email protected]> Co-authored-by: Kevin ONeill <[email protected]> Co-authored-by: Rick_Xu <[email protected]> Co-authored-by: rcrick <[email protected]> Co-authored-by: frankekn <[email protected]> Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: Frank <[email protected]> Co-authored-by: scoootscooob <[email protected]> Co-authored-by: ruochen <[email protected]> Co-authored-by: Onur Solmaz <[email protected]> Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> Co-authored-by: Frank Yang <[email protected]> Co-authored-by: artwalker <[email protected]> Co-authored-by: RichardCao <[email protected]> Co-authored-by: create <[email protected]> Co-authored-by: RichardCao <[email protected]> Co-authored-by: liuyang <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> Co-authored-by: Matt Van Horn <[email protected]> Co-authored-by: Penchan <[email protected]> Co-authored-by: Penchan <[email protected]> Co-authored-by: Julia Bush <[email protected]> Co-authored-by: Bakhtier Sizhaev <[email protected]> Co-authored-by: Бахтиер Сижаев <[email protected]> Co-authored-by: wangchunyue <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> Co-authored-by: evann <[email protected]> Co-authored-by: Robin Waslander <[email protected]> Co-authored-by: Sathvik Veerapaneni <[email protected]> Co-authored-by: Nimrod Gutman <[email protected]>

@frankekn

…claw#105) * fix(web-search): mark DuckDuckGo experimental * docs(tools): update DuckDuckGo Search for landed plugin code - Mark as experimental (not just unofficial) - Add region and safeSearch tool parameters (from DDG schema) - Add plugin config example for region/safeSearch defaults - Document auto-detection order (100 = last) - Note SafeSearch defaults to moderate - Verified against extensions/duckduckgo/src/ * fix(agents): deny local MEDIA paths for MCP results * Usage: include reset and deleted session archives (openclaw#43215) Merged via squash. Prepared head SHA: 49ed6c2 Co-authored-by: rcrick <[email protected]> Co-authored-by: frankekn <[email protected]> Reviewed-by: @frankekn * docs(tools): soften DDG wording (scrapes -> pulls/gathers) * fix(build): add stable memory-cli dist entry (openclaw#51759) Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: Frank <[email protected]> * refactor!: drop legacy CLAWDBOT env compatibility * refactor!: remove moltbot state-dir migration fallback * fix(gateway): preserve async hook ingress provenance * fix(ci): write dist build stamp after builds * perf: trim vitest hot imports and refresh manifests * fix(security): unwrap time dispatch wrappers * fix(plugin-sdk): fall back to src root alias files * fix(ci): skip docs-only preflight pnpm audit * docs(changelog): note time exec approval fix * docs: refresh plugin-sdk api baseline * fix(runtime): make dist-runtime staging idempotent * fix(media): bound remote error-body snippet reads * fix(gateway): gate internal command persistence mutations * fix: restrict remote marketplace plugin sources * fix(runtime): skip peer resolution for bundled plugin deps * docs(agents): prefer current test model examples * fix(exec): escape invisible approval filler chars * test(models): refresh example model fixtures * fix(security): unify dispatch wrapper approval hardening * fix(security): harden explicit-proxy SSRF pinning * fix: gate synology chat reply name matching * docs: clarify sessions_spawn ACP vs subagent policies * refactor(exec): split wrapper resolution modules * refactor(exec): make dispatch wrapper semantics spec-driven * refactor(exec): share wrapper trust planning * refactor(exec): rename wrapper plans for trust semantics * fix: include .npmrc in onboard docker build * test: trim docker live auth mounts * Docs: refresh config baseline for Synology Chat * refactor: clarify synology delivery identity names * refactor: centralize synology dangerous name matching * refactor: narrow synology legacy name lookup * refactor: audit synology dangerous name matching * refactor: dedupe synology config schema * fix: normalize scoped vitest filter paths * fix(voice-call): harden webhook pre-auth guards * fix(synology-chat): fail closed shared webhook paths * docs: credit nexrin in synology changelog * test: fix base vitest thread regressions * test: finish base vitest thread fixture fixes * test(voice-call): accept oversize webhook socket resets * test: honor env auth in gateway live probes * fix: harden plugin docker e2e * Docs: align MiniMax examples with M2.7 * fix(ci): restore stale guardrails and baselines * Test: isolate qr dashboard integration suite * Gateway: resolve fallback plugin context lazily * fix: bind bootstrap setup codes to node profile * fix(tlon): unify settings reconciliation semantics * refactor(synology-chat): type startup webhook path policy * docs(synology-chat): clarify multi-account webhook paths * refactor: unify minimax model and failover live policies * docs: sync minimax m2.7 references * fix: harden Windows Parallels smoke installs * docs: reorder unreleased changelog by user impact * refactor: remove embedded runner cwd mutation * Infra: support shell carrier allow-always approvals * refactor: centralize bootstrap profile handling * refactor: reuse canonical setup bootstrap profile * fix(plugin-sdk): resolve hashed diagnostic events chunks * fix(plugin-sdk): normalize hashed diagnostic event exports * test: fix ci env-sensitive assertions * fix(gateway): fail closed on unresolved discovery endpoints * feat: add slash plugin installs * fix(media): block remote-host file URLs in loaders * fix(media): harden secondary local path seams * test: harden no-isolate reply teardown * docs(changelog): add Windows media security fix * refactor(gateway): centralize discovery target handling * test: narrow live transcript scaffolding strip * test: fix ci docs drift and bun qr exit handling * fix(browser): enforce node browser proxy allowProfiles * refactor(media): share local file access guards * test: stabilize ci test harnesses * test: harden no-isolate test module resets * fix(plugins): preserve live hook registry during gateway runs * test: fix channel summary registry setup * test: harden isolated test mocks * chore(plugins): remove opik investigation checkpoints * ACPX: align pinned runtime version (openclaw#52730) * ACPX: align pinned runtime version * ACPX: drop version example from help text * test: stop leaking image workspace temp dirs * fix(android): gate canvas bridge to trusted pages (openclaw#52722) * fix(android): gate canvas bridge to trusted pages * fix(changelog): note android canvas bridge gating * Update apps/android/app/src/main/java/ai/openclaw/app/node/CanvasActionTrust.kt Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * fix(android): snapshot canvas URL on UI thread --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * test: isolate base vitest thread blockers * fix: sync agent and autoreply e2e updates * test: harden no-isolate mocked module resets * docs: reorder unreleased changelog * fix(changelog): note windows media path guardrails (openclaw#52738) * fix: alphabetize web search provider listings * docs: clarify unreleased breaking changes * test: harden ci isolated mocks * fix: align websocket stream fallback types * test: finish no-isolate suite hardening * style: format image-generation runtime tests * fix(memory-core): register memory tools independently to prevent coupled failure (openclaw#52668) Merged via admin squash because current required CI failures are inherited from base and match latest `main` failures outside this PR's `memory-core` surface. Prepared head SHA: df7f968 Co-authored-by: artwalker <[email protected]> Reviewed-by: @frankekn * fix(status): recompute fallback context window (openclaw#51795) * fix(status): recompute fallback context window * fix(status): keep live context token caps on fallback * fix(status): preserve fallback runtime context windows * fix(status): preserve configured fallback context caps * fix(status): keep provider-aware transcript context lookups * fix(status): preserve explicit fallback context caps * fix(status): clamp fallback configured context caps * fix(status): keep raw runtime slash ids * fix(status): refresh plugin-sdk api baseline * fix(status): preserve fallback context lookup * test(status): refresh plugin-sdk api baseline * fix(status): keep runtime slash-id context lookup --------- Co-authored-by: create <[email protected]> Co-authored-by: Frank Yang <[email protected]> Co-authored-by: RichardCao <[email protected]> * fix(telegram): make buttons schema optional in message tool The Telegram plugin injects a `buttons` property into the message tool schema via `createMessageToolButtonsSchema()`, but without wrapping it in `Type.Optional()`. This causes TypeBox to include `buttons` in the JSON Schema `required` array. In isolated sessions (e.g. cron jobs) where no `currentChannel` is set, all plugin schemas are merged into the message tool. When the LLM calls the message tool without a `buttons` parameter, AJV validation fails with: `buttons: must have required property 'buttons'`. Wrap the buttons schema in `Type.Optional()` so it is not required. * fix: keep message-tool buttons optional for Telegram and Mattermost (openclaw#52589) (thanks @tylerliu612) * test: update codex test fixtures to gpt-5.4 * fix: repair runtime seams after rebase * fix: restore Telegram topic announce delivery (openclaw#51688) (thanks @mvanhorn) When `replyLike.text` or `replyLike.caption` is an unexpected non-string value (edge case from some Telegram API responses), the reply body was coerced to "[object Object]" via string concatenation. Add a `typeof === "string"` guard to gracefully fall back to empty string, matching the existing pattern used for `quoteText` in the same function. Co-authored-by: Penchan <[email protected]> * docs: sync generated release baselines * test: isolate pi embedded model thread fixtures * fix: restore provider runtime lazy boundary * fix: preserve Telegram reply context text (openclaw#50500) (thanks @p3nchan) * fix: guard Telegram reply context text (openclaw#50500) (thanks @p3nchan) * fix: preserve Telegram reply caption fallback (openclaw#50500) (thanks @p3nchan) --------- Co-authored-by: Ayaan Zaidi <[email protected]> * fix: harden gateway SIGTERM shutdown (openclaw#51242) (thanks @juliabush) * fix: increase shutdown timeout to avoid SIGTERM hang * fix(telegram): abort polling fetch on shutdown to prevent SIGTERM hang * fix(gateway): enforce hard exit on shutdown timeout for SIGTERM * fix: tighten gateway shutdown watchdog * fix: harden gateway SIGTERM shutdown (openclaw#51242) (thanks @juliabush) --------- Co-authored-by: Ayaan Zaidi <[email protected]> * build: prepare 2026.3.22-beta.1 * fix: restore provider runtime lazy boundary * test: add parallels npm update smoke * test: split pi embedded model thread fixtures * fix: stop browser server tests from launching real chrome * test: stabilize live provider docker probes * fix: restart windows gateway after npm update * test: isolate server-context browser harness imports * test: inject model runtime hooks for thread-safe tests * test: snapshot ci timeout investigation * test: target gemini 3.1 flash alias * test: stabilize trigger handling and hook e2e tests * build: prepare 2026.3.22 * test: harden channel suite isolation * test: inject thread-safe deps for agent tools * test: raise timeout for slow provider auth normalization * ci: stabilize windows and bun unit lanes * test: inject thread-safe gateway and ACP seams * test: isolate pi model and reset-model thread fixtures * build: prepare 2026.3.23 * test: inject image-tool provider deps for raw threads * test: stabilize e2e module isolation * test: decouple vitest config checks from ambient env * fix: harden parallels smoke agent invocation * test: avoid repo-root perf profile artifacts * test: inject thread-safe base seams * fix: document Telegram asDocument alias (openclaw#52461) (thanks @bakhtiersizhaev) * feat(telegram): add asDocument param to message tool Adds `asDocument` as a user-facing alias for the existing `forceDocument` parameter in the message tool. When set to `true`, media files (images, videos, GIFs) are sent via `sendDocument` instead of `sendPhoto`/ `sendVideo`/`sendAnimation`, preserving the original file quality without Telegram compression. This is useful when agents need to deliver high-resolution images or uncompressed files to users via Telegram. `asDocument` is intentionally an alias rather than a replacement — the existing `forceDocument` continues to work unchanged. Changes: - src/agents/tools/message-tool.ts: add asDocument to send schema - src/agents/tools/telegram-actions.ts: OR asDocument into forceDocument - src/infra/outbound/message-action-runner.ts: same OR logic for outbound path - extensions/telegram/src/channel-actions.ts: read and forward asDocument - src/channels/plugins/actions/actions.test.ts: add test case * fix: restore channel-actions.ts to main version (rebase conflict fix) * fix(test): match asDocument test payload to actual params structure * fix(telegram): preserve forceDocument alias semantics * fix: document Telegram asDocument alias (openclaw#52461) (thanks @bakhtiersizhaev) --------- Co-authored-by: Бахтиер Сижаев <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> * fix: refactor deepseek bundled plugin (openclaw#48762) (thanks @07akioni) * fix: declare typebox runtime dep for mattermost plugin * test: reset line webhook mocks between cases * test: split attempt spawn-workspace thread fixtures * test: remove replaced spawn-workspace monolith * refactor: isolate attempt context engine thread helpers * CI: remove npm release preview workflow (openclaw#52825) * CI: remove npm release preview workflow * Docs: align release maintainer skill with manual publish * Docs: expand release maintainer skill flow * test: stabilize gateway thread harness * test: fix status plugin pagination expectation * test: harden channel suite isolation * build: sync lockfile for mattermost plugin * fix: ensure env proxy dispatcher before MiniMax and OpenAI Codex OAuth flows (openclaw#52228) Verified: - pnpm install --frozen-lockfile - NPM_CONFIG_CACHE=/tmp/openclaw-npm-cache-52228 pnpm build - pnpm check - pnpm test:macmini (failed on inherited pre-existing plugin contract test: src/plugins/contracts/registry.contract.test.ts missing deepseek in bundled provider contract registry outside this PR surface) Co-authored-by: openperf <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> * fix: restore ci gates * test: stabilize channel ci gate * docs: refresh generated config baseline * release: verify control-ui assets are included in npm tarball * release-check: include stderr/stdout when npm pack fails * release: add changelog for control UI tarball check * fix: keep session transcript pointers fresh after compaction (openclaw#50688) Co-authored-by: Frank Yang <[email protected]> * fix(msteams): isolate probe test env credentials * release: automate macOS publishing (openclaw#52853) * release: automate macOS publishing * release: keep mac appcast in openclaw repo * release: add preflight-only release workflow runs * release: keep appcast updates manual * release: generate signed appcast as workflow artifact * release: require preflight before publish * release: require mac app for every release * docs: clarify every release ships mac app * release: document Sparkle feed and SHA rules * release: keep publish flow tag-based * release: stabilize mac appcast flow * release: document local mac fallback * Update CHANGELOG.md * Improve PR template regression prompts * fix(agents): preserve anthropic thinking block order (openclaw#52961) * fix(release): ship bundled plugins in pack artifacts * fix(config): keep built-in channels out of plugin allowlists (openclaw#52964) * fix(config): keep built-in channels out of plugin allowlists * docs(changelog): note doctor whatsapp allowlist fix * docs(changelog): move doctor whatsapp fix to top * Update CHANGELOG.md * fix(config): keep built-in auto-enable idempotent * fix(release): preserve shipped channel surfaces in npm tar (openclaw#52913) * fix(channels): ship official channel catalog (openclaw#52838) * fix(release): keep shipped bundles in npm tar (openclaw#52838) * build(release): fix rebased release-check helpers (openclaw#52838) * fix(gateway): harden supervised lock and browser attach readiness * fix(matrix): avoid duplicate runtime api exports * fix(gateway): avoid probe false negatives after connect * docs(changelog): note release and matrix fixes * fix(plugins): unblock Discord/Slack message tool sends and Feishu media (openclaw#52991) * fix(plugins): unblock Discord and Slack message tool payloads * docs(changelog): note Discord Slack and Feishu message fixes * fix(channels): preserve external catalog overrides (openclaw#52988) * fix(channels): preserve external catalog overrides * fix(channels): clarify catalog precedence * fix(channels): respect overridden install specs * fix(gateway): require admin for agent session reset * fix(voice-call): stabilize plivo v2 replay keys * fix(gateway): require auth for canvas routes * fix(clawhub): resolve auth token for skill browsing (openclaw#53017) * fix(clawhub): resolve auth token for skill browsing * docs(changelog): note clawhub skill auth fix * fix(release): raise npm pack size budget * Tests: fix fresh-main regressions (openclaw#53011) * Tests: fix fresh-main regressions * Tests: avoid chat notice cache priming --------- Co-authored-by: Vincent Koc <[email protected]> * fix(config): ignore stale plugin allow entries * fix(browser): reuse running loopback browser after probe miss * fix(clawhub): honor macOS auth config path (openclaw#53034) * docs: fix nav ordering, missing pages, and stale model references - Sort providers alphabetically in docs.json nav - Sort channels alphabetically in docs.json nav (slack before synology-chat) - Add install/migrating-matrix to Maintenance nav section (was orphaned) - Remove zh-CN/plugins/architecture from nav (file does not exist) - Add Voice Call to channels index page - Add missing providers to providers index (DeepSeek, GitHub Copilot, OpenCode Go, Synthetic) - Sort providers index alphabetically - Update stale claude-3-5-sonnet model reference to claude-sonnet-4-6 in webhook docs * fix(clawhub): preserve XDG auth path on macOS * Agents: fix runtime web_search provider selection (openclaw#53020) Co-authored-by: Vincent Koc <[email protected]> * docs: fix CLI command tree, SDK import path, and tool group listing - Remove non-existent 'secrets migrate' from CLI command tree - Add actual secrets subcommands: audit, configure, apply - Add missing plugin subcommands: inspect, uninstall, update, marketplace list - Fix plugins info -> inspect (actual command name) - Add message send and broadcast subcommands to command tree - Remove misleading deprecated import from sdk-overview - Add sessions_yield and subagents to group:sessions tool group docs - Fix formatting * fix(gateway): guard openrouter auto pricing recursion (openclaw#53055) * test: refresh thread-safe agent fixtures * Release: fix npm release preflight under pnpm (openclaw#52985) Co-authored-by: Vincent Koc <[email protected]> * docs(changelog): add channel catalog override note (openclaw#52988) (openclaw#53059) * fix: harden update dev switch and refresh changelog * fix(mistral): repair max-token defaults and doctor migration (openclaw#53054) * fix(mistral): repair max-token defaults and doctor migration * fix(mistral): add missing small-model repair cap * fix(plugins): enable bundled Brave web search plugin by default (openclaw#52072) Brave is a bundled web search plugin but was missing from BUNDLED_ENABLED_BY_DEFAULT, causing it to be filtered out during provider resolution. This made web_search unavailable even when plugins.entries.brave.enabled was configured. Fixes openclaw#51937 Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Vincent Koc <[email protected]> * fix(release): fail empty control ui tarballs * Revert "fix(plugins): enable bundled Brave web search plugin by default (openclaw#52072)" This reverts commit 0ea3c4d. * Telegram: preserve inbound debounce order * Telegram: fix fire-and-forget debounce order * fix(reply): refresh followup drain callbacks * Update CHANGELOG.md * fix(reply): preserve no-debounce inbound concurrency * fix(reply): clear idle followup callbacks * fix(inbound): bound tracked debounce keys * fix: preserve debounce and followup ordering (openclaw#52998) (thanks @osolmaz) * fix(discord): reply on native command auth failures (openclaw#53072) * docs(changelog): add missing recent fixes * fix: bound tracked debounce key accounting * fix packaged control ui asset lookup (openclaw#53081) * fix(cli): preserve posix default git dir * build: prepare 2026.3.23-beta.1 * test: harden canvas host undici isolation * docs(changelog): credit web search runtime fix * fix(openai-codex): bootstrap proxy on oauth refresh (openclaw#53078) Verified: - pnpm install --frozen-lockfile - pnpm exec vitest run extensions/openai/openai-codex-provider.runtime.test.ts extensions/openai/openai-provider.test.ts * release: harden preflight workflows (openclaw#53087) * release: harden preflight-only workflows * release: require main for publish runs * release: select xcode for macos workflow * release: retry flaky macos preflight steps * ci: shard bun test lane * Fix Control UI operator.read scope handling (openclaw#53110) Preserve Control UI scopes through the device-auth bypass path, normalize implied operator device-auth scopes, ignore cached under-scoped operator tokens, and degrade read-backed main pages gracefully when a connection truly lacks operator.read. Co-authored-by: Val Alexander <[email protected]> * build: prepare 2026.3.23 * fix(agents): prefer runtime snapshot for skill secrets * docs(changelog): note skill secretref runtime fix * fix(memory): bootstrap lancedb runtime on demand (openclaw#53111) Bootstrap LanceDB into plugin runtime state on first use for packaged/global installs, keep @lancedb/lancedb plugin-local, and add regression coverage for bundled, cached, retry, and Nix fail-fast runtime paths. Co-authored-by: Val Alexander <[email protected]> * build: finalize 2026.3.23 release * release: upload macos preflight artifacts (openclaw#53105) * release: upload macos preflight artifacts * release: speed up macos preflight * release: use xlarge macos runner * release: skip dmg path in macos preflight * fix(subagents): recheck timed-out announce waits (openclaw#53127) Recheck timed-out subagent announce waits against the latest runtime snapshot before announcing timeout, and keep that recheck best-effort so transient gateway failures do not suppress the announcement. Co-authored-by: Val Alexander <[email protected]> * docs(feishu): replace botName with name in config examples (openclaw#52753) Merged via squash. Prepared head SHA: 5237726 Co-authored-by: haroldfabla2-hue <[email protected]> Co-authored-by: altaywtf <[email protected]> Reviewed-by: @altaywtf * fix(plugins): accept clawhub uninstall specs * test(auth): align device scope expectations (openclaw#53151) * fix: prevent delivery-mirror re-delivery and raise Slack chunk limit (openclaw#45489) Merged via squash. Prepared head SHA: c7664c7 Co-authored-by: theo674 <[email protected]> Co-authored-by: altaywtf <[email protected]> Reviewed-by: @altaywtf * Infra: tighten shell-wrapper positional-argv allowlist matching (openclaw#53133) * Infra: tighten shell carrier allowlist matching * fix(security): tighten shell carrier allowlist matcher * fix: generalize api_error detection for fallback model triggering (openclaw#49611) Co-authored-by: Ayush Ojha <[email protected]> Co-authored-by: altaywtf <[email protected]> * feat(modelstudio): add standard (pay-as-you-go) DashScope endpoints for Qwen (openclaw#43878) Add Standard API Key auth methods for China (dashscope.aliyuncs.com) and Global/Intl (dashscope-intl.aliyuncs.com) pay-as-you-go endpoints alongside the existing Coding Plan (subscription) endpoints. Also updates group label to 'Qwen (Alibaba Cloud Model Studio)' and fixes glm-4.7 -> glm-5 in Coding Plan note messages. Co-authored-by: wenmeng zhou <[email protected]> * Release: privatize macOS publish flow (openclaw#53166) * fix(diagnostics): redact credentials from cache-trace diagnostic output Refs openclaw#53103 * Release: document manual macOS asset upload (openclaw#53178) * Release: document manual macOS asset upload * Release: document macOS smoke-test mode * docs(changelog): reorder release highlights * test(whatsapp): stabilize login coverage in shared workers * test(whatsapp): preserve session exports in login coverage * test(whatsapp): preserve media test module exports * test(whatsapp): preserve harness session exports * fix(ci): stabilize whatsapp extension checks * test: make update-cli checkout path assertion platform-safe * fix(auth): prevent stale auth store reverts (openclaw#53211) * Doctor: prune stale plugin allowlist and entry refs (openclaw#53187) Signed-off-by: sallyom <[email protected]> * test: stabilize test isolation * test: update command coverage * test: expand gemini live transcript stripping * test: fix update-cli default path assertion * chore(sre:PLA-920): adopt upstream sync changes * fix(sre:PLA-920): align branch with adopted upstream tree * build(sre:PLA-920): refresh dist artifacts * test(sre:PLA-920): align incident-format expectations --------- Signed-off-by: sallyom <[email protected]> Co-authored-by: Vincent Koc <[email protected]> Co-authored-by: Peter Steinberger <[email protected]> Co-authored-by: Rick_Xu <[email protected]> Co-authored-by: rcrick <[email protected]> Co-authored-by: frankekn <[email protected]> Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: oliviareid-svg <[email protected]> Co-authored-by: Frank <[email protected]> Co-authored-by: scoootscooob <[email protected]> Co-authored-by: ruochen <[email protected]> Co-authored-by: Onur Solmaz <[email protected]> Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> Co-authored-by: Frank Yang <[email protected]> Co-authored-by: artwalker <[email protected]> Co-authored-by: RichardCao <[email protected]> Co-authored-by: create <[email protected]> Co-authored-by: RichardCao <[email protected]> Co-authored-by: liuyang <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> Co-authored-by: Matt Van Horn <[email protected]> Co-authored-by: Penchan <[email protected]> Co-authored-by: Penchan <[email protected]> Co-authored-by: Julia Bush <[email protected]> Co-authored-by: Bakhtier Sizhaev <[email protected]> Co-authored-by: Бахтиер Сижаев <[email protected]> Co-authored-by: wangchunyue <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> Co-authored-by: evann <[email protected]> Co-authored-by: Robin Waslander <[email protected]> Co-authored-by: Sathvik Veerapaneni <[email protected]> Co-authored-by: Nimrod Gutman <[email protected]> Co-authored-by: Luke <[email protected]> Co-authored-by: scoootscooob <[email protected]> Co-authored-by: Jamil Zakirov <[email protected]> Co-authored-by: TheRipper <[email protected]> Co-authored-by: Quinn H. <[email protected]> Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Val Alexander <[email protected]> Co-authored-by: betoblair <[email protected]> Co-authored-by: haroldfabla2-hue <[email protected]> Co-authored-by: altaywtf <[email protected]> Co-authored-by: Altay <[email protected]> Co-authored-by: theo674 <[email protected]> Co-authored-by: theo674 <[email protected]> Co-authored-by: Ayush Ojha <[email protected]> Co-authored-by: Ayush Ojha <[email protected]> Co-authored-by: George Zhang <[email protected]> Co-authored-by: wenmeng zhou <[email protected]> Co-authored-by: Onur <[email protected]> Co-authored-by: Sally O'Malley <[email protected]>

…h flows Operator1 adaptation of upstream 4e849ac: - extensions/minimax-portal-auth/oauth.ts: add proxy bootstrap before loginMiniMaxPortalOAuth (keep minimax-portal-auth SDK path, upstream renamed to provider-auth) - src/agents/minimax-vlm.ts: add proxy bootstrap before outbound VLM fetch - src/commands/openai-codex-oauth.ts: add proxy bootstrap before TLS preflight (operator1 equivalent of deleted src/plugins/provider-openai-codex-oauth.ts) - src/plugin-sdk/infra-runtime.ts: already exports undici-global-dispatcher from prior sync - CHANGELOG.md: entry already present from prior sync (cherry picked from commit 4e849ac, upstream openclaw#52228, fixes openclaw#51619, openclaw#51569)

openclaw-barnacle bot added agents Agent runtime and tooling extensions: minimax size: XS labels Mar 22, 2026

chatgpt-codex-connector bot reviewed Mar 22, 2026

View reviewed changes

src/plugins/provider-openai-codex-oauth.ts Outdated Show resolved Hide resolved

openperf mentioned this pull request Mar 22, 2026

[Bug]: mitmproxy integration broken - LLM ERROR #51619

Closed

Takhoffman self-assigned this Mar 23, 2026

openperf and others added 3 commits March 23, 2026 09:00

fix: ensure env proxy dispatcher before MiniMax and OpenAI Codex OAut…

2dfb5bd

…h flows (openclaw#51619, openclaw#51569)

fix: initialize proxy before OpenAI OAuth TLS preflight

732f21e

chore(changelog): note proxy oauth fix for openclaw#52228

764a2a1

Takhoffman force-pushed the fix/proxy-init-oauth branch from 18b79e6 to 764a2a1 Compare March 23, 2026 14:23

Takhoffman merged commit 4e849ac into openclaw:main Mar 23, 2026
26 of 34 checks passed

chatgpt-codex-connector bot reviewed Mar 23, 2026

View reviewed changes

Takhoffman mentioned this pull request Mar 23, 2026

fix(openai-codex): bootstrap proxy on oauth refresh #53078

Merged

25 tasks

neeravmakwana mentioned this pull request Mar 25, 2026

fix(memory): bootstrap proxy for LanceDB embeddings #54119

Merged

25 tasks

Uh oh!

Conversation

openperf commented Mar 22, 2026

Summary

Root Cause

Changes

Fixes

Uh oh!

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

Uh oh!

🔒 Aisle Security Analysis

1. 🔵 SSRF via configurable MiniMax API host in minimaxUnderstandImage

Description

Recommendation

2. 🔵 Plugin SDK exposes global Undici dispatcher mutation (process-wide proxy hijack)

Description

Recommendation

Uh oh!

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

Uh oh!

Greptile Summary

Confidence Score: 4/5

Comments Outside Diff (1)

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

openperf commented Mar 22, 2026

🔒 Aisle Security Analysis

Severity Title

1. 🟡 OAuth/token requests routed via env-controlled HTTP(S) proxy (global Undici dispatcher)

Description

Recommendation

Uh oh!

openperf commented Mar 22, 2026

Greptile Summary

Confidence Score: 4/5

Comments Outside Diff (1)

Uh oh!

Uh oh!

Takhoffman commented Mar 23, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

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

edited

Loading

greptile-apps bot commented Mar 22, 2026 •

edited

Loading