Chippy with Claude Code and Codex
Select what a coding agent wrote in the terminal and tap the right Option key; what you select is spoken as written, code and all.
Chippy does not know it is in a terminal, and it does not need to. A coding agent's answer in Claude Code, Codex or any other terminal tool is text on the screen, and text on the screen is what Chippy reads. Chippy notes which app was in front on the recording, and treats every app the same.
Hearing an answer
When the agent finishes, drag over its answer in the terminal window to select it, then tap the right Option key. Chippy asks the terminal for a copy of the selection, the way Command C does, and reads it in the panel with the spoken word lit. Select the next answer and tap again; the new text replaces the old.
If selecting in the terminal is awkward, copy first. Press Command C on the selection, then tap the right Option key with nothing selected: Chippy reads what you copied, and the panel's header says from clipboard so you know which it was.
Code is read as written
What you select is what is spoken, byte for byte. A file path, a code fence, a list marker or a command is read as it is on the screen; Chippy does not strip or rewrite any of it. So select the prose you want to hear, the explanation above the diff rather than the diff, and the read is the agent's words.
There is one exception, and you have to turn it on: Settings has a switch, Make all Chippy selected text TTS friendly, off by default, which rewrites the selection to read aloud better. It applies from the next read.
A long answer
The panel holds the whole selection. To hear one part again, click a word in the panel, then shift-click a later word: play reads that range and stops at its end. Tap the right Option key on the same selection and it replays from the start, and nothing new is made. Stop is in Chippy's menu in the menu bar, and the space bar in the panel pauses and plays.