# Troubleshoot screen context

Screen context needs three things: the intended capture gesture, access to capture the screen, and an agent path that accepts the image. Check the attachment you can see before assuming the model received it.

## No drawing trail appears

Use the agent shortcut, **Control + Option** by default, rather than Fn dictation. Hold it long enough to start a voice request and move the pointer. On the current macOS gesture path, movement draws while no mouse button is held; pressing a button preserves dragging instead.

Check your configured Agent Mode keys in **Settings → General**. If the notch itself does not react, diagnose the [keyboard shortcut](/nock/keyboard-shortcuts) first. Screen Recording permission cannot fix a key event that never reached Nock.

## The request has no image

A nearly stationary pointer does not count as a drawing. This keeps an ordinary spoken request from attaching a full-screen picture. Make one clear circle or use **Point at something** in Nock's own composer to select a region deliberately.

Look for the captured-region thumbnail or attached-context chip. If you clicked its close button, that attachment was removed. Region context is used once and expires after a few minutes, so make a fresh capture after waiting or changing the page.

Do not rely on an old screenshot to describe the current state of a dialog. Capture again after an error changes, a page scrolls, or an app navigates.

## Captures are blank or incomplete

Open **Settings → Permissions** and review Screen Recording. Follow macOS's instructions if it requires reopening Nock after a grant. Test a normal window with non-sensitive content before trying a protected or unusual surface.

If you use several displays, put the pointer on the display containing the target before drawing. Keep the first reproduction to one display and one small area. The implementation limits captures per turn and may omit a capture that was not ready in time.

## Small text is misread

Nock resizes images before sending them. Tiny text on a high-resolution display can become difficult to read even when capture worked. Zoom the source app, crop to the relevant area, or use [selected text](/nock/selected-text) when the text can be highlighted. For exact identifiers or error strings, paste the text with your question.

## A connected agent ignores the picture

Different agent paths can accept different context. The macOS drawing behavior does not promise that every external or remote agent receives screenshots. Retry in Nock's own chat and confirm the attachment there; describe essential details in text if that integration cannot consume an image.

## Report the smallest safe example

Include your app/macOS version, display arrangement, gesture used, whether an attachment appeared, and whether the image was blank or merely unreadable. Remove private content from any example screenshot. See [pointing](/nock/pointing) for the intended flow and [permissions](/nock/permissions) for grants.