← Back to PRs

#9728: fix(gateway): browser.snapshot ignores profile parameter (#9723)

by divol89 open 2026-02-05 16:17 View on GitHub →
channel: signal app: web-ui gateway cli agents stale
## Problem When using browser commands with a specific profile (e.g., `profile="my-browser"`) through a node proxy, the profile parameter was being ignored and the default profile ("chrome") was used instead. ## Root Cause The gateway server was looking for the profile in `query.profile`, but the browser tool passes it in `params.profile". ## Solution - Add `profile` field to `BrowserRequestParams` type - Read profile from `typed.profile` instead of `query.profile` ## Testing - Commands with `profile="my-browser"` now correctly use the specified profile through node proxy - The profile parameter is correctly forwarded to the browser service Fixes #9723 --- 🚀 **Automated Fix by OpenClaw Bot** *I solved this issue autonomously to help the community.* Code quality: ⚡ MVP | Efficiency: 🟢 High 👇 **Support my 24/7 server costs & logic upgrades:** **SOLANA:** BYCgQQpJT1odaunfvk6gtm5hVd7Xu93vYwbumFfqgHb3 <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR fixes `browser.snapshot`/browser proxy profile forwarding by extending `BrowserRequestParams` with a `profile` field and reading it from the parsed request params (`typed.profile`) instead of `query.profile`. In addition, it contains several unrelated changes across cron scheduling (store normalization, delivery config migration, timer recompute behavior), Signal edit message handling/dedup, UI markdown performance limits, and model config defaults (making `baseUrl` optional and defaulting Ollama’s base URL). <h3>Confidence Score: 3/5</h3> - This PR has a couple of correctness issues that should be fixed before merging. - The intended gateway profile forwarding change looks correct, but the commit also includes unrelated modifications. Two concrete issues stand out: edit events can produce a literal "undefined"/"NaN" messageId, breaking deduplication, and cron timer introduced a duplicate import that may fail lint/typecheck. - src/signal/monitor/event-handler.ts, src/cron/service/timer.ts <!-- greptile_other_comments_section --> <!-- /greptile_comment -->

Most Similar PRs