Skip to content

[Windows Desktop] @Browser selected and in-app tab visible, but existing chat cannot read page #56193

Open

Description

@bella9527-A

Summary

In an existing local Codex chat on Windows, the built-in Browser tab opens and is visible to the user, but selecting @Browser in the composer does not give the assistant a supported way to read or control the page. The same chat had previously used the in-app browser successfully. This blocks a read-only website research task.

Environment

  • Windows desktop app, local Codex chat.
  • Bundled Browser component: 26.1016.51333 (from local plugin configuration; not claimed as the About-dialog app version).
  • Browser plugin is present and configured as enabled.
  • The exact desktop app package version could not be verified in this run.

Reproduction

  1. Open an existing local Codex chat and a website in its built-in Browser tab.
  2. Confirm that the tab visibly renders in the app.
  3. Select @Browser in the chat composer and ask the assistant to read the current page.
  4. The assistant can see only ambient tab metadata (such as the current URL), not the rendered page, and has no Browser-specific callable control entry point or provided Browser bootstrap instructions.
  5. Closing and reopening the tab in the same chat does not restore access.

Expected

The browser-enabled chat can inspect and interact with the visible in-app tab through the supported Browser API, or receives a specific actionable connection/permission error.

Actual

The website renders normally for the user, while the assistant cannot read its page content or perform browser actions. A generic Node REPL tool is present, but the Browser-specific control interface is not provided to this chat. No website login failure has been established.

Request

Please investigate Browser capability/tool binding for existing local chats after explicit @Browser selection, and provide a supported recovery path that preserves the browser profile and signed-in session. Please distinguish tool-provisioning failure from page-login or browser-tab failure.

Potentially related, but not confirmed to share a root cause: #50778 and #55243.

Submitted at the user's explicit request. No shop name, account identifiers, private URL, screenshots, transcripts, or logs are attached.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    on Oct 22, 2026
  2. gennus-design commented on Nov 20, 2026

    @gennus-design

    I can reproduce this on Windows in an existing Codex desktop chat. The built-in browser opens and works manually. When I switch pages, Codex receives the updated tab URL. Even after I select @Browser, Codex still cannot read the page contents. This persisted across several attempts in the same conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbrowserbugSomething isn't workingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions