Chris Tate 640d259130 Fix extensions not being loaded from config.json (#750) ...

Fix issue where Chrome extensions specified in the `extensions` field of `config.json` were not being loaded when launching the browser.

## Problem
Extensions configured via the `extensions` field in `config.json` were not being passed to the Chrome browser launch command, causing them to be ignored.

## Changes
- Added `!flags.extensions.is_empty()` to the launch trigger condition to ensure browser launch is triggered when extensions are configured
- Added extensions to the launch command JSON payload so they are properly passed to the browser

Fixes #726

2026-03-13 02:42:39 -05:00

..

cdp-protocol

native (#594)

2026-03-03 15:15:57 -06:00

src

Fix extensions not being loaded from config.json (#750)

2026-03-13 02:42:39 -05:00

build.rs

Fix clippy warnings across CLI codebase (#654)

2026-03-06 16:18:51 -06:00

Cargo.lock

chore: version packages (#740)

2026-03-12 14:41:00 -05:00

Cargo.toml

chore: version packages (#740)

2026-03-12 14:41:00 -05:00