I have been wanting a Bluetooth ring myself so I can just tap my finger and have it trigger my airpods which would initiate live voice or dictation on my phone or computer.

I have not considered input for editing functions but that makes a lot of sense. Maybe a swipe gesture or something with a little capacitive pad on the ring.

How do you keep your prompts from getting just ramblings as you do the thinking?

It sounds like a fun way to "code", but I just can't imagine how it works in reality.

I am having great results by mapping the press to dictate onto my pedal.I have been vibecoding without using my hands for the past four months with great results.It's amazing using the computer without touching it.I can go on for hours with a couple of pedals.I use them to switch windows, dictate and press enter.That's really all you need.

The one thing about the Bluetooth microphones is that there is this annoying lag that it's very hard to get used to, even when using AirPods which you think would be optimized for this. It's just untenable in my opinion because I could never get used to the 3-400 millisecond delay that I had to deal with. I ended up using simple Apple wired headphones as my go-to solution eventually. They actually produce a least a modest strain on ears when being in for hours on end, at least in my situation. I do like your idea about the Bluetooth multimedia remote controller.

I can see the appeal from a workflow perspective, though from a “social” perspective I don’t see myself enjoying talking to myself all day.

Bonus points if you work in an office. This kind of workflow would be a nightmare.

…unless it means we get our private offices back.

Great ideas here thanks! I’m going to see if I can whip up a Windows equivalent, using Autohokey instead of Karabiner.

i forked handy and built 2 modes. One for dictation and one for quick agent actions that uses the pi harness with local models and jev style classifiers so it can read screens and interact with elements (via accessiblity tree, screenshots, os scripts, bash, mcp, etc). Its nice because in agent mode you can just give it instructions on how to respond (like dictation that can read the context of the current page or input). I've been pretty happy with it so far and debating if i should release it. Just not sure if the world needs yet another vibe coded agent system.

I'm glad we're getting to a point where voice can be the main UI, and that some people are actively using it to their benefit, but I hope it doesn't become THE primary interface, even with AIs.

I find speaking tiresome, somehow, and if I had to talk all the time to my computer with text input being a fidgety "accessibility" option, I'd retire to a monastery and just become a monk.

Agree with the need for different buttons for different voice contexts though.

Though I think it will become a dedicated AI key on some keyboards.. How about the Right Alt/Option on MacBooks? Does anybody use that? It could be the "AI Anywhere" input key, optionally defaulting to voice, and while F5 could continue to serve as a literal dictation key..