# Talk to the agent

Hold **left Control + left Option**, say what you want, then release. Nock sends the recognized request to the selected agent and presents the answer in the notch. Spoken replies depend on your voice settings and available access.

## Make a clear request

Start with an action and enough context: “Summarize this paragraph in three bullets” or “Help me understand this error.” Highlight text or circle the relevant screen area when the request depends on something visible.

A quick tap opens the chat box for typing. In that box, Return sends and Shift + Return adds a line. The mic button can dictate into the composer without sending immediately, which gives you a chance to review the words.

## During a voice request

Beginning a new recording interrupts Nock's spoken reply. **Escape** cancels the recording. Releasing finishes recognition; silence does not become an empty request.

If an approval card is waiting, a simple “yes” or “no” can answer it. Read the pending action before responding. For work that changes something, inspect the resulting card or output rather than assuming a spoken acknowledgement proves completion.

## Context and boundaries

Selected text and screenshots can accompany a request. A plain hold without drawing does not automatically attach a drawing screenshot. Some actions can request screen context when you ask about the screen and the feature is permitted.

Your words and attached context go to the agent and its model. Remote agents may support different context types; avoid assuming that every connected agent receives screen images.

## If it stalls

Check whether the notch is waiting for approval, whether your account has access, and whether recognition produced the intended words. Try a short text question to separate speech problems from agent connectivity. An agent recording is limited to five minutes and is discarded at the limit.

See [selected text](/nock/selected-text), [pointing](/nock/pointing), and [voice settings](/nock/voice-settings).

## Continue the right conversation

Before referring to “that result” or “the previous file,” check the chat currently shown in the notch. Selecting another chat or agent can change the context that receives the next request. State the target again when switching between unrelated tasks.

For a request that could change something outside the chat, name the intended destination and desired result. “Draft a reply I can review” and “send this reply” have different consequences. Review any approval card and the final result, particularly when using a connected app or a separate coding agent.

If work continues in the background, a short spoken response may only acknowledge that it started. Open its task or result card to see whether it completed, needs input, or failed. Repeating an action before checking can create duplicate work.