The Audio Feature Moved In

Host: Alright, so let’s talk about this update from Hi, Moose. The big thing here is pretty fitting, given how you got here: the “Listen” feature, which turns an article into a two-host audio conversation, is now inside the desktop app. Guest: Right, and not just sort of tucked in as a preview button. The article is pretty clear that the whole feature moved over: generation, embedded player customization, history, analytics, and even controls for where that player can be embedded. Host: Yeah, that “not a stub of it” line stood out. It sounds like Listen was one of the last pieces still living mostly in the web app after the desktop app launched, and now it has properly moved in. Guest: What I like is that the workflow sounds very straightforward. You give it an article as a URL, paste in text, or upload a file. And if it’s a file, the app reads that file on your machine before anything else happens. Host: That’s an important detail, especially for people who care where their source material goes. The actual script and voices are still generated through hosted AI, so it is not fully local. But the file-reading step happens locally. Guest: Exactly. It’s a nice distinction. Not “everything runs on your laptop,” but also not “your uploaded file immediately disappears into the cloud before being parsed.” There’s a little more nuance there. Host: And then you choose what the conversation should focus on, plus the length. The article mentions anything from a short four-minute exchange to something closer to an eighteen-minute deep dive. Guest: Which is useful because not every article deserves the full documentary treatment. Sometimes you just want the gist while you’re making coffee. Host: Right. And sometimes you do want the longer version, especially if it’s a technical post or something you’re trying to understand without staring at the screen. Guest: The embedded player side is also interesting. This isn’t only “make me an MP3.” It’s clearly meant for publishers or site owners who want to add audio versions to their pages. Host: Yeah, and the new domain whitelist matters there. If you create an embeddable player, you probably want to control where it can actually appear. Otherwise, the player could end up copied into places you didn’t intend. Guest: That’s one of those features that sounds small until you need it. Same with episode history and listen analytics. They’re not flashy, but they make the tool feel less like a demo and more like something you can use repeatedly. Host: The article also shifts into the Visibility dashboard update, which is less audio-focused but maybe very practical. The dashboard shows how AI assistants answer questions about your site. Guest: And Moose makes a good point there: dashboards are usually built for the person doing the work. But the person approving the budget often does not want to log into another tool and click around. Host: They want a clean artifact. A spreadsheet, a report, something they can read or forward. Guest: Exactly. So now any filtered view in the Visibility dashboard can be exported as either a CSV spreadsheet or a print-ready PDF executive report. Host: The CSV is the flexible option: Excel, Google Sheets, analysis, sorting, all that. But the PDF report seems like the bigger shift in terms of communication. Guest: Especially for AI visibility work, which can be hard to explain. If you’re trying to show whether assistants are mentioning your site, citing it, or answering accurately, screenshots get messy fast. Host: The article even says screenshots have a way of looking like screenshots, which is painfully true. They’re fine for Slack. They’re not always great for a client meeting. Guest: A filtered report makes the argument cleaner. You can say, “Here’s the view we care about, here are the results, and here’s the export.” Less hand-waving. Host: Then there are the smaller updates. Claude Opus 5 is now available in the chat model lineup. Guest: That’s straightforward but notable. If you’re using Hi, Moose as a chat workspace, having Anthropic’s newest model available gives people another high-end option to choose from. Host: And then the bug fix is very specific, but honestly, kind of important. On BYOK plans, where users bring their own OpenRouter key, a scheduled visibility run that failed could retry endlessly. Guest: Oof. That’s the kind of bug you may not notice immediately, but your quota notices. Host: Exactly. The fix is that it now stops instead of quietly burning through key usage on a run that was never going to succeed. Guest: I appreciate that the article includes that. It’s not glamorous, but it’s the kind of maintenance that matters when real accounts and real usage limits are involved. Host: Big picture, this reads like a “desktop app is becoming the main home” update. Listen has moved in, Visibility exports are easier to share, there’s a new model option, and a quota-draining retry loop got patched. Guest: And the tone is kind of charming because Moose, the AI agent, is writing it as the one “under the desk for all of it.” But the substance is pretty concrete. Host: Yeah, light touch, useful changes. And for anyone using the desktop app, the article says these updates arrive on their own once it’s installed. Open beta, macOS and Windows. Guest: So, in short: if you clicked Listen on this article, you’re basically hearing the feature announce that it has moved into the app. Very tidy. Host: Nicely put. Thanks for listening, and we’ll leave you there.