app-access — Claude Code prompt for app permissions
This prompt for Claude Code governs how the agent handles app access settings. It applies when an app is blocked or an access-related status appears.
Apache-2.0 ★ 9,488 updated 2026-11-16
.claude/commands/app-access.mdWhat app-access does
The prompt bars the agent from bypassing a ban on automatic app access. It must not retry, relaunch the app, or alter its permissions; instead, it can pursue another route to the task or explain where the user can enable access.
For Claude Code, the file path is .claude/commands/app-access.md. A screen shared by the user does not grant automatic access. If the target app cannot be identified, the agent observes again and asks the user if uncertainty remains. When settings need repair, it stops using phone tools; the user handles any authorization or sharing prompt.
What it helps with
- prevent an agent from bypassing an app access ban
- find another route when a required app is blocked
- tell an unidentified app apart from a blocked one
- leave authorization prompts for the user to handle
Example prompts for the agent
- Open the app and complete the task without bypassing its access settings.
- The app is blocked; find another way to complete this task.
- There is an authorization prompt on screen; ask me to handle it.
How to install app-access
Manually: put the files in place
.claude/commands/app-access.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about app-access
How do I install app-access in Claude Code?
Use the file path .claude/commands/app-access.md.
What does app-access do?
It sets rules for cases where app settings deny automatic access. The agent must not bypass the ban; it can use another route or explain that only the user can enable access.
What should the agent do if it cannot identify the app?
It observes the screen again, then asks the user if the target is still uncertain.
Source text
app-access.md · Apache-2.0
Application access Respect Application access settings. `app_blocked` means the user has forbidden automatic reading and operation of that app. Do not retry, relaunch, diagnose its screen, change its permissions, or use shell or another route to bypass the decision. Reconsider the plan: if another app, screen, share target or web route can achieve the same goal, continue there. If the blocked app is required, stop and explain that this app is disabled in Settings › Application access and they can allow it there. Never end with a bare failure, a raw error code, or the tool's English message. Only the user can change the setting. A user-shared screen does not grant automatic access. `app_access_unverified` means the target could not be identified, not that it is blocked: observe again to identify the app, and ask the user if it stays uncertain. `app_access_unavailable` means settings need repair: do not use phone tools, and tell the user to reset Application access in Settings. `app_access_protected` means the screen is an authorization or sharing prompt only the user may operate: ask the user to handle it.
© wangzan101 · Apache-2.0 · wangzan101/Mika