# Desktop actions On supported macOS builds, **Settings → Agent → Actions** controls native desktop actions. These include editing selected text, drafting replies, creating prompts, reminders, music and volume, opening apps, and screen context. ## Enable only what you need Review the switches before your first action. **Draft replies** starts off in the current candidate; other actions have their own defaults. Turning off an action removes that capability from the intended agent tool path. It does not revoke an unrelated app's operating-system permissions. ## Know what the result means | Request | Expected result | | ------------------- | ------------------------------------------------------------------------------- | | Draft a reply | An editable draft/card and clipboard text, not an automatically sent message. | | Create a prompt | A staged prompt you can inspect and paste yourself. | | Edit selected text | Replacement in the selected editable field; review it in the destination app. | | Open an app or site | An attempt to open the named installed app or address. | | Control music | Playback or volume action against a supported running player or system control. | | Explain the screen | Screen context for the model when permission and feature access allow it. | For edits, use the destination app's Undo if the replacement is wrong. For a drafted message, review the recipient and text before you send it yourself. ## When an action fails Read the card's error. Confirm the app is installed, the intended field has focus, and the necessary permissions are granted. If screen context is unavailable, give a description rather than assuming Nock saw it. Repeating a request without checking the previous outcome can cause duplicate actions. Native execution happens on the computer, but your request, relevant selected text, or a requested screenshot can be sent to the model. See [Privacy](/nock/privacy). Continue with [Selected text](/nock/selected-text), [Pointing](/nock/pointing), and [Reminders](/nock/reminders).