[BUG] "Open" button stays stuck after present_files tool use

Resolved 💬 2 comments Opened Mar 27, 2026 by GuyMannDude Closed Mar 31, 2026

Bug Description

After Claude uses the mcp__cowork__present_files tool to present a file, the "Open" button/overlay in the UI stays active and won't dismiss. The only way to clear it is to navigate away from the session and come back.

Environment

  • Claude Desktop version: 1.1.8629
  • OS: Ubuntu Linux (kernel 6.14.0-27-generic), installed via aaddrick/claude-desktop-debian Debian package
  • Model: Claude Opus 4.6 (via Claude Desktop chat)

Steps to Reproduce

  1. In a Claude Desktop session, trigger a workflow where Claude presents a file via mcp__cowork__present_files
  2. Click the "Open" button when it appears
  3. The Open button/overlay remains active — does not dismiss or return to normal conversation state
  4. Clicking elsewhere, scrolling, or continuing the conversation does not clear it
  5. Only fix: navigate away from the session entirely and return

Expected Behavior

The "Open" button should dismiss after being clicked and the file action should complete, returning the UI to normal conversation state.

Actual Behavior

The "Open" button stays stuck in an active/highlighted state. The overlay persists indefinitely. No amount of interaction within the session clears it. Requires leaving the session and coming back.

Logs

Checked ~/.config/Claude/logs/main.log and ~/.config/Claude/logs/cowork_vm_node.log — no errors or warnings related to this behavior during the timeframe it occurred.

Related Issues

This appears to be in the same family as #22127 (MCP tool calls hang until user clicks/expands panel) — both involve MCP tool result UI elements not properly dismissing after interaction.

Notes

  • Reproducible — happened during a normal file presentation workflow, not an edge case
  • The tool itself completes successfully (the file is presented correctly)
  • The bug is purely in the UI layer's handling of the post-action state

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