CourseGuidesArticlesPodcastGitHubAboutStart free course
Course/Claude Code Everywhere

5 min · +90 XP

Build by voice on the go

Short spoken requests from the phone, a check of the result, and when to say No.

By the end of this lesson

You will be able to send a short spoken request from your phone, check what Claude did and refuse actions you cannot see properly.

Away from the keyboard, speaking is often faster than typing on a phone. In the chat with your session, tap the microphone key on the phone's keyboard, say the request, read the text it produced and send it. Claude receives it like any typed message.

🎙From a café

This is how the request can sound if you dictate it:

“Add a weekly view to my habit tracker. Check that it works with three test entries, and tell me in two sentences what changed.”

A spoken request that works

  1. 1One task per message. A long paragraph with five wishes is hard to check later.
  2. 2Say what to change and where: "in the habit tracker", "on the main page".
  3. 3Say how Claude should check it: "open the page and confirm the chart shows three entries".
  4. 4Ask for a short report: "tell me in two sentences what you changed".
  5. 5Read the dictated text before sending. Dictation sometimes mishears file names and commands.
For beginners
›Dictation on the phone

Most phone keyboards have a microphone key. Tap it, speak, tap it again to stop, and the words appear as text in the message field. Correct a wrong word by tapping it and typing. If there is no microphone key, voice typing may be switched off in the phone's keyboard settings.

Check the result from the phone

Ways to see what happened

  1. 1Read Claude's summary in the chat.
  2. 2If the project is a git repository, the diff pane on the phone shows which lines changed.
  3. 3Ask for a check you can read on a small screen: "run the tests and tell me how many passed".
  4. 4Leave large reviews for when you are back at the computer.
!When the phone screen is too small

When Claude asks permission for a command you cannot read in full on the phone, or do not understand, answer No and ask for an explanation. Do not approve deleting files, publishing to a server or anything involving payments from the phone. Those can wait until you see the whole picture on the computer.

💬 After you answer No

“Explain in simple words what this command does and what it changes. If there is a safer way that does not need my approval from the phone, use it; otherwise wait until I am at the computer.”

Claude explains, finds another way or waits; nothing runs that you did not understand.

For experienced users
✦If you are experienced

At the computer, /voice turns on dictation in the CLI: hold Space and speak, or /voice tap to tap once to start and again to send. It needs a claude.ai account and a local microphone, does not work in cloud or SSH sessions, and does not count toward /usage limits. Remote Control sessions offer Manual, Accept edits, Plan and Auto from the app; bypass cannot be selected there. Auto keeps routine questions away while risky actions are still checked, which suits phone work.

Quick check

On the phone, Claude asks to run a long command that you can see only partly. What do you do?

Facts checked against the official Claude Code docs October 24, 2026 · source

EAEvgenii Arsentev

Author

Evgenii Arsentev

PhD · Chief Executive Officer, digital health