claude-code - 💡(How to fix) Fix Add setting to auto-approve computer-use request_access prompt [1 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#47796Fetched 2026-04-15 06:42:06
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Fix Action

Workaround

Currently forced to use Playwright MCP for web tasks only, losing the ability to interact with native macOS apps.

Code Example

{
  "computerUse": {
    "autoApprove": true,
    "allowedApps": ["Google Chrome", "Safari", "Finder"]
  }
}
RAW_BUFFERClick to expand / collapse

Feature Request

Problem

When running Claude Code in a non-interactive environment (e.g., a tmux session with --dangerously-skip-permissions and --channels for a Telegram bot), the request_access prompt from the computer-use MCP blocks the entire session indefinitely. There is no way to pre-approve app access, so the bot hangs waiting for user input that will never come.

Current behavior

  • --dangerously-skip-permissions bypasses all standard tool permissions ✅
  • request_access from computer-use still requires an interactive approval per session ❌
  • No setting in settings.json or settings.local.json can skip this prompt
  • This makes computer-use completely unusable in any headless/unattended Claude Code setup

Proposed solution

Add a configuration option such as skipComputerUseApproval: true in settings.json or a CLI flag (e.g., --approve-computer-use) that pre-grants access to specified (or all) applications, removing the need for interactive confirmation.

Example config:

{
  "computerUse": {
    "autoApprove": true,
    "allowedApps": ["Google Chrome", "Safari", "Finder"]
  }
}

Use case

Running Claude Code as a 24/7 autonomous agent (via tmux + Telegram plugin) on a dedicated Mac mini. Computer-use is needed for native app automation, but the interactive prompt makes it unusable in headless/unattended mode.

Workaround

Currently forced to use Playwright MCP for web tasks only, losing the ability to interact with native macOS apps.

extent analysis

TL;DR

Add a configuration option to pre-grant access to specified applications, removing the need for interactive confirmation in non-interactive environments.

Guidance

  • Consider adding a skipComputerUseApproval flag in settings.json or a CLI flag like --approve-computer-use to bypass the request_access prompt.
  • Evaluate the proposed computerUse configuration example to determine if it meets the requirements for pre-granting access to specific applications.
  • Investigate the feasibility of implementing a whitelist of allowed applications to ensure security while enabling automation in headless mode.
  • Assess the trade-offs of using Playwright MCP for web tasks versus implementing a solution for native app automation using computer-use MCP.

Example

{
  "computerUse": {
    "autoApprove": true,
    "allowedApps": ["Google Chrome", "Safari", "Finder"]
  }
}

This example configuration suggests a possible implementation for pre-granting access to specific applications.

Notes

The proposed solution requires careful consideration of security implications to avoid unintended access to sensitive applications or data. The --dangerously-skip-permissions flag already bypasses standard tool permissions, so adding another flag or configuration option must be done with caution.

Recommendation

Apply a workaround by implementing the proposed computerUse configuration or a similar solution to pre-grant access to specified applications, as upgrading to a fixed version is not mentioned in the issue. This approach allows for automation in headless mode while minimizing security risks.

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