Heard is a macOS voice layer for your agentic workflows. It connects to Claude Code, Codex, and Cursor and turns their output into intelligent summaries you can hear. Full commentary when your eyes are elsewhere, or silence until something errors or needs a decision. With agents run in parallel, Heard summarizes at the project level, so you hear where the work stands, not five terminals talking over each other. Pair your phone and it comes with you. Open source, free for personal use.
Hey PH, Kelly here, maker and founder of Heard.
The last two years went into making it easier to talk to agents. Voice input, better prompts, better context. Nobody worked on the other half. Agents still answer in scrolling text you have to sit and watch.
Heard is that half. It listens to your Claude Code, Codex, and Cursor sessions, understands what matters in context, and turns the useful parts into concise, natural speech. A useful update, not a transcript.
It matters most once you're running more than one agent. Parallelism is free now, attention isn't, and every agent you add makes the terminal a worse instrument for keeping up. So each agent gets its own voice, and a swarm gets summarized at the project level. One clear story instead of five windows you can't watch at once.
With Heard Power you can pair your phone and keep the session going from the kitchen, a walk, anywhere you're not at the desk. Hear what's happening, answer by voice, approve the next step in one tap.
Open source, free for personal use.
#1 well deserved 🥇 talking to claude code instead of typing just makes sense
I like the “useful update, not a transcript” framing. I’ve definitely lost time babysitting parallel agent terminals; curious how you decide when to stay silent vs interrupt for a decision?
The next bottleneck isn’t building better agents but orchestrating human attention across them. Love this direction !!
Congrats on the launch. How does Heard handle conflicting updates across parallel agents? If one agent finishes successfully while another discovers a change that invalidates its work, does the project-level summary surface that dependency, or does each session remain isolated?
@itskellysun, this is awesome! Any chance you can share an invite code for the Power beta?
This sounds amazing for anyone running multiple things at once. I do not always have my eyes on the screen and missing an error will cost time. I like that it only interrupts when it actually matters. Congratulations on your launch.
Does this work for non-developers or is it built specifically for coders?
Congrats on the launch Kelly! The thing I keep hitting is not knowing whether an agent is actually stuck waiting on me or just still working. Does Heard speak up only when it needs an answer from you, or does it narrate as it goes?
really smart approach to the feedback loop problem with agentic coding. half the time I'm running Claude Code I'm doing something else entirely and only check back when it's done — having audio summaries of what happened means you catch errors or odd decisions way earlier instead of reading through the whole diff after the fact. does it differentiate between routine completions vs things that actually need your attention?
Running agents in parallel makes the hard-signal versus context-aware split feel like the core design choice, not just a notification feature. For the project-level summaries, how do you handle two agents reaching contradictory states, such as one reporting a successful migration while another has a failing test against the same branch? Does Heard surface the conflict as a decision point, or is reconciliation left to the underlying agent sessions?
@itskellysun makes sense, the reasoning-pass override on top of the per-session read is the part I like - a pure fixed rule table would misjudge the edge cases constantly. shipping the heuristic now and layering personal preference on top later seems like the right build order rather than trying to learn preferences from day one with no baseline behavior.
I run Claude Code daily and the output itself was never the problem, it's zoning out halfway through a long scrolling session and missing the part that actually mattered. Reading holds my attention for maybe 30 seconds before I start skimming. Hearing usually doesn't do that to me. I am definitely going to try this one.
heard is awesome :) love the audio first human computer interaction approach to agent work. this is the future!
Voice as the interface to a coding agent is more interesting than it first sounds, because the hard part isn't dictation, it's knowing when to interrupt. If I'm talking while the agent is mid-task, does it queue what I said, or does it treat it as a course correction and abandon the current step? Curious where you landed on that.
Huge congrats on the launch, @itskellysun Solving the outbound half of the agent interface is such an underrated vector. qq can we adjust a 'verbosity slider' to only hear critical errors instead of full updates?
Oh this is such a nice idea, I always miss the moment when my agent is waiting on a permission prompt and lose 20 minutes for nothing. Love that there is a near silent mode too. Does the phone pairing let you actually approve things by voice while you are away from the desk, or is it more of a listen only thing?
Congrats on the launch. The multi agent part caught my eye, giving each agent its own voice identity is a smart way to keep track of parallel sessions without staring at four terminals. How does the filtering decide what counts as a critical event versus routine noise, is that configurable per project?
The verbosity dial and the project-level summary are the right primitives for parallel work. Before I'd commit to this for real sessions, I need to understand where the session state actually lives: when the context pass holds state across the session, is that in-process memory that disappears when Heard closes, persisted locally on disk, or synced to a server? Open source positioning suggests local, but the Heard Power phone-pairing feature makes me wonder if there is a relay component once you go beyond single-machine.
About Heard on Product Hunt
“Give Claude Code and Codex a voice”
Heard launched on Product Hunt on July 25th, 2026 and earned 339 upvotes and 91 comments, earning #1 Product of the Day. Heard is a macOS voice layer for your agentic workflows. It connects to Claude Code, Codex, and Cursor and turns their output into intelligent summaries you can hear. Full commentary when your eyes are elsewhere, or silence until something errors or needs a decision. With agents run in parallel, Heard summarizes at the project level, so you hear where the work stands, not five terminals talking over each other. Pair your phone and it comes with you. Open source, free for personal use.
Heard was featured in Productivity (657k followers), Developer Tools (516.5k followers), Artificial Intelligence (474.6k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 361.6k products, making this a competitive space to launch in.
Who hunted Heard?
Heard was hunted by Abdul Rehman. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Heard stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Abdul Rehman