Openbase

Manage your team of AI agents by voice, from anywhere

Developer Tools

Artificial Intelligence

GitHub

Tech

Visit WebsiteSee on Product HuntTwitter ⧉Github ⧉LinkedIn ⧉

Congrats on the launch @lucaszhao! Is this mostly for checking in and approving things while you're away, or can you actually kick off real work from scratch without touching a laptop? I look forward to seeing where you take it.

managing agent fleets by voice is kinda wild 👏 do teams run them fully async yet?

The approval flow is strong, especially pausing sensitive actions and failing closed when voice input is unclear.

How does Openbase handle two agents trying to change the same files at once? Does it detect conflicts before either agent commits or pushes?

The voice-first workflow is compelling, especially for starting tasks or checking progress away from a desk. Where would you personally draw the line between actions that can be approved by voice and changes that should always require reviewing the diff on screen first?

@zoky_zhou

Congrats on the launch! I already manage Codex from my phone, so the voice control is the part that interests me here. How well does Openbase handle longer instructions or corrections when you change your mind halfway through speaking?

This is a smart solution — finally a way to supervise AI coding agents by voice from your phone without being glued to a laptop.

good, that's the right default. re-asking is a small friction cost that's obviously worth it compared to the alternative on something like a merge

Congrats on the launch. The voice layer feels strongest as a triage/approval surface, not a replacement for review. One thing I’d want to see in the flow is a review-at-desk escape hatch: before any multi-file change, the agent summarizes files touched, tests run, risky operations, and what still needs a screen. Then approving later should be as easy as approving now.

This is the hard part and you're putting it front and center: which calls the agent makes alone vs. which ones it asks about out loud.

We ship agents in a very different domain — they message customers and take payments for small businesses — and the rule we landed on after getting it wrong is: plan freely, execute visibly, but always ask before anything that touches money, anything that goes out to many people at once, and anything that changes configuration.

The trap we hit: we tried letting the agent tune its own thresholds, with a guard scoring the outcomes. It optimized straight into the failure mode — a safe, wrong answer scores beautifully, because it generates no escalation and burns fewer tokens. We killed the autonomy and kept the human in the loop.

Curious how you think about that when the approval is by voice, where "yes" is a very cheap thing to say.

I'm non-technical and ship almost everything through coding agents, so the part that would decide it for me isn't approval, it's verification. My recurring failure isn't an agent doing something destructive, it's an agent telling me a change shipped when it actually landed on a branch that had already been merged. Does Openbase report back from the actual repo state after the fact, or only from what the agent says it did?

the safety word answer above covers accidental triggers, but what about a garbled connection mid-approval, like walking through a spot with bad signal while saying yes to a PR merge? if the transcription comes back partial or mangled, does it fail closed and ask you to repeat, or is there any path where a mis-heard word could get treated as an approval for something you didn't actually confirm

Honestly the voice steering thing is kind of wild, I was telling an agent to fix a bug while walking the dog and it just committed the patch. Felt like cheating honestly.

Good to know it fails safe rather than proceeding on a guess - that queue-and-resume behavior is exactly what I'd want if I'm the one walking around unable to babysit the connection. Thanks for the detail.

Great idea, it’s the worst when you’re running an agent process and step away, screen goes dark and all work pauses. Best of luck!

Update: we've also just uploaded our YouTube demo to our launch, check it out here: https://www.youtube.com/watch?v=SsnUgItdae4

Congrats Lucas! I do almost everything by voice, my dictation is full of half-sentences and “wait, no, actually” corrections, so this launch is personally relevant. My question is about the input side rather than the approval side everyone’s covering: when my spoken instruction is messy or ambiguous, does OpenBase confirm its interpretation back to me before dispatching the agent? A five-second “here’s what I understood, go?” would save a twenty-minute run building the wrong thing. Curious how much you’ve tuned for how people actually talk versus how demos talk.

this solves a real problem, I live in Claude Code all day too and the "still tied to a laptop to babysit it" gap is exactly right. question that's more about reliability than the approval-safety angle everyone's asking about: what happens if you lose connectivity mid-flow, say you're walking and your phone drops signal right as an agent is waiting on a voice approval. does it just pause and wait indefinitely for you to reconnect, timeout and roll back the pending action, or keep going with whatever the last confirmed state was?

Congrats on the beta! Getting to approve a PR out loud on a walk instead of hunting down a laptop is a great use of voice as an interface.

I'm curious what stops a sensitive approval from firing on someone else's voice, a recording, or an accidental phrase match before it reaches a real repo. That's the piece of the voice layer I'd want locked down first.

Sign me up, this is actually a dream! Hopefully I can find time to download this to try it. I like it because I used to drive around calling my human assistants to help me do work as I was driving long distances. This is really useful for people who drive long distances and are business people or people with work that requires computers. Maybe even artists can use this like music industry people.