mirror of
https://github.com/OpenRouterTeam/spawn.git
synced 2026-04-28 03:49:31 +00:00
fix: use Google Chrome .deb for OpenClaw browser tool (#2368)
* fix: use Google Chrome .deb instead of Playwright for OpenClaw browser Snap Chromium on Ubuntu 24.04 fails because AppArmor confinement blocks CDP control. OpenClaw's own docs recommend installing Google Chrome via .deb package which bypasses snap entirely. Also adds browser.noSandbox and browser.executablePath to the OpenClaw config so the browser tool works out of the box on Linux VMs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: remove unnecessary confirmation prompt when OAuth fails If OAuth didn't complete, the user obviously wants to paste a key. The "Paste your API key manually? (Y/n)" prompt was pointless friction. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: remove unnecessary "Continue anyway?" credential confirmation If the user selected a cloud, they obviously want to continue. The warning + setup guidance is sufficient — no need to block on a confirm. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: move Chrome install to configure step so it runs after tarball The tarball path skips agent.install() entirely, so Chrome never got installed. Moving it to configure() (setupOpenclawConfig) ensures it always runs regardless of install method. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: bundle Google Chrome in openclaw tarball Add Chrome .deb install to openclaw's tarball build so it ships pre-installed. Capture /usr/bin/google-chrome and /opt/google/chrome/ in the tarball. Add dl.google.com to the workflow domain allowlist. The configure() step still has a fallback install with idempotency check (command -v google-chrome) for non-tarball installs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: use openclaw config set for browser setup + correct binary name - Use `google-chrome-stable` (actual .deb binary name) not `google-chrome` - Set browser config via `openclaw config set` CLI (the supported way) instead of writing JSON directly which wasn't being picked up - Remove browser section from JSON config to avoid conflicts Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
3c029be108
commit
7e2f9f45fc
7 changed files with 51 additions and 40 deletions
|
|
@ -14,7 +14,8 @@
|
|||
"openclaw": {
|
||||
"tier": "full",
|
||||
"install": [
|
||||
"mkdir -p ~/.npm-global/bin && npm install -g --prefix ~/.npm-global openclaw"
|
||||
"mkdir -p ~/.npm-global/bin && npm install -g --prefix ~/.npm-global openclaw",
|
||||
"wget -q https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb -O /tmp/google-chrome.deb && apt-get install -y -qq /tmp/google-chrome.deb && rm -f /tmp/google-chrome.deb"
|
||||
]
|
||||
},
|
||||
"opencode": {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue