fix(browser): honor cdpUrl for user default profile by HemantSudarshan · Pull Request #80143 · openclaw/openclaw

HemantSudarshan · 2026-05-10T07:06:29Z

Problem summary

browser.cdpUrl was ignored when browser.defaultProfile selected an existing-session profile such as the built-in user profile. Chrome MCP then launched through its default auto-connect path and could still look for DevToolsActivePort instead of using the configured endpoint.

Root cause

resolveBrowserConfig only carried the legacy top-level browser.cdpUrl into the managed openclaw profile. resolveProfile handles existing-session profiles from their profile-local cdpUrl, so an explicit defaultProfile: "user" left the selected profile with an empty endpoint.

Architectural reasoning

The fix stays inside browser profile resolution, where the legacy single-profile config is normalized. When the selected default profile is existing-session and has no explicit endpoint, the resolver now applies the normalized top-level browser.cdpUrl to that profile. Explicit per-profile cdpUrl still wins. Chrome MCP session creation, caching, cleanup, gateway routes, and action behavior are unchanged; the existing Chrome MCP argument builder already converts HTTP endpoints to --browserUrl and websocket endpoints to --wsEndpoint without combining them with userDataDir.

Testing performed

pnpm test extensions/browser/src/browser/config.test.ts
pnpm test extensions/browser/src/browser/chrome-mcp.test.ts
pnpm exec oxfmt --check --threads=1 extensions/browser/src/browser/config.ts extensions/browser/src/browser/config.test.ts
pnpm lint:extensions
pnpm tsgo:extensions from temporary P:\ mapping because the local checkout path contains a space and the direct Windows command split C:\Projects\Personal Project.
pnpm tsgo:extensions:test from temporary P:\ mapping for the same path reason.
git diff --check
pnpm check:changed exited 0 in this checkout, but printed no lane details.
pnpm test extensions/browser was attempted. It failed on existing local Windows environment assumptions outside this patch: unsupported local browser discovery in chrome.internal.test.ts, LaunchServices default-browser expectations, and POSIX /tmp path expectations resolving as C:\tmp.

Real behavior proof

Behavior or issue addressed: browser.defaultProfile: "user" plus top-level browser.cdpUrl now resolves to an existing-session profile with that endpoint, so Chrome MCP receives endpoint flags instead of --autoConnect.
Real environment tested: local Windows checkout, pnpm 10.33.2, Node v22.15.0. The repo warns it wants Node >=22.16.0, but targeted tests, lint, and typechecks completed as listed above.
Exact steps or command run after this patch:

pnpm exec tsx -e "import { resolveBrowserConfig, resolveProfile } from './extensions/browser/src/browser/config.ts'; import { buildChromeMcpArgs } from './extensions/browser/src/browser/chrome-mcp.ts'; const resolved = resolveBrowserConfig({ defaultProfile: 'user', cdpUrl: 'http://127.0.0.1:9222/' } as any); const profile = resolveProfile(resolved, resolved.defaultProfile); if (!profile) throw new Error('profile missing'); const args = buildChromeMcpArgs(profile); console.log(JSON.stringify({ defaultProfile: resolved.defaultProfile, driver: profile.driver, cdpUrl: profile.cdpUrl, args }, null, 2)); if (!args.includes('--browserUrl') || args.includes('--autoConnect') || args.includes('--userDataDir')) throw new Error('Chrome MCP args did not use configured cdpUrl cleanly');"

Evidence after fix:

{
  "defaultProfile": "user",
  "driver": "existing-session",
  "cdpUrl": "http://127.0.0.1:9222",
  "args": [
    "-y",
    "chrome-devtools-mcp@latest",
    "--browserUrl",
    "http://127.0.0.1:9222",
    "--experimentalStructuredContent",
    "--experimental-page-id-routing"
  ]
}

Observed result after fix: the selected user existing-session profile carries http://127.0.0.1:9222, and Chrome MCP launch args contain --browserUrl with no --autoConnect or --userDataDir fallback.
What was not tested: live attachment to a real Chrome v145 instance on port 9222 was not run in this environment.

Risk analysis

Risk is low to medium. The change is limited to config normalization and only affects an existing-session default profile with a top-level browser.cdpUrl and no profile-local endpoint. It does not modify session caching, concurrency, gateway protocol, route behavior, cleanup logic, or managed browser launch semantics. The main compatibility risk is users who accidentally had both defaultProfile: "user" and browser.cdpUrl; that config now follows the documented endpoint instead of silently ignoring it.

Backward compatibility

Existing defaults are preserved: the built-in user profile still has no endpoint unless selected as the default with a top-level browser.cdpUrl, and explicit browser.profiles.<name>.cdpUrl continues to take precedence. No public API shape, config schema, gateway payload, or protocol version changes are introduced.

clawsweeper · 2026-05-10T07:09:49Z

Codex review: needs maintainer review before merge. Reviewed June 10, 2026, 11:02 AM ET / 15:02 UTC.

Summary
The PR applies normalized top-level browser.cdpUrl to the selected existing-session default profile when it has no profile-local endpoint, adds precedence tests, and updates endpoint help/type descriptions.

