Voice agents should become more than transcription tools. Instead of simply turning speech into text, they should understand what users are trying to achieve. The same spoken idea may need to become a short Slack message, a detailed email, a technical issue, or a personal note. A useful voice agent should adapt automatically.
This is the direction Loqua is exploring: voice as an intelligent layer across the apps people already use. It can understand the current application, nearby content, personal vocabulary, and writing style, then shape spoken thoughts into something ready to use. Users should be able to speak naturally without organizing every sentence beforehand.
The next step is real-time duplex conversation. A good agent should know when someone has finished speaking, when they are only pausing, and when they want to interrupt. It should also recognize signals beyond words, such as emotion, hesitation, emphasis, and tone. Its own voice should feel equally natural, expressive, and appropriate to the situation.
Behind this conversation, the agent needs deeper capabilities. It should remember relevant context, think through difficult requests, use tools, and continue working after the conversation moves on. The voice experience remains fast and fluid, while more complex reasoning happens quietly in the background.
We all know that long-horizon coding tasks are difficult, but understanding long, multi-turn conversations is even harder. The agent must remain consistent, respond with the right emotion, use tools correctly, and remember what matters.
Lessie AI
Would this work well for developers writing documentation, PR descriptions, and technical explanations?
Loqua
@alexia_li Definitely! Voice can be especially useful for getting technical explanations and documentation out quickly.
Loqua
@alexia_li We are developers, everything works better now lol!
Fish Audio
Loqua
@hehe6z Thanks Helena, Fish Audio is also awesome!
BiRead
vibe coding❌
voice coding✅
Congrats on the launch!
Paste
Dictation tools always mangle product names and internal jargon, which is half of what I'd be dictating. Is there a way to teach Loqua custom words, or does it pick them up from whatever's on screen? That part would decide it for me.
Loqua
@protsenkoalexandra Totally get that, product names, acronyms, and internal jargon are exactly where generic dictation tends to get frustrating.
Loqua supports a personal dictionary, so you can add names and domain-specific terms you use a lot instead of hoping the model guesses them correctly every time. Screen context can also help when a term is visible, but we don’t rely on that alone.
If that’s the deciding factor for you, I’d definitely stress-test it with your real vocabulary, that’s exactly the kind of use case we want to get right.
Loqua
@protsenkoalexandra We designed customized dictionary and a set of algorithms to auto pick your terms on screen for context. The more you use it, the better it works!
The hands free angle feels super practical. Did that become a bigger use case after you guys started building it?
Loqua
@nathan_holdstein36 Definitely. We started more from the “less typing, less context switching” angle, but once we began using it day to day, the hands-free part became much more obvious.
There are a surprising number of moments where your brain is free but your hands aren’t, and voice suddenly feels less like a convenience and more like the natural interface.
I hate having to stop what I’m doing just to open another app. Can Loqua handle most of these little tasks without making me switch around?
Loqua
@sathesharayu12 That’s exactly the kind of friction we’re trying to reduce. On Mac, Loqua can already handle things like opening apps or webpages, creating reminders and calendar events, searching Maps, taking screenshots, and controlling things like Wi-Fi or Bluetooth.
It won’t handle every desktop task yet, but the goal is that more of those tiny “stop what I’m doing and click around” moments can just become a quick voice command.
Great Product! But I have a question does Capture to Ask hold up on all screens like a spreadsheet or code editor, or is it mainly reliable on simpler layouts like the calendar and chat view shown here?
Loqua
@sidraarifali It’s not limited to simple layouts, we’ve designed Capture to Ask for things like spreadsheets, dashboards, code editors, docs, and other dense screens too.
That said, the more complex the screen, the more important it is to capture the relevant area rather than everything at once. For a spreadsheet or code editor, that usually gives Loqua much cleaner context and a better answer.
So yes, those are definitely target use cases for us, not just calendar/chat-style screens.
Loqua
@sidraarifali It works on all conditions, complex tasks such as spreadsheets, formulas, candlestick charts or picture caption, you name it!