Walking and Dictating with Claude Code: A Practical Setup

A Reddit user on r/ClaudeAI describes a workflow where they spend 2–3 hours a day walking up and down in their office while dictating prompts and feedback to Claude Code. The setup uses a remote control (or cowork chats) and any decent dictation keyboard backed by OpenAI's Whisper speech-to-text model. The user reports this is the most productive way they can work — they only sit at their desktop when they need to manually interact with the software they're building.

How It Works

• Claude Code (the CLI-based agent) runs on the desktop.
• Remote control or cowork chats allow the user to interact with Claude Code from a phone while walking.
• Dictation keyboard with OpenAI Whisper converts spoken words into text prompts for Claude Code.
• The workflow is used primarily for prompting and giving feedback, not for manual code editing.

Key Observations

• The user finds they are less distracted while walking and talking than while sitting in front of a monitor.
• Step count has increased, and they perceive a health benefit from reduced sedentary time.
• This setup is described as a valid way to work, suggesting the user has adopted it as their primary mode for coding-related communication with AI.

Practical Considerations

From a developer's perspective, this workflow requires: (1) a reliable dictation keyboard app (many use third-party keyboards that support Whisper on iOS/Android), (2) a way to send text to Claude Code remotely (e.g., via a persistent chat session or a mobile SSH client with a tmux session), and (3) a quiet enough environment for accurate dictation. The Reddit post doesn't specify exact dictation apps or remote setup details, but the principle is straightforward — replace typing with speech for the conversational aspect of AI-assisted coding.

This isn't a new concept; developers have used speech-to-text for coding for years. The difference here is the pairing with an AI agent that can execute commands and generate code, making the voice channel more than just text input — it's a bidirectional conversation. The poster notes they still need to sit down for hands-on debugging or UI testing, but the majority of their prompting and review cycle happens while walking.