How can I dictate coding prompts without changing paths and identifiers?

Quick answer — November 3, 2026: Speak the task and its constraints, then type or copy exact paths, identifiers and code when needed. With Dictop on Mac, use narrow replacements for recurring recognition errors and on-demand Paste with Edit text before pasting for review. Leave optional AI cleanup off or constrain it carefully. Check the finished prompt before sending; exact transcription is not guaranteed.

Coding requests often mix easy-to-speak explanations with details where one character matters. You can describe a bug, explain the expected behavior and list exclusions aloud, then add literal references from your editor. Use Dictop to enter the request in supported assistant and editor fields, then use the destination’s own controls to attach files or send it.

Speak the task, then add exact references

For an illustrative project, your finished request might read:

In src/auth/session.ts, update refreshSession so an expired token returns the existing signed-out state. Do not rename SessionState or change the public API. Explain the change and suggest a focused test.

Dictate the behavior and negative constraint first. Add the path and symbol spellings from the repository, or correct them in the review editor. Type literal slashes, underscores, backticks, brackets or command flags manually whenever recognition leaves them uncertain. Speaking “session dot T S” does not guarantee session.ts.

You can also select a file through the destination's own controls. Cursor's prompting documentation describes typing @ to choose file or folder context. Claude Code's interactive documentation documents @ file-path autocomplete. Use those controls directly when you need a file reference; a spoken filename alone need not create an attachment or mention.

Use replacements for recurring mistakes

If your recordings repeatedly turn a fictional identifier refreshSession into “refresh session,” a literal replacement for that observed phrase can restore its spelling. Start with the actual recognized wording and check a few sentences before relying on the rule.

Keep replacements narrow. A rule replacing every occurrence of “session” could alter ordinary explanations as well as symbols. Dictop applies replacement rules after recognition and before optional AI refinement. They transform text; they do not train the recognizer or protect a corrected identifier from later rewriting. See custom words and replacements.

Keep optional cleanup limited to editing

For a prompt containing exact technical details, leaving AI refinement off gives you fewer transformations to review. If you enable it, try an editing instruction such as:

Edit this transcript as a request for a coding assistant. Correct grammar and punctuation only. Preserve negations, names, paths, identifiers, literal code, numbers and scope constraints exactly. Do not answer the request, perform the task, or add requirements. Return only the edited request.

Try the instruction on a short recording, then check whether “do not rename” survived and whether a tentative suggestion became a requirement. Review the result even with these instructions in place.

With history enabled, on-demand recordings retain Original text and Replaced and AI-refined versions when present. The refined version is labeled LLM. Comparing them can show whether a mistake began in recognition, a replacement or refinement. Continuous mode saves processed text without those separate stage versions.

Review before insertion and before sending

Choose on-demand recording, select Paste delivery and enable Edit text before pasting. Continuous mode bypasses this editor, and Type and Copy delivery do not open it. Turn off Press a key after insertion: that optional setting can send Return or another key after pasting or typing.

In the editor, check the path character by character, identifier capitalization, requested behavior and every exclusion. For the example, confirm src/auth/session.ts, refreshSession, SessionState and “Do not.” Choose Paste, Copy or Cancel. Review edits affect delivery, not the saved transcript versions.

Before recording, focus the intended prompt field. Automatic insertion needs macOS Accessibility permission and depends on the destination field's behavior. In a terminal, confirm the coding assistant's prompt is active before pasting. If insertion is unreliable, select Copy delivery, then focus the intended field and paste manually.

Check the inserted text and submit it yourself when ready. Keep insertion and submission separate; do not rely on a dictated instruction to prevent sending. The review-before-pasting guide explains the checkpoint, and Dictop for Mac covers the app.