PR surface: Source +30, Tests +33. Total +63 across 4 files.

Reproducibility: yes. Current-main source provides a high-confidence path: top-level browser.cdpUrl is assigned to the managed profile, while the selected built-in user existing-session profile remains endpoint-free and therefore uses Chrome MCP auto-connect.

Review metrics: 1 noteworthy metric.

Config/default behavior: 1 existing setting newly honored in 1 selected-profile case. The patch changes how an existing top-level endpoint is normalized when the default is an existing-session profile, without adding a new config key or default.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🐚 platinum hermit
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

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

Rank-up moves:

none.

Next step before merge

The patch has no actionable repair finding and should proceed through normal maintainer review and landing rather than a ClawSweeper fix lane.

Security
Cleared: The diff adds no dependency, permission, secret-access, or code-execution source, and inherited endpoints use current main’s credential-redacted diagnostic and status paths.

Review details

Best possible solution:

Land the narrow resolver normalization on current main, keeping explicit per-profile cdpUrl authoritative and relying on the merged existing-session endpoint and redaction paths for runtime behavior.

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

Yes. Current-main source provides a high-confidence path: top-level browser.cdpUrl is assigned to the managed profile, while the selected built-in user existing-session profile remains endpoint-free and therefore uses Chrome MCP auto-connect.

Is this the best way to solve the issue?

Yes. Browser config resolution is the narrow normalization owner, and this implementation reuses the canonical profile-local endpoint runtime added by #91736 instead of adding another connection path.

AGENTS.md: found and applied where relevant.

Codex review notes: reasoning high; reviewed against ade5ac03506e.

Label changes

Label changes:

add P2: The PR fixes a bounded browser configuration bug that causes an explicitly configured endpoint to be ignored and selects the wrong Chrome MCP connection path.
add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix local live output showing the selected user profile carries the normalized endpoint and Chrome MCP receives --browserUrl without --autoConnect or --userDataDir.
add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR body includes after-fix local live output showing the selected user profile carries the normalized endpoint and Chrome MCP receives --browserUrl without --autoConnect or --userDataDir.

Label justifications:

P2: The PR fixes a bounded browser configuration bug that causes an explicitly configured endpoint to be ignored and selects the wrong Chrome MCP connection path.
rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (live_output): The PR body includes after-fix local live output showing the selected user profile carries the normalized endpoint and Chrome MCP receives --browserUrl without --autoConnect or --userDataDir.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-fix local live output showing the selected user profile carries the normalized endpoint and Chrome MCP receives --browserUrl without --autoConnect or --userDataDir.

Evidence reviewed

PR surface:

Source +30, Tests +33. Total +63 across 4 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	3	33	3	+30
Tests	1	33	0	+33
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	4	66	3	+63

What I checked:

Current-main reproduction: Current resolveBrowserConfig only passes the legacy endpoint into ensureDefaultProfile, which creates or updates the managed openclaw profile; ensureDefaultUserBrowserProfile creates user without cdpUrl, and no later normalization copies the top-level endpoint to the selected existing-session default. (extensions/browser/src/browser/config.ts:315, ade5ac03506e)
Exact refreshed patch: The PR head adds one resolver helper that fills only a selected existing-session profile with no explicit cdpUrl, then adds tests for inheritance and profile-local precedence. (extensions/browser/src/browser/config.ts:345, 6026eb8ad14a)
Merged sibling implementation: The related merged change supports profile-local existing-session endpoints in Chrome MCP, improves connection diagnostics, and redacts endpoint credentials, but its diff does not modify resolveBrowserConfig; this PR remains the missing legacy-config bridge. (extensions/browser/src/browser/chrome-mcp.ts:270, ac21e89c13e4)
Redaction coverage: Current main redacts resolved profile endpoints in browser status and formats endpoint diagnostics through CDP URL redaction, so an inherited endpoint follows the same credential-safe output paths as an explicit profile endpoint. (extensions/browser/src/browser/server-context.ts:236, ade5ac03506e)
Current-main provenance: Blame ties the current profile construction and legacy endpoint normalization block to the recent browser config refactor on main, while the endpoint runtime was subsequently completed by the merged related PR. (extensions/browser/src/browser/config.ts:417, 7b7e8f6e88e7)
Release status: The PR head is not contained by current main or any release tag, while the latest release predates both the refreshed head and the merged downstream endpoint commit; the requested top-level normalization is therefore not shipped or implemented on main. (6026eb8ad14a)

Likely related people:

