[Bug]: F12 in one Space opens DevTools in a different Space

[lyydsheep]

Affected component

ego lite browser app

What happened?

When multiple Spaces are open, pressing F12 in the currently focused Space switches to another Space and opens the developer console there.

The shortcut is applied to the wrong Space instead of the one that has keyboard focus. This makes DevTools unusable for inspecting the page you are actually looking at.

Steps to reproduce

1. Open ego lite and create at least two Spaces (Space A and Space B). Put a normal webpage in each.
2. Click into Space A so it is focused / in the foreground.
3. Press F12 to open the developer console.
4. Observe that the UI switches to Space B (or another Space) and opens DevTools there, instead of opening it in Space A.

Expected behavior

F12 should open DevTools for the currently focused Space and leave that Space in the foreground. Other Spaces should stay untouched.

Version

ego lite 0.4.6.13; ego-browser 0.4.6.13

Environment

macOS 26.6 (25G72), Apple Silicon (arm64)

Logs or screenshots

Additional context

I searched existing issues for F12, DevTools, console, inspector, 控制台, and 开发者工具 and did not find a duplicate.

Closest related reports, but not the same bug:

• [Bug]: Profile switching targets the previous window #210 Profile switching targets the previous window (wrong-window targeting, but for profiles, not DevTools)
• [Feature]: Per-taskspace CDP channel isolation to avoid global CDP state races #213 Per-taskspace CDP channel isolation (global CDP state, agent/runtime, not the F12 UI)

This looks like the DevTools toggle is bound to a global inspected target / last-active Space rather than the Space that currently has focus.

Before submitting

• I searched the existing issues and did not find a duplicate.
• I removed secrets and sensitive browsing data from this report.

[liuwd8]

Thanks for the report.

I have reproduced this locally. The behavior matches your description: when multiple Spaces are open, pressing F12 from the focused Space can open DevTools for a different Space and bring that other Space forward.

We are investigating the wrong-target selection path for the DevTools toggle. The expected behavior is that F12 should resolve the inspected target from the currently focused/foreground Space, not from a stale or global last-active target.

Written by liuwd8, edited by Codex operating ego-lite.

[liuwd8]

This has been fixed and will be included in next week's update.

Written by liuwd8, sent by Codex operating ego-lite.