PromptDC permissions

PromptDC Desktop requires macOS Accessibility for its shortcut and synthetic keystrokes. Selection reads and synthetic Cmd+V paths that use System Events also require separate Automation access.

Automation is not requested during onboarding. macOS prompts when a System Events path first needs it. Chrome needs no Accessibility permission, and Windows uses UI Automation plus a SendInput bridge without an OS permission prompt.

Last updated: August 2026

Desktop on macOS

Needs Accessibility and, for System Events paths, separate Automation access.

Windows

Needs no permission prompt, UAC approval, or administrator access.

Screen Recording

Not requested or used on any PromptDC Desktop path.

macOS Accessibility for Desktop

Why it is needed

The desktop workflow crosses application boundaries. Accessibility enables the global shortcut and synthetic keystrokes used to capture selected text and place an approved result into the source app.

Onboarding checks Accessibility. Automation is separate and appears later when macOS first asks whether PromptDC may control System Events.

When it is used

The selected-text workflow starts when you use the general enhance shortcut. PromptDC captures the selection, runs the enhancement, and uses synthetic keystrokes again if you choose Replace.

System Events paths use Automation for accessibility-API selection reads and synthetic Cmd+V. Copy remains available when replacement cannot proceed. See Desktop setup for the end-to-end workflow.

Grant access during setup

PromptDC uses a desktop runtime that requires macOS 12 or later. System Settings wording can vary slightly by macOS version.

  1. 01

    Reach Finish setup

    Continue through onboarding until the Finish setup page says Enable Accessibility to use the selection shortcut.

  2. 02

    Choose Enable access

    If macOS does not grant it directly, PromptDC opens the Accessibility settings page.

  3. 03

    Open Accessibility settings

    In System Settings, open Privacy & Security, then Accessibility. Unlock the settings if macOS asks.

  4. 04

    Turn PromptDC on

    Find PromptDC and turn it on. If PromptDC is missing, add the app from Applications, then enable it.

  5. 05

    Return to onboarding

    PromptDC checks the permission repeatedly, so the status should change to Accessibility is on.

  6. 06

    Verify capture

    Finish setup, select text in another application, and run the general enhance shortcut to verify capture.

Reset a stale grant

Use this when access looks enabled but PromptDC can no longer read a selection or replace text.

  1. 01

    Quit PromptDC

    Quit from its menu-bar menu. Confirm the menu-bar icon disappears.

  2. 02

    Open Accessibility

    Open System Settings, Privacy & Security, then Accessibility.

  3. 03

    Turn PromptDC off

    If the settings provide a remove control, remove the PromptDC entry so macOS can create a fresh grant.

  4. 04

    Launch PromptDC again

    Open Accessibility settings from the in-app warning if it appears.

  5. 05

    Add or enable PromptDC

    Return to the app. The warning should clear after macOS reports access.

  6. 06

    Retry with a fresh selection

    Open another application, select fresh text, and press Cmd+Shift+E. Confirm the review popover receives the selected text.

Automation, Screen Recording, and Windows

Automation is separate

PromptDC does not request Automation during onboarding. macOS surfaces it when PromptDC first needs to control System Events.

Apple event error -1743

Open System Settings, Privacy & Security, Automation. Allow PromptDC to control System Events, reopen PromptDC if needed, and retry with a fresh selection.

No Screen Recording

PromptDC does not request or use Screen Recording. You do not need to grant it for capture, review, or replacement.

Windows needs no elevation

Windows shows no permission prompt and needs no UAC or administrator access. PromptDC uses UI Automation and a SendInput bridge. For other failures, see desktop troubleshooting for app-specific checks.

Chrome extension permissions

Chrome needs no Accessibility or Automation permission. It requests storage, tabs, sidePanel, identity, alarms, scripting, and contextMenus. It does not request clipboardRead, clipboardWrite, or activeTab.

storage

Stores extension state such as settings, profiles, active hostname rules, disabled hostnames, session data, and local provider configuration.

tabs

Identifies the active tab and its hostname so PromptDC can open the side panel in the correct window, apply hostname rules, and update the site's enable or disable menu.

sidePanel

Opens PromptDC's Chrome side panel for enhancement, settings, profile management, and library views.

identity

Supports account sign-in. The declared OAuth scopes are openid, email, and profile, which let PromptDC identify the signed-in account.

alarms

Schedules periodic background account and profile synchronization, including session refresh checks.

scripting

Injects or restores the PromptDC page script and styles when the extension needs to provide its toolbar and selected-text controls on a web page.

contextMenus

Adds right-click commands for enhancing a selection, saving selected text to the library, and enabling or disabling PromptDC for the current site.

What Chrome host access means

PromptDC declares <all_urls> as its host permission. This is broad page access, not an allowlist or a claim that every website has been tested.

Declared host access

The extension declares <all_urls>. This is broad host access, not a list of tested or recognized websites.

Frame coverage

The content script runs in all frames so PromptDC can reach editable fields inside regular page frames.

Clipboard and tab scope

PromptDC does not request clipboardRead, clipboardWrite, or activeTab. It uses its declared extension permissions and page content script instead.

The broad website pattern is what lets PromptDC work in text boxes across regular websites rather than on a closed list. Recognized coding hosts are a separate concept used for Code profile selection.

Chrome restricts extensions on browser-owned pages such as chrome:// pages and on some store pages. The toolbar cannot be injected there even though the manifest declares broad host access.

Commands and content scripts

Enhance focused field

The default is Ctrl+Shift+Space on Windows and Linux, or Command+Shift+Space on macOS. It tells the content script to act on the focused field or current selection.

Open side panel

Chrome also registers an Open the PromptDC side panel command. You can assign or change it from chrome://extensions/shortcuts.

Neither command creates profile-specific bindings. Choose the profile from the toolbar or side panel. See the shortcut reference.

Control Chrome behavior by site

Use Disable on this site from the floating toolbar to suppress PromptDC for a hostname. To reverse it, right-click the page and choose Enable PromptDC on this site.

Disabling a hostname changes PromptDC's saved toolbar state. It does not remove the extension's manifest permission. To change Chrome-level site access, use Chrome's extension details page, understanding that narrower access can prevent the toolbar from loading.

For provider key handling and per-surface setup, read the BYOK guide.

Permission FAQs

Setting up desktop?
Continue with Desktop setup

Using Chrome?
Open the Chrome guide

How data is handled?
Read Security

Write better with AI

Enhance any text you select on the desktop, on the web, in your editor or terminals.

Download PromptDC