[Windows] In-app browser device preview toolbar closes when Browser Use returns control
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- desktop
Research direction
Start by reproducing the Browser Use viewport change at 393 × 852 and trace the device-preview toolbar state when control returns to the user, including the case without tabs.finalize(). Done means the user- or agent-selected preview remains visibly active until explicitly reset.
Written by the indexing model from the issue text.
Description
Codex App version
Microsoft Store package version 26.715.3651.0 on Windows x64.
What issue are you seeing?
When Browser Use sets the in-app browser to an iPhone-sized responsive/device preview (393 × 852), the preview works while the agent controls the browser, but the visible device-preview toolbar closes again as soon as the Browser Use step ends and control returns to the user.
This also reproduced when the agent deliberately did not call tabs.finalize(). During the active Browser Use call, page evaluation confirmed:
window.innerWidth === 393window.innerHeight === 852
After the tool call returned, the user observed the device-preview toolbar close again.
Steps to reproduce
- Open a local web page in the Codex in-app browser.
- Start Browser Use and set the browser viewport:
await viewport.set({ width: 393, height: 852 }) - With the tab claimed, reload if necessary and verify the page viewport is 393 × 852.
- End the Browser Use tool call and return control to the user.
- Observe that the visible responsive/device-preview toolbar closes or is no longer visibly pinned.
- Repeat without calling
browser.tabs.finalize(...); the same behavior occurs.
Expected behavior
The user-selected or agent-set device preview should remain visibly active until the user or agent explicitly resets it.
Actual behavior
The device preview is temporary to the Browser Use control step. Its toolbar is dismissed when control returns, so the agent cannot leave the requested iPhone preview visibly pinned for the user.
Additional context
The first reproduction used tabs.finalize(), which also closed the toolbar. A second reproduction intentionally omitted finalization, but the toolbar still closed after the Browser Use call ended.
I searched existing issues before filing. Issues such as #28062 cover different device-toolbar problems (for example, blank zoom options), not this toolbar-lifecycle/persistence behavior.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·