Talk to your agent: voice in, spoken pings out

Video 2 min 5 secAbout 25 min to do
Not startedSession 2 of 7, 0 done · Next up: Build the apps you used to buy (Mac, Windows, web)

Chapters

Shortcuts
  • Space or Kplay and pause
  • Left and Rightback and forward 5 seconds
  • J and Lback and forward 10 seconds
  • , and .step one frame
  • Shift + , and .slower and faster
  • 0 to 9jump to that tenth
  • Ffullscreen
  • Mmute
  • Ccaptions

Shortcuts stay out of the way while you are typing a note.

Lesson notes and steps

The written version of this session, with the commands and templates to copy.

In the last session you installed your agent. Now fix the two slowest parts of using it. Typing long, detailed prompts is slow, and most people then sit and watch the terminal scroll while the agent works. That is wasted time.

Two upgrades fix both: speak your prompts instead of typing them, and make the machine speak (or ping) when the agent finishes. By the end of this lesson you can start a job by talking, walk away, and hear "Your agent is done" from across the room.

What you will use

  • The agent you installed in session 1 (Codex, Claude Code, or Grok Build)
  • A Mac with built-in Dictation, or a Windows 10/11 PC with voice typing
  • A microphone (the one built into your laptop is fine)
  • 10 minutes to set two things and test them

Step 1: Turn on Dictation on your Mac

macOS has Dictation built in, and it works inside Terminal. Open System Settings and look under Keyboard for a Dictation section. Apple moves these menus around between macOS versions, so if it is not exactly there, type "Dictation" into the search box at the top of System Settings.

Turn Dictation on, then set the shortcut. The options include pressing a single key twice (Control twice is a common one). Pick something you can hit without looking.

Now test it. Start your agent in Terminal (codex, claude, or grok), hit your Dictation shortcut, and talk your prompt instead of typing it. Your words appear at the prompt. Stop dictating (usually the same shortcut or the Escape key, depending on your macOS version), then press Enter to send.

Do not try to speak like a programmer. Long, rambling spoken prompts are fine; agents handle them well. A shop owner can say: "Look at the sales CSV in this folder and give me the top ten products by revenue this month, put it in a file called top products, and flag anything that dropped more than twenty percent." A nonprofit director can say: "Read the volunteer signup spreadsheet and draft a short welcome email for each person who joined this week." Both of those would take two minutes to type and fifteen seconds to say.

Step 2: Turn on voice typing on Windows

Windows has the same thing under a different name. Click into the PowerShell window where your agent is running, press Win + H, and voice typing starts listening. Speak your prompt, and it types into PowerShell wherever your cursor is. Press Win + H again (or click the microphone) to stop, then Enter to send.

Same rule applies: talk naturally, in full sentences, with all the detail you would put in a good typed prompt.

Step 3: The quick "tell me when you are done" trick

macOS ships with a say command that speaks any text out loud. That gives you a done-ping with zero setup, two ways:

  1. Put it in the prompt. End your request with: "When you finish everything, run this command: say 'All done'." The agent runs it as its last step.
  2. Chain it yourself. If you run a long command directly, append it: python import_donors.py && say "import finished".

Example: "Build me a one-page price list from prices.csv, and when you finish, run: say 'Price list is ready'." Then go help a customer or return a call. The computer will tell you when to come back.

On Windows there is no say, but PowerShell can beep. This one-liner works in the prompt trick above:

[console]::beep(800,400)

Step 4: The proper way in Claude Code: a Stop hook

Asking for the ping in every prompt gets old. Claude Code supports hooks: commands that run automatically on certain events. A Stop hook runs every time the agent finishes responding. Put this in ~/.claude/settings.json (create the file if it does not exist):

{
  "hooks": {
    "Stop": [
      {
        "hooks": [
          { "type": "command", "command": "say 'Your agent is done'" }
        ]
      }
    ]
  }
}

Now every job, big or small, announces itself when it lands. On Windows, replace the say command with a beep:

{ "type": "command", "command": "powershell -c [console]::beep(800,400)" }

