Skip to content
Start here

POPULAR GUIDES

    FROM THE DOCUMENTATION

    Open this guide ↗
    ↑ ↓ select ↵ open esc closeV3Code Docs
    Nock · Your workspacenock

    Task approvals

    ↗ View as Markdown

    Review Nock's action cards and keep them separate from coding-agent permission prompts.

    Nock may pause before a consequential action and show an approval card in the notch. Read what it wants to do, the target or destination, and why it is asking before choosing Accept or Reject.

    This page covers action cards for Nock’s own voice agent and connected-app actions. It does not describe Settings → Agent → Coding agent permissions, which controls supported Claude Code and Codex runs; see Coding permissions. A coding chat question, a Team inbox message, and a Nock action card each have their own controls.

    Each pending action appears with a short explanation. Select or click the explanation for more detail. If several actions are waiting, review each row; Accept all and Reject all apply to the entire visible queue, so use an individual control when you mean one action only.

    For a connected-app action with editable fields, check its destination and content—such as an email recipient, subject, and body. Make any edits before confirming. Nock may show Applying your edits… while it prepares the revised action, followed by a sending or completion status. Check the destination service after a consequential action.

    While an action is actually waiting, hold Nock’s talk shortcut and say a clear answer such as “yes” or “no.” Without all, the answer applies to the oldest pending action. If several unrelated actions are open, use the card’s buttons so you can choose the exact one.

    “No, send it to my manager instead” is a new instruction, not a simple approval. Reject the pending action, then give Nock the changed request. General praise such as “looks good” does not approve an action.

    Reject declines the action. Nock is told it was rejected and stops that request rather than trying another way to do the same thing. Stop or Escape cancels the request and its waiting actions. Neither can undo an external action that already completed.

    An unanswered Nock action card expires after ten minutes and is declined. The expired card says Expired — declined for you. If you still want the action, ask again after checking whether any earlier step succeeded.

    • Nock action approval: an action from Nock’s own voice agent, shown in the notch.
    • Coding-agent permission: a prompt from Claude Code or Codex, governed by Coding permissions.
    • Coding-task question: a question in a background coding task Nock started. The optional Answer for me after 2 minutes setting may choose a non-sensitive answer; it never approves an action. It does not answer questions in found chats or agent-helper chat windows. See Coding permissions.
    • Coding-chat question: a specific choice asked by an existing chat; answer it in its window or tell Chat Manager which choice you mean.
    • Team message: a message held for you in Settings → Team → Messages. Use Keep in inbox to mark it reviewed without sending it, or Send to chat to deliver it to the selected conversation. See Shared chats.
    • Widget action: a control inside a widget may show a separate system confirmation before it runs. Read that dialog as well.

    Some settings or local-program changes use a macOS confirmation dialog instead of an ordinary action card. Approving one kind of prompt does not approve another. See Nock permissions and Coding task troubleshooting.