lifuyue: Authored the merged existing-session endpoint routing, diagnostics, CLI/status, and redaction implementation that this normalization patch builds upon. (role: recent feature contributor; confidence: high; commits: ac21e89c13e4; files: extensions/browser/src/browser/chrome-mcp.ts, extensions/browser/src/browser/server-context.ts, extensions/browser/src/browser/profiles-service.ts)
Vincent Koc: The current browser config construction and legacy endpoint normalization block trace through the recent config refactor commit, making this a useful routing candidate for resolver behavior. (role: recent area contributor; confidence: medium; commits: 7b7e8f6e88e7; files: extensions/browser/src/browser/config.ts)
sallyom: Refreshed the PR head onto the current browser implementation and requested review after the related endpoint support merged. (role: recent integrator; confidence: medium; commits: 6026eb8ad14a; files: extensions/browser/src/browser/config.ts, extensions/browser/src/browser/config.test.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

RomneyDa · 2026-05-29T06:30:51Z

Heads up: this PR needs to be updated against current main before the new required Dependency Guard check can pass.

Copilot

Pull request overview

Fixes a configuration-resolution bug where top-level browser.cdpUrl was not honored when browser.defaultProfile selected an existing-session profile (notably the built-in user profile), causing Chrome MCP to fall back to --autoConnect behavior instead of using the configured DevTools endpoint.

Changes:

Apply the normalized top-level browser.cdpUrl to the selected default profile when that profile is existing-session and has no explicit per-profile cdpUrl.
Update config/help text to describe per-profile cdpUrl as a general CDP/DevTools endpoint (remote CDP or existing-session attach).
Add regression tests covering default-profile inheritance and precedence of explicit per-profile cdpUrl.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/config/types.browser.ts	Clarifies `cdpUrl` documentation for browser profiles.
src/config/schema.help.ts	Updates help text for per-profile `cdpUrl` to reflect existing-session attach semantics.
extensions/browser/src/browser/config.ts	Fixes profile resolution to propagate legacy/top-level `cdpUrl` into an `existing-session` default profile when needed.
extensions/browser/src/browser/config.test.ts	Adds tests validating the new default-profile `cdpUrl` inheritance and precedence rules.

sallyom · 2026-06-10T16:24:57Z

  "browser.profiles.*.cdpUrl":
-    "Per-profile CDP websocket URL used for explicit remote browser routing by profile name. Use this when profile connections terminate on remote hosts or tunnels.",
+    "Per-profile CDP/DevTools endpoint URL used for explicit browser routing by profile name. Use this for remote CDP hosts, tunnels, or existing-session profiles that should attach through a running Chrome DevTools endpoint.",


sallyom · 2026-06-10T16:35:27Z

Rebased this on current main after #91736 landed, resolved the overlap, and addressed the review finding by updating the top-level browser.cdpUrl help text to match the accepted CDP/DevTools endpoint forms.

The fix still targets #48042’s reported path: top-level browser.cdpUrl with defaultProfile: "user" now resolves into the selected existing-session profile, while explicit per-profile cdpUrl continues to take precedence. Targeted tests, formatting, diff check, and autoreview are clean. I’m comfortable merging this.

…26.6.6) (#1040) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040

openclaw-barnacle Bot added size: S proof: supplied External PR includes structured after-fix real behavior proof. labels May 10, 2026

HemantSudarshan mentioned this pull request May 10, 2026

fix(browser): honor cdpUrl for user default profile #79994

Closed

clawsweeper Bot added the proof: sufficient ClawSweeper judged the real behavior proof convincing. label May 10, 2026

clawsweeper Bot mentioned this pull request Jun 9, 2026

Support existing-session browser CDP endpoints #91736

Merged

sallyom force-pushed the hemant/48042-browser-cdp-url branch from 3e9e103 to 6026eb8 Compare June 10, 2026 14:56

Copilot AI review requested due to automatic review settings June 10, 2026 14:56

Copilot started reviewing on behalf of sallyom June 10, 2026 14:56 View session

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 10, 2026

Copilot AI reviewed Jun 10, 2026

View reviewed changes

sallyom self-assigned this Jun 10, 2026

fix(browser): honor cdp url for default session profile

625156c

sallyom force-pushed the hemant/48042-browser-cdp-url branch from 6026eb8 to 625156c Compare June 10, 2026 16:24

sallyom merged commit 2e4bf41 into openclaw:main Jun 10, 2026
158 of 160 checks passed

github-actions Bot mentioned this pull request Jun 10, 2026

📡 Upstream Digest — 2026-06-10 16:54 UTC curtismercier/openclaw-mods#1053

Open

github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request Jun 11, 2026

fix(browser): honor cdp url for default session profile (openclaw#80143)

771a773

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(browser): honor cdpUrl for user default profile#80143

fix(browser): honor cdpUrl for user default profile#80143
sallyom merged 1 commit into
openclaw:mainfrom
HemantSudarshan:hemant/48042-browser-cdp-url

HemantSudarshan commented May 10, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented May 10, 2026 •

edited

Loading

Uh oh!

RomneyDa commented May 29, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

sallyom Jun 10, 2026

Uh oh!

sallyom commented Jun 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

HemantSudarshan commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem summary

Root cause

Architectural reasoning

Testing performed

Real behavior proof

Risk analysis

Backward compatibility

Uh oh!

clawsweeper Bot commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

RomneyDa commented May 29, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

sallyom Jun 10, 2026

Choose a reason for hiding this comment

Uh oh!

sallyom commented Jun 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

HemantSudarshan commented May 10, 2026 •

edited

Loading

clawsweeper Bot commented May 10, 2026 •

edited

Loading