Do not want to edit JSON by hand? Ask the agent itself: "Add a Stop hook to my ~/.claude/settings.json that runs say 'Your agent is done'." Then restart Claude Code and test it.

If a spoken announcement is too much (shared office, sleeping baby), Claude Code also has a quieter terminal bell option. Type /config inside Claude Code and look for the notification preferences; the exact wording shifts between versions, but a bell or notification setting is what you are looking for.

Step 5: Codex and Grok Build

Codex and Grok Build each have their own settings and add notification features quickly, so check their docs or settings screens for hooks or notifications. Either way, the Step 3 trick works everywhere: end your prompt with "when you finish, run: say 'done'" (Mac) or the PowerShell beep (Windows), and any agent will ping you.

You are done when...

You can start your agent, hit one shortcut, speak a full detailed prompt without touching the keyboard, send it, walk away, and hear the machine announce that it finished. Test it with a real job: have it summarize a folder of documents or draft five emails, and leave the room while it works.

This matters in the next sessions, when you will hand your agent jobs that run for many minutes at a time. The habit you just built (speak the job, leave, come back when called) is how you run those without babysitting the terminal.


Template included: Members get a printable cheat sheet with the Mac Dictation and Windows voice typing setup steps, the say and beep one-liners, the ready-to-paste Stop hook JSON for Claude Code, and five example spoken prompts to try. Find it in your member dashboard under Templates.

Want it done for you?

Short on time? Agentic Quarks will implement this end to end, wired into your stack, and hand you the keys.

Implementation engagements from $2,500
Narration transcript (what the video says)

Typing long prompts is slow, and watching the terminal while your agent works is wasted time. This session gives you both upgrades: speak your prompts out loud, and make the agent speak up when it finishes.

On a Mac, the built-in Dictation works right inside the terminal. Turn it on in keyboard settings and pick a shortcut you can hit without looking. Then start your agent, hit the shortcut, and just talk. Rambling is fine. Agents sort it out.

On Windows, press the Windows key plus H and voice typing drops your words straight into PowerShell. Same idea: open your agent, tap the shortcut, and speak the prompt instead of typing it.

Now the other direction. Tell your agent: when you finish, run the command that says All done, out loud. The Mac speaks with a built-in command called say. One sentence in your prompt, and the machine announces itself.

The permanent version is a hook: a tiny setting that runs a command every time your agent finishes responding. Set it once and every session pings you, no reminders needed. The lesson below has the exact snippet to paste, for Mac and for Windows.

Using Codex or Grok Build instead? The chained say command works everywhere, and each tool has its own notification settings worth two minutes of looking. The habit is the point: no more babysitting the terminal.

Put it together and your working day changes shape. Start a big job by voice, go do something that matters, and the machine calls out when it is ready for you. That loop gets more valuable with every session in this course.

You are done when you have spoken one prompt instead of typing it, and heard your machine announce a finished job. Members get the printable cheat sheet with the shortcuts, the one-liners, and the hook snippet.

This is session two of Your AI Coding Agent. Next up: building the apps you used to buy, with the agent you can now run by voice. The full written walkthrough is below.

The course this session belongs to

What you will build in Your AI Coding Agent

Install an agent, then make it build, watch, and guard for you

7 sessions, 17 min of video, about 4.5 hours to do, 2 free.

  1. 01Install your AI coding agent (Mac or Windows)Free2:09 video
  2. 02Talk to your agent: voice in, spoken pings outFree2:05 videoYou are here
  3. 03Build the apps you used to buy (Mac, Windows, web)Member2:28 video
  4. 04Slash commands: save your best promptsMember2:32 video
  5. 05Parallel agents and subagent teamsMember2:33 video
  6. 06Borrowed experts: code, security, and legal reviewMember2:37 video
  7. 07Do not get prompt injectedMember2:33 video
About Your AI Coding Agent

Cancel anytime from your account page, and a 14-day money back on your first month that you trigger yourself. Prefer to pay once? Lifetime All-Access is $399.

By purchasing you agree to the Terms and the Refund Policy.

Members share their results from this session in the community. See what is included.