Problem

When running opencli bilibili hot (or any browser-based command) on Chrome 146+, the command fails with:

Error: Invalid value for state

Running opencli doctor shows:

[OK] Daemon: running on port 19825
[OK] Extension: connected
[FAIL] Connectivity: failed (Invalid value for state)

Root Cause Analysis

1. Chrome API Documentation

According to the Chrome Extensions API documentation, the state parameter for chrome.windows.create() is described as:

state (WindowState) - Optional. Chrome 44+. The initial state of the window ('minimized', 'maximized', 'fullscreen'). Cannot be combined with 'left', 'top', 'width', or 'height'.

Key finding: The state parameter only accepts 'minimized', 'maximized', and 'fullscreen' as input values. The value 'normal' is NOT a valid input for chrome.windows.create().

2. WindowState Enum vs. state Parameter Input

While the WindowState enum definition includes "normal":

WindowState Enum:
  "normal" - Normal window state
  "minimized" - Minimized window state
  "maximized" - Maximized window state
  "fullscreen" - Fullscreen window state

This enum is used for reading window state (return value), not for setting window state during creation.

3. Chrome 146 Behavior Change

Chrome 146 (tested on 146.0.7680.165) now enforces stricter validation on the state parameter. Previous Chrome versions may have silently ignored invalid state values, but Chrome 146 throws an error.

4. The Bug

In extension/src/background.ts:163-170:

const win = await chrome.windows.create({
  url: BLANK_PAGE,
  focused: false,
  width: 1280,
  height: 900,
  type: 'normal',
  state: 'normal',  // ❌ Invalid: 'normal' is not an accepted input value
});

Solution

Remove the state: 'normal' parameter entirely. When state is not specified, the window defaults to 'normal' state anyway.

const win = await chrome.windows.create({
  url: BLANK_PAGE,
  focused: false,
  width: 1280,
  height: 900,
  type: 'normal',
  // No state parameter - window defaults to 'normal' state
});

Testing

Environment:

• Chrome version: 146.0.7680.165
• opencli version: 1.5.3

After applying the fix:

• opencli doctor passes all checks
• opencli bilibili hot returns results correctly

opencli v1.5.3 doctor (node v22.16.0)

[OK] Daemon: running on port 19825
[OK] Extension: connected (v1.5.3)
[OK] Connectivity: connected in 0.3s

Everything looks good!

References

• Chrome Windows API Documentation
• WindowState Enum