[BUG] Windows Desktop: app-access prompt offers "Deny" as the only option; computer_request_access always rejected in a cloud Cowork session

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code

### What's Wrong?

In a Cowork session running in the cloud and linked to a Windows desktop, computer_resolve_access works perfectly — it returns the real executables, their tier and the willHide list — but every computer_request_access call comes back rejected, and on the desktop the approval card appears with "Deny" as the only available option. There is no "Allow for this session" button at all. The user is shown a choice that isn't one.

The same account, same machine and same apps worked normally the previous day (2026-09-08, around midday local time), when Word and Acrobat were granted in full-control mode and used successfully.

Apps requested: Word 2016, Excel 2016, Adobe Acrobat, Adobe Acrobat Distiller (also tried including Windows PowerShell, tier "click"). Plan: Max.

WHAT WAS TRIED, AND DID NOT FIX IT

- Computer-use toggle: the very first computer_request_access returned "computer use is not turned on yet". The user enabled it in Settings > General > Desktop app, and from then on every request comes back rejected with Deny as the only option. Enabling it mid-session never took effect.
- Overlays: closed NVIDIA Overlay/Share and every other overlay process. No change.
- Full app restart (killing every claude process, then reopening). No change.
- Sign out and sign back in. This did fix a separate error visible in the logs (`oauth failed: authorize returned 403 `, which afterwards became `[oauth-v2] performing fresh /authorize`), but the approval card behaviour did not change.
- Blocked-apps list: empty.
- Connectors page: all connectors connected, nothing blocked.
- Requesting a single app at a time, and requesting without the terminal (Windows PowerShell, the only isSentinel entry) in the set. No change.
- The permission mode of the conversation was "Automatically approve" throughout.

LOG EVIDENCE

%LOCALAPPDATA%\Claude\Logs\main.log records every file operation of the session (`[remote-file] staged ...`, `[remote-file] committed ...`) between 01:02 and 01:23, but does not record a single one of the four app-access requests made in that same window. Nothing is logged when the approval card is shown or denied.

The bridge itself is healthy: device_list_dir, device_stage_files, device_commit_files and computer_resolve_access all work throughout.

WORKAROUND THAT DOES WORK

Creating a new task (a create_trigger routine with requires_local_device: true and the folders attached) and letting it run in a fresh session: there the app-access request works normally and the apps can be granted. Nothing else recovers it inside the original conversation.

PROBABLY RELATED

#64433 — "Desktop local-agent: 900s session idle timeout tears down the computer-use connector and never re-registers it on resume". That report is macOS-only and describes the tools silently disappearing; here, on Windows, the tools remain callable, resolve still succeeds, and the approval card is still shown but arrives pre-decided as Deny, which is arguably worse.

IMPACT AND SUGGESTIONS

Two hours lost by a paying Max user chasing machine-side causes that were all irrelevant, because the card presents itself as a user decision when it isn't one.

1. Re-register the computer-use connector when a session resumes, or at least surface the connector's real state instead of rendering an approval card that cannot approve.
2. When the request cannot be granted, say so in the card ("this session's computer-use connector is no longer registered — start a new task") rather than showing Deny as the only button.

### What Should Happen?

The approval card should offer "Allow for this session" alongside "Deny", as it does in a fresh session, so the user can actually grant access to Word, Excel and Acrobat.

If the request cannot be granted at all — because the session's computer-use connector is no longer registered, or because the approval was routed elsewhere and timed out — the card should say so instead of rendering a single "Deny" button that looks like a user decision. A timeout should be reported to the agent as a timeout, not as a denial: that distinction is what sent us chasing machine-side causes for two hours.

Possibly the same underlying routing problem as #74405 (approval requests delivered to the phone and never properly shown on the desktop), but here on Windows the card IS shown on the desktop, only mutilated: it lists the apps and offers no way to approve them.

### Error Messages/Logs

```shell

```

### Steps to Reproduce

1. Start a Cowork session in the cloud, linked to a Windows machine (session started from the desktop app).
2. Work in that session for a while using only non-computer-use tools, such as file staging and commits through the device bridge.
3. Later in the session, call computer_resolve_access with the app names. It succeeds and returns the real bundleIds, tiers and the willHide list.
4. Call computer_request_access with those entries verbatim.
5. The approval card appears on the desktop listing the apps, with "Deny" as the only option; the tool call returns rejected. Repeating with a single app, without the terminal entry, after enabling the toggle, after restarting the app and after signing out and back in all give the same result.

### Claude Model

None

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

_No response_

### Claude Code Version

Claude Desktop 1.49585.0 (Windows), Electron 44.2.0, Node 24.20.0

### Platform

Anthropic API

### Operating System

Windows

### Terminal/Shell

Warp

### Additional Information

_No response_

Start by reproducing the cloud Cowork flow on Windows: run computer_resolve_access followed by computer_request_access after using the device bridge, then inspect %LOCALAPPDATA%\Claude\Logs\main.log for the missing request and approval events. Compare the original session with a fresh task where access succeeds; done means the card offers approval and the tool reports the granted result, or clearly identifies an unavailable session.

Rédigé par le modèle d'indexation à partir du texte de l'issue.