[BUG] No way to "Allow all domains" for `WebFetch` and `WebSearch` from mobile Remote Control session
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?
The WebFetch permission prompt only offers per-domain approval ("Yes, and allow all" -- the"all" seems to mean all requests on that domain, not all domains). Any research task that follows links across hosts therefore re-prompts on every new domain. This makes the session completely unusable.
The equivalent rule already exists — WebFetch(domain:*) — but today you can only get it by hand-editing ~/.claude/settings.json or changing permissions in the local host app, which is not reachable from the mobile app or from a Remote Control session. That makes it effectively unavailable to anyone who steps away from their machine mid-task.
Quick Fix: add another option to the WebFetch dialog — "Yes, and allow all domains" — writing WebFetch(domain:*) to .claude/settings.local.json, the same way the existing option writes the single-domain rule.
Context: hit this on iOS driving a Remote Control session, where Auto mode isn't selectable from the app and the settings file isn't editable, so there was no way to stop the prompts without returning to the machine.
What Should Happen?
iOS app should let me allow all WebFetch and WebSearch requests in one dialog.
Error Messages/Logs
Steps to Reproduce
- Fresh install of the MacOS App.
- Enable Remote Control from iOS App.
- Open Remote Control session from iOS
- try a research request that triggers
WebSearchacross many domains. - Dukkha.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.2553.1 (Electron 44.2.0, Node 24.20.0, macOS arm64)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