Desktop (macOS): computer-use permission dialog has only a Deny button, no Allow

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 9, 2026

Environment

  • Claude Desktop (macOS): app version 1.49585.0, Electron 44.2.0, Node 24.20.0
  • macOS, Apple Silicon (arm64)
  • Cowork session running in cloud, linked to this Mac ("Link to this computer")
  • Target app: Telegram Desktop (bundle id ru.keepcoder.Telegram)

What happens

When the session calls computer_request_access for Telegram, the desktop shows the approval dialog
"Claude wants to use Telegram", but the dialog renders only a "Deny ⌘." button. There is no
"Allow" / "Approve" control anywhere in the dialog. The only way to close it is Deny, so every request
comes back as User rejected mcp__remote-devices__computer_request_access.

Screenshots of the dialog were taken by the user (two of them) and confirm there is no Allow button.

Reproduction

  1. Start a Cowork session linked to the Mac.
  2. From the session, call computer_resolve_access(["Telegram"]) → resolves fine

(tier: full, preferredModeDefault: background, screenshotFiltering: native).

  1. Call computer_request_access with the resolved entry and a reason.
  2. The approval dialog appears on the Mac with a single "Deny" button.

Reproduced 8 times over ~3 hours (2026-09-09, 15:00–20:30 UTC+5), across several turns and one
MCP reconnect.

What was already tried (no effect)

  • Signing out of the desktop app and signing back in
  • Fully quitting and relaunching Claude Desktop
  • Reconnecting the remote-devices MCP (grants are dropped on reconnect, dialog still broken)
  • Waiting several hours between attempts

Expected

The dialog should offer Allow (and Deny), as it did earlier: computer-use access to the same Telegram
app was granted successfully from the same Mac on 2026-09-08 (evening) and on 2026-09-09 around
14:50 local time, and full-screen control worked. The dialog broke later the same day.

Notes

  • computer_request_full_control was never reached, because the app grant itself fails first.
  • Other remote-devices tools (device_bash on connected folders, Chrome extension) keep working fine

in the same session, so the link itself is healthy — it is specifically the computer-use approval UI.

View original on GitHub ↗