github / github/app

Computer Use leaves accessed windows permanently topmost

Open
#3,524 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

Description

Short summary

After an agent accesses an application using Computer Use, that application's window remains in the foreground and prevents other windows on the same monitor from rendering over it, even after the agent has stopped using Computer Use.

Affected version or release

v1.1.14

Installation context

Installed on an MDB.

What happened?

If I let an agent access an app using Computer Use, the app refuses to let other applications render over it, even after the agent stops using Computer Use.

For example, if I let an agent inspect something in an isolated Edge window, that window does not let anything else render over it when I focus another app on the same monitor. The newly focused app stays behind the window the agent previously inspected. Ending the session is required to stop this behavior.

Steps to reproduce
  1. Open a session with an agent.
  2. Let the agent access an application using Computer Use, including the GitHub Copilot app itself.
  3. Try to focus another application that was already open on the same monitor.
  4. Observe that the second application remains behind the window the agent inspected. It becomes visible only after minimizing that window, even though the agent is no longer interacting with it.
Expected behavior

When I focus another application, its window should render normally over an application that an agent previously inspected using Computer Use. The inspected window should not remain permanently topmost after Computer Use finishes.

Additional context

The behavior persists after the agent finishes interacting with the window and appears to clear only after ending the session.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the GitHub Copilot app on an MDB using an isolated Edge window and Computer Use. Start by tracing the Computer Use session lifecycle and window focus behavior; done means another focused application renders over the inspected window without minimizing it or ending the session.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.