[Bug]: Agent cursor overlay remains visible after Computer Use session ends

[kyrregjerstad]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Open a thread in T3 Code Desktop.
2. Let the agent perform a Computer Use session.
3. Wait for the Computer Use session to finish.
4. Continue using T3 Code.

This happens intermittently rather than after every Computer Use session.

Expected behavior

The agent cursor overlay should disappear when the Computer Use session ends.

Actual behavior

The cursor used during Computer Use sometimes remains visible on screen after the session has finished. It remains stuck until T3 Code is closed.

Impact

Minor bug or occasional failure

Version or commit

Unknown.

Environment

T3 Code Desktop. OS, T3 Code version, and provider version not yet recorded.

Logs or stack traces

No logs collected.

Screenshots, recordings, or supporting files

None currently.

Workaround

Close and reopen T3 Code.

[juliusmarminge]

Triage

This looks like a real leftover Computer Use overlay, not a T3 preview-cursor leak.

On main, T3 does not own a desktop agent-cursor window. Computer Use is Codex’s bundled helper (unified-computer-use@openai-bundled / @oai/sky / SkyComputerUseService). T3 starts Codex as an app-server child and presents computerUse tool calls in CodexAdapter. Session/turn teardown in CodexSessionRuntime interrupts the turn and can close the session, but it never hides or reaps the Computer Use helper that draws the cursor.

That matches the report: the overlay can survive after the session looks finished, and it only disappears when T3 Code is quit (which kills the Codex process tree). Codex already has the same class of leftover overlays/helpers after Computer Use goes idle, including when an embedding app-server stays alive between turns.

This is not a duplicate of #11579 (bundled Computer Use stealing browser work from T3 preview). T3’s in-preview AgentBrowserCursor is a different surface and is designed to stay dimly visible after clicks. The closed T3-native AgentCursor work in #6537 never landed.

Where a T3 look belongs

• apps/server/src/provider/Layers/CodexSessionRuntime.ts — turn complete / interrupt / session close
• apps/server/src/provider/Layers/CodexAdapter.ts — Computer Use presentation only; no overlay lifecycle
• No T3 host API today to dismiss the Codex cursor

Proposed next step

1. Please add OS, T3 Code version, Codex CLI version, and a screenshot/recording of the stuck cursor.
2. On the next repro, check whether SkyComputerUseService, codex-computer-use, or cua_node is still running after the turn ends.
3. Investigate whether T3 can request Computer Use teardown when a turn completes or is interrupted. If Codex has no supported host API for that, the durable fix is upstream.

Accepting as a real desktop bug; marking upstream because the overlay is owned by Codex Computer Use. Workaround remains quit and reopen T3 Code.

Related:

• [macOS] Computer Use and BUZZ ACP continue after Codex is closed openai/codex#36958
• Codex Desktop Browser Use forces uncontrollable Picture-in-Picture and leaves orphan Computer Use mascot overlay openai/codex#32363
• Codex Computer Use leaves ScreenCaptureKit stream running at ~56 FPS, causing high WindowServer GPU on macOS openai/codex#35659