Loqua - Speak naturally and move from thoughts to being done
Your thoughts shouldn’t have to slow down for a keyboard. With Loqua, you can speak naturally to turn rough ideas into ready-to-use writing, understand what’s on your screen, listen when you’d rather not read, and move work forward by voice - from rewriting and translation to scheduling and coding workflows. Less typing, less context switching, more time in flow.
Replies
for app actions, can i see exactly what loqua heard and plans to do before it runs anything
@mattkilmer Good question, you can see what Loqua understood, but we don’t currently show a full step-by-step action plan before every single action.
We’re putting a lot of thought into that boundary though, especially for actions with bigger consequences. The goal is for simple, low-risk things to stay fast, while anything more sensitive or ambiguous should be clear enough for you to confirm before Loqua acts.
@ema_miao that split makes sense, can users choose which actions always need confirmation or is the threshold fixed by loqua
@mattkilmer Right now, that threshold is set by Loqua rather than user-configurable on an action-by-action basis.
We’re still tuning it though, the goal is to keep low-risk actions fast, while making anything sensitive, ambiguous, or harder to undo require more explicit confirmation.
User-defined confirmation preferences are definitely an interesting direction, especially for people who want tighter control over specific actions.
@mattkilmer That is a good idea for agent trust build, we will consider adding that feature for long horizon agentic functions, thanks!
@joshua_zhou731 that would help, especially if confirmations can be saved per action instead of handled one by one
@hehe6z Thanks Helena, Fish Audio is also awesome!
vibe coding❌
voice coding✅
Congrats on the launch!
@ll_wen 😂 Exactly. Hands on the code, voice on everything else. Thanks for the support! 🚀
This is probably perfect for those “wait, I just had an idea” moments
@eren_mindful Exactly! Our team member and many users use it as notebooks for random thoughts, especially for young parents who work and attend baby at the same time.
Screenshot to ask is such a simple idea but removes so much friction. No more explaining screenshots manually.
@zaniaz Yep. Just capture what you're looking at and ask about it directly.
most voice tools fail badly when dictating terminal commands or nested JSON structures. am curious if your underlying model treats code syntax natively or if i still have to manually edit brackets later.
@sansa_grey Great question, for exact terminal commands or heavily nested JSON, I wouldn’t claim perfect syntax-level accuracy yet. Those cases are much less forgiving than normal prose, since one bracket or character can matter.
Loqua is already useful around coding workflows and technical explanations, but for dense structured code we’d still recommend reviewing the output. Improving this is definitely an area we care about.
@sansa_grey That is the way we are aiming to, a truly hands free coding experience. Try variable names, terms, complex logic together with CC & Codex, it reads coding context so all the dictation feels much better. We will keep improving the model for better performance!
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.
@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.
@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!
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?
@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.
@sidraarifali It works on all conditions, complex tasks such as spreadsheets, formulas, candlestick charts or picture caption, you name it!
The screen context part is what caught my attention. Being able to just point at something and ask instead of explaining what I’m looking at every time sounds genuinely useful. Curious to try this in my daily workflow!
@mi_leeli Exactly, that’s one of the interactions we really wanted to make feel effortless. Sometimes explaining what you’re looking at takes longer than the actual question 😅
Really curious to hear how it fits into your day-to-day once you’ve tried it!