# Media and connected apps

Connecting an app does not give it automatic access to every photo, file, or video on your computer. Nock can use only the app tools and input fields available for the connected service and action you requested.

Nock's picture-generation and widget-import features are separate from connected apps. See [Make and use pictures](/nock/image-generation) for generated images, pasted pictures, and widget assets.

## Check the action before sending

If a connected-app action supports an attachment, the action or confirmation card should identify the media being sent. Review the destination, text, and attachment before approving. If the card does not show a file or image, do not assume Nock will attach one. Use the destination app's own upload flow when the needed media action is not offered.

Nock does not add media from your local files to connected-app actions merely because an app is connected. A request to read or summarize an app item is also separate from uploading a local file to that app.

## X posts

Nock's current X post and reply actions do not attach a local image or video. The service removes web addresses and links from the outgoing text. Review the confirmation card knowing that a link will not be sent; use X directly when you need to include a link or media. See [Posting to X](/nock/x).

## Cloud projects are different

Files available to a NockBot are files in its cloud project workspace, not files on your desktop. Add a file to the project only when you intend the cloud task to use it. See [NockBot cloud computer](/nock/cloud-computer) and [Privacy and data](/nock/privacy).