# Claude Code Input and Output Tips: Voice, Clipboard, Markdown > Six Claude Code tips for faster back-and-forth: voice prompts, getting output out of the terminal, Cmd+A, writing with Claude, markdown, and keeping links. Source: https://camnangai.com/en/for/developers/claude-code-tips-input-and-output Published: 2026-10-24 Most of the time you spend with Claude Code is not spent waiting for Claude to think; it goes into moving information between you and it: typing requests, pasting material in, copying results out. This is part three of a series that walks through all 50 **Claude Code tips** in YK Sugi's [claude-code-tips](https://github.com/ykdojo/claude-code-tips) repo. It groups six tips about the pipe between you and Claude: numbers 2, 6, 10, 16, 17, and 18. On the way in, that means voice, Cmd+A, and pasting with links intact; on the way out, `/copy`, the clipboard, files, and markdown. None of these tips needs complicated setup, but together they remove most of the manual copy-and-paste in a working day. ## Is talking to Claude Code faster than typing? For most people, speaking is faster than typing, and a speech-to-text system running on your own machine is good enough for prompting Claude Code. On a Mac, the options that have been tried are superwhisper, MacWhisper, and [Super Voice Assistant](https://github.com/ykdojo/super-voice-assistant), an open-source app that supports the Parakeet v2/v3 models. Hosted services are more accurate, but a local model is strong enough for this job. Even when the transcript has mistakes, Claude is smart enough to work out what you meant. In the repo's example, words mistranscribed as "ExcelElanishMark" and "advast" are still read correctly as "exclamation mark" and "Advanced". Now and then you have to say a word more clearly; overall it holds up. The easiest way to think about it is to treat Claude like a friend. You can text, and that is what most Claude Code users do, but if you want to go faster you send voice messages. As for the perennial "what if you're in a room with other people?", the answer is to whisper into wired earphones (the repo author prefers Apple EarPods over AirPods because they are cheap and good enough). Offices are full of people talking anyway; you are just talking quietly to your transcription software instead of to a coworker. It works well enough to use on a plane: the cabin is loud enough that the person next to you won't hear, and with the mic close to your mouth the model still does. Claude Code now has built-in voice dictation: turn it on with `/voice`, then hold Space while you speak, or run `/voice tap` to tap once to start and again to send. It requires a Claude.ai account. The repo author tested it and found it works well, but still uses a local model because it feels faster. If you have never tried voice prompting, `/voice` is the cheapest way to try, since there is nothing to install. ## How do you get output out of the terminal? Copying straight from a terminal tends to drag in stray characters and broken line wraps, so there are five cleaner ways to get Claude's content out: - **`/copy`**: the simplest option, which copies Claude's last response to your clipboard as markdown. - **The clipboard directly**: on Mac or Linux, ask Claude to use `pbcopy` to send output straight to your clipboard. - **Write to a file**: have Claude put the content in a file and open it in VS Code (or your editor of choice), optionally at a line number so you land on what it just edited. For markdown, open it in VS Code, press Cmd+Shift+P (Ctrl+Shift+P on Linux/Windows), and choose "Markdown: Open Preview" to see it rendered. - **Open URLs**: when there is a link you want to look at yourself, ask Claude to open it in your browser. On a Mac it will use `open`; elsewhere, "open it in my browser" works fine. - **GitHub Desktop**: ask Claude to open the current repo in GitHub Desktop, which helps most when it is working in another directory, such as a git worktree you have not opened Claude Code in yet. These combine. To edit a GitHub PR description, for example, don't let Claude edit it in place on GitHub, where it might break the formatting. Have it copy the content into a local file, edit it there, check the result yourself, and only then have it paste it back into the PR. You can of course run any of these commands yourself, but once you catch yourself repeating one, let Claude do it for you. ## Why are Cmd+A and Ctrl+A your friends? When Claude Code can't reach a page, the fastest fix is to select everything yourself (Cmd+A on a Mac, Ctrl+A elsewhere), copy it, and paste it straight into Claude Code. The typical cases are a private page that isn't public (not sensitive data, just not open to everyone) or a Reddit post that Claude Code struggles to fetch. The same trick works on terminal output: output from Claude Code itself or any other CLI tool, select it all, copy it, and paste it back to Claude. Some pages don't select cleanly as they are, but there are ways to get them into a state that does: - **Gmail**: for a long thread, click Print All to open the print preview (then cancel the print). That page expands every email in the thread, so Cmd+A captures the whole conversation. - **YouTube**: to ask about or summarize a video, click "Show transcript" under it, then press Cmd+A or Ctrl+A. This is not specific to Claude Code and works with any AI tool. It sounds crude, but I find it the most reliable option once every page-fetching tool has failed. ## How do you use Claude Code as a writing assistant? Claude Code is an excellent writing assistant if you work in two phases. In the first, give it all the context about what you want to write, then dictate detailed instructions by voice so it can produce a first draft. If that isn't good enough, try a few times. The second phase is where most of the work happens: going through the draft almost line by line with Claude. I like this line for these reasons, that line should move down there, this sentence needs to change in this particular way. You can ask about reference material for any paragraph too. It is a continuous back-and-forth, and the layout that suits it best is the terminal on the left and your editor on the right, so you see each change land in the file. Unlike "having AI write it for you", you never receive a finished piece to accept or reject. You keep editorial control at every line, while Claude handles the typing and proposes the wording. ## Why write in markdown? When people start a new document, many reach for Google Docs or Notion. With Claude Code at hand, the most efficient route is to write straight in markdown. Markdown was already good before AI, but because Claude Code is such a strong writing partner, its value goes up: for a blog post or even a LinkedIn post, talk to Claude Code, save the result as markdown, and go from there. Annoyingly, many platforms don't accept pasted markdown. The workaround: paste it into a fresh Notion page first, then copy from Notion into the other platform; Notion converts it to a format the others accept. If a regular paste still fails, try Command+Shift+V to paste without formatting. ## How do you keep links when pasting into Claude Code? The Notion trick works in reverse too. If you copy text with links from somewhere like Slack and paste it straight into Claude Code, the links vanish. Paste it into a Notion page first and copy it from there, and you get markdown with the links intact, which Claude Code reads without trouble. The faster route is to ask Claude Code to read your clipboard. It usually knows exactly which command to use, which on a Mac is `pbpaste`, and it fetches the content without changing the formatting. From then on, "here's a paste" can become "read my clipboard", which saves a step and keeps the links. ## Which habit should you change first? If you pick one habit, spend a week prompting by voice, whether through `/voice` or a local model. It is the tip in this part that changes your working speed the most, while `/copy`, `pbpaste`, and Cmd+A are things you will reach for naturally whenever copy and paste gets in the way. ## References - [45+ Claude Code Tips: From Basics to Advanced — YK Sugi](https://github.com/ykdojo/claude-code-tips) - [Voice dictation — Claude Code Docs](https://code.claude.com/docs/en/voice-dictation) - [Commands — Claude Code Docs](https://code.claude.com/docs/en/commands)