How to Use Claude Hands-Free for Notes and Work

Claude does not have a dedicated voice mode. What it does have is compatibility with any text input your device can produce, including dictation. Speak through your keyboard's microphone, let it transcribe, review the text, and send it as a normal message. For most hands-free tasks — capturing notes, dictating a draft, reviewing a list — that is enough.

The harder part is what comes after. A voice session ends and its decisions, follow-up tasks, and next steps need to go somewhere they can be found again. Tools like fenbs keep those tasks alongside the project brief, so the next session can start from a concrete point whether it is voice-based or not.

How to activate dictation for Claude

Dictation works differently by device and operating system. Set it up once, and it is available anywhere you can type:

• iOS: tap the microphone on the right side of the space bar on the default keyboard while the Claude message field is active. Speak; it transcribes in real time.
• Android: tap the microphone on Gboard or your installed keyboard. Some phones also offer a voice typing shortcut through accessibility settings.
• Mac: enable Dictation in System Settings > Keyboard. Press the shortcut (default: press the mic key or Fn twice) while the Claude text field is focused.
• Windows: press Win+H to open Voice Typing. Focus the Claude web app message field and speak.

Always review the transcription before sending. Technical terms, proper nouns, and long sentences are where errors appear most. Correcting a misheard phrase before the AI acts on it takes less time than recovering afterward.

What works well in a voice session

Dictation with Claude is a good fit for tasks where typing is the main friction:

• Brain dumps: speak freely, then ask Claude to organize the output into a structured list or outline.
• Rough drafts: narrate what you want to say and ask for a cleaned-up version.
• Thinking out loud: describe a problem in plain speech and ask for structured options.
• Meeting note summaries: dictate a short summary while the conversation is still fresh.
• Quick questions: ask by voice and read the answer on screen.

Voice sessions are harder for tasks that require switching between files, precise code review, or multi-step instructions where exact wording matters. For those, typing or a structured screen-based workflow is more reliable.

A practical combination is to dictate rough notes or an outline by voice, then switch to typing for the detailed work. This works well for initial planning sessions where the goal is to capture ideas quickly, before the precision stage begins.

Starting a voice session with the right context

A voice session goes faster when the assistant already knows the project. Dictating the whole background at the start of each session wastes the advantage of going hands-free. If the assistant can start from a known brief, you begin with the task, not the explanation.

Claude Projects let you write a system prompt once. Every conversation in the Project starts with it, so on-phone or hands-free sessions do not require a spoken briefing. See how to use Claude on your phone for the mobile setup steps.

Saving what a voice session produced

A voice session ends and the output is in the chat. Without a save step, the next session starts from nothing. Here are three practical ways to capture the outcome:

1. Ask Claude to list the decisions made and the tasks that came out of the session. Copy them into your project notes.
2. If Claude is connected to fenbs, ask it to save progress on each task it touched and update Where we left off for the project.
3. Dictate a short summary into a notes app while the session is fresh, then paste it into your project context before the next session.

The save step takes two minutes. Skipping it means the next session — voice or typed — starts from a blank state and needs the same context all over again.

How to do this with fenbs

1. Create a free account. Add a project for the recurring work you handle in voice sessions.
2. Write the project goal, current tasks, and standing decisions in fenbs. Keep it short enough that the assistant can read it quickly at the start of a session.
3. Connect Claude to fenbs from Integrations. Follow the MCP guide and approve only the access you need.
4. At the start of each voice session, dictate: "Read the project context and tell me where we left off." Review the answer, then continue with your task.
5. Near the end of the session, say: "Save progress on what we worked on and update Where we left off." That record is available for the next session, hands-free or not.

When voice dictation is not the right fit

Dictation works best in a quiet space. Background noise, accents, and technical jargon increase transcription errors. For detailed coding work, file-heavy tasks, or work where precision outweighs speed, a keyboard is more reliable. Browse the AI at work topic for other Claude workflows.