claude-code - 💡(How to fix) Fix Feature request: pre-approve apps for computer-use MCP in remote/unattended sessions [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46907Fetched 2026-04-12 13:29:57
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×2

Code Example

{
  "computerUse": {
    "preApprovedApps": ["Finder", "Notes", "Maps"]
  }
}
RAW_BUFFERClick to expand / collapse

Currently, request_access requires interactive approval every session — there's no way to pre-grant access to specific apps via config. This blocks computer-use in remote/unattended workflows (e.g., scheduled tasks, remote control).

Request: Add a settings option (e.g., in settings.json or .mcp.json) to pre-approve a list of apps for computer-use, so sessions can start without manual dialog interaction.

Use case: Running Claude Code remotely (e.g., via /remote-control or scheduled agents) where the user isn't at the keyboard to click "Allow" on the native approval dialog.

Suggested approach: A config like:

{
  "computerUse": {
    "preApprovedApps": ["Finder", "Notes", "Maps"]
  }
}

This would skip the request_access dialog for listed apps while preserving the security gate for unlisted ones.

extent analysis

TL;DR

Implement a configuration option to pre-approve specific apps for computer-use, allowing sessions to start without manual dialog interaction.

Guidance

  • Introduce a new setting in settings.json or .mcp.json to store a list of pre-approved apps for computer-use.
  • Update the request_access logic to check this new setting and skip the approval dialog for listed apps.
  • Ensure the new setting is properly validated and sanitized to prevent security vulnerabilities.
  • Consider adding a fallback mechanism to handle cases where the new setting is misconfigured or empty.

Example

{
  "computerUse": {
    "preApprovedApps": ["Finder", "Notes", "Maps"]
  }
}

This example illustrates the proposed configuration format for pre-approving specific apps.

Notes

The implementation should carefully balance security and convenience, ensuring that the pre-approval mechanism does not introduce unintended vulnerabilities.

Recommendation

Apply a workaround by implementing the proposed configuration option, as it addresses the specific use case of running Claude Code remotely without requiring manual approval.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING