Good product decisions depend on making the feedback path shorter than the frustration. Version 1.4 puts that path in the Help menu and gives every shipped version a public place to explain itself.
The release also tightens a smaller choice with an outsized first impression: which voices people hear first.
Report the problem without leaving the moment
Report a Problem and Request a Feature are now real forms inside Agent Callout. A report can include diagnostics with explicit permission, helping explain the environment and recent app behavior without asking someone to reconstruct it manually.
Those diagnostics contain operating facts and logs, not the content of agent transcripts. The privacy boundary stays intact even when the product needs help understanding a failure.
Release notes become part of the product
The Help menu already had a What’s New destination. Version 1.4 gives it a real changelog and adds a permanent contact page, so support and release communication are not dead ends.
That first changelog is the source that grew into this release blog. The intent is to explain not only what changed, but why a change was worth shipping.
Better defaults in the voice picker
Felix, Natalie, and Jude now lead the voice list. The underlying set is unchanged, but the order gives the strongest starting choices the most visible positions.
Defaults and ordering are quiet product decisions. They shape the first experience long before someone explores every available setting.
Product decision
The principle behind 1.4
Feedback belongs close to the behavior it describes. Every extra app switch, browser search, or missing destination filters out useful context before it reaches the product team.
We want the release loop to stay visible: ship a focused change, explain the reasoning, and make the next useful signal easy to send.