How to Listen to Claude Responses
• By Elliott Tong
To listen to Claude responses, install the Alexandria Chrome extension, then open any conversation on claude.ai. Alexandria detects when a response finishes streaming (by checking the data-is-streaming attribute and cursor-blink class) and injects a play button into the action toolbar beside the Copy and thumbs buttons. Click it to hear that response read aloud with word-by-word highlighting. Each response in a conversation gets its own button.
Why Listen to Claude Responses Instead of Reading Them?
Claude's responses are often detailed and nuanced. A single explanation can run thousands of words when you ask it to think through a problem, consider edge cases, or weigh trade-offs. That depth is valuable, but it demands focused reading time.
Listening changes how you can use that depth:
You can think alongside the response
When Claude is helping you work through a decision or code review, listening lets you process its reasoning while you look at the thing it's discussing — the code, the document, the design. Reading forces your eyes to be in one place.
It suits Claude's conversational style
Claude tends to write in a conversational register with clear structure. That style translates well to audio — it sounds like someone explaining something, not a document being read aloud.
You catch the caveats
Claude often qualifies its answers: "however", "that said", "one thing to consider". When scanning text, these qualifications are easy to skip. Listening forces you through the whole response, including the parts that nuance the main answer.
You can review long conversations
After a back-and-forth with Claude, you might want to revisit an earlier response. Each response has its own play button, so you can jump to any one without scrolling through and re-reading.
How Alexandria Works with Claude
Alexandria's Claude adapter (503 lines of custom code) handles three challenges that generic TTS tools cannot:
Streaming-aware injection
Claude streams responses token by token. A naive extension would inject a button into a half-finished response, then break when the DOM shifts as more tokens arrive. Alexandria's adapter checks the data-is-streaming attribute and looks for cursor-blink or typing-indicator classes, and only shows the play button once the response is stable [ClaudeAdapter.js, isStreaming()].
Finding the toolbar in an ancestor
Claude's DOM structure places the action toolbar (Copy, thumbs up/down, retry) in a per-turn wrapper element, not adjacent to the response text. Alexandria's adapter walks up from the response through up to six parent elements until it finds the toolbar, using fallback selectors to handle Tailwind class changes between Claude versions [ClaudeAdapter.js, findAnchor(), lines 274-310].
Multi-response state synchronisation
When you click a response's play button, that button shows the playing state while all other response buttons in the conversation show idle. If you click a different response mid-playback, the first stops and the second starts — no overlapping audio, no confused states [ClaudeAdapter.js, _currentResponseElement + stateManager subscription].
Conversation switch detection
Claude is a single-page application. Clicking a different conversation in the sidebar doesn't trigger a page load — it swaps the DOM. Alexandria polls the URL every 500ms, detects these navigation events, cleans up old buttons, and injects new ones once the new conversation renders.
Tips for Listening to Claude Effectively
Start with explanatory responses
Claude's best use case for listening is when you've asked it to explain something: a concept, a design pattern, a trade-off. These structured, multi-paragraph responses are where listening saves the most time compared to reading.
Use it for code reviews
When Claude reviews your code, listen to its feedback while looking at the code itself. The audio explains what it's seeing; your eyes stay on the lines it's discussing.
Listen to earlier turns
After a long conversation, you might forget what Claude said in an earlier response. Each response has its own button — click it to hear just that response without scrolling back and forth.
Adjust speed gradually
At 1x, a 500-word response takes about 4 minutes. At 1.5x, it's under 3 minutes. Alexandria's free tier goes up to 5x, but start at 1.25x and increase as your comprehension adjusts. Most people settle into 1.5x–2x within a week.