# Choose a workflow

Start with the result you want: text in a field, an answer, a file change, a small interactive tool, or a visual board. Nock exposes different workflows for those outcomes. The examples below are instructions to try when the feature is available in your build; they are not recorded demonstrations or guarantees of a particular result.

## Put your words into another app

Choose [Dictation](/nock/dictation) when you already know what to write. Click a text field, hold **Fn / Globe**, speak a short sentence, and release. The expected result is a transcript inserted into that field.

Review the words before submitting them. Dictation is not an instruction to the agent to carry out the sentence. If text misses the field, use [Paste last transcript](/nock/paste-last) after restoring focus.

## Improve text that already exists

Choose [Selected text](/nock/selected-text) when the source text is already in a supported editable field. Select a paragraph, use Agent Mode, and ask for a specific change such as “Make this paragraph shorter while keeping the dates.”

Check the replacement in the original app. If it is wrong, use that app's Undo. For a message draft, inspect whether Nock produced a draft card or performed an edit; neither should be confused with a confirmed send.

## Ask a question or investigate what you see

Choose [Agent Mode](/nock/agent-mode) for explanation or a task. Hold the configured agent shortcut, ask the question, and release. If the subject is a particular screen element, use [Pointing](/nock/pointing) and describe what you need to understand.

Look for a response or result card, and answer any pending approval deliberately. If screen access is unavailable, provide the relevant text yourself. A voice acknowledgment is not proof that an external action completed.

## Change a code project

Use [Coding agents](/nock/coding-agents) for a bounded project task. Name the project, describe the desired change, and specify checks, for example: “In this project, investigate why the settings test fails, propose a focused fix, and run that test.”

Expect a task surface with progress, questions, and a result. Inspect the actual diff and test output before accepting the work. Use the task's stop control to interrupt work; starting a new conversation does not automatically stop a running worker.

## Make a small interactive tool

Use [Widget builder](/nock/widget-builder) for a compact utility such as a timer or calculator. Describe the controls and expected behavior, inspect the preview, test it, and keep it when satisfied. A preview with sample data is not evidence of a live service connection.

For a richer saved preview, explore [Studio](/nock/studio). Verify data sources and connection access separately from the appearance of the generated interface.

## Arrange information visually

Use [Glass Canvas](/nock/glass-canvas) for a board containing notes, links, drawings, and other supported items. Make a board, add a small set of content, then use [Canvas workflows](/nock/canvas-workflows) to organize or export it.

Inspect exported content before sharing; it may include private material or remote embeds. Choose a saved copy before a large revision when you need to preserve the earlier board.

If an expected step is unavailable, check [Account](/nock/account), [Availability](/nock/availability), and the workflow's troubleshooting guide before switching modes at random.