Built-in browser (cloud session linked to Mac): "Always allow" site approvals don't carry over to new conversations (follow-up to #83604)

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Oct 7, 2026 · closed Oct 10, 2026

Preflight Checklist

  • [x] I have searched existing issues 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?

Follow-up to #83604 (closed as not planned/stale). Still happening, now on the built-in browser rather than the Chrome extension.

I use a cloud session linked to my Mac via the Claude desktop app. I click "Always allow" on every site prompt (around 70 job-board domains). In a new conversation I have to approve every one again. Approvals hold within a single conversation but do not carry over to the next one.

What Should Happen?

Sites approved with "Always allow" should stay approved until I revoke them in Settings, across conversations.

Error Messages/Logs

Steps to Reproduce

  1. Open a conversation in the desktop app linked to a Mac, using the built-in browser.
  2. Visit a number of sites and click "Always allow" on each approval prompt.
  3. Confirm they work for the rest of that conversation.
  4. Start a new conversation and visit the same sites.
  5. Every site prompts for approval again.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

N/A - Claude Desktop 2.26454.0 (macOS Tahoe 26.1)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Claude Desktop 2.26454.0 on macOS Tahoe 26.1. This is the desktop app (built-in browser, cloud session linked to the Mac), not the Claude Code CLI. Impact: recurring browser tasks across the same set of sites are impractical, because each new chat needs dozens of manual approvals. Related: #83604, #74715.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