HN user

arend321

72 karma
Posts1
Comments58
View on HN

I've been building out the Android app that works as the wrapper between codex and me this way. ADB debugging access over WireGuard. I ask to add a local wake phrase detection for the phrase "Hey codex" to start dictation. Codex tells me it thinks Vosk or OpenWakeWord might be a good fit, I voice select Vosk. Codex starts working. Codex deploys (updates) the app on my phone and restarts it and I hear the task complete response. I say "Hey Codex" to test and ask for some tuning/improvements, or move onto the next task. All while keeping my phone in my pocket.

But there are countless projects I work on this way. Eg, I got an email from person X, it says it encountered a bug when doing x and y. Codex reads the email (using nvidia/gliner-PII to hide PII data) and investigates the reason for the bug and proposes a solution. I ask it to implement the fix on my dev server and increase test coverage. I enjoy my walk and after say 7 minutes get a an overview of the fix and can decide to deploy to production.

I have my phone in my pocket, no screen interaction is required. I use a headset (Shokz OpenComm2) with wind muff (when cycling). I made an Android app that listens for codex turn-complete or intermediate updates and plays them back to me. My answer is transcribed and pasted back to the relevant codex (tmux) session on the server (which I can select by voice) a tiny layer helps with things like /new, /plan, answer selection, etc.

I do a ton of coding (codex) with a tts/stt wrapper. During walks, cycling, in the car. Not every task is suited to this style of interaction, but many are. Long form codex replies are condensed, code blocks are suppressed all in the name of making it work for tts feedback. So it works best on well defined projects with guardrails, where you know the agent can perform well.

Not my experience. Maybe an hour of top model use on the $20 plan, then Composer 2.5 which needs constant hand holding.

Cursor was nice when I was still meticulously hand coding my stack, fantastic autocomplete. With today's top models, I barely write code myself, just review commits. Cursor eats Opus credits like there is no tomorrow. Composer has been a net negative in my experience. All in on Codex with GPT 5.5 on high using /fast.

I've been trying out various mobile, ai-assisted coding workflows.

Packing a Linux mini-pc in my rucksack, connected to display glasses, and voice-to-text with handy. Voice to text gets injected into a remote (Docker) codex session, running a hot reload web stack. I prompt to implement various features in an existing code base, where codex understands the structure and requirements. If a feature is done, I take a moment to inspect the results on the display glasses, then move onto the next feature or keep iterating. It's not perfect, but I was able to implement a couple of not too complex features while walking my local national park. The display glasses have a built-in 4-microphone array, and solid speakers. No need for a bulky headset or earbuds. Glasses come with monochromatic dimming, you can easily switch between dimming and see through.

If this comes with Linux integration, I will certainly give it a try.

I'm also using this project. Easy to configure and operate.

I am feeling a slight unease using such a recent project for things as important as the database. But the polished interface combined with the easy docker deployment made me use it anyway. Restores need some permission tuning on PostgreSQL but otherwise happy.

They are very proud of their github star acquisition curve [0], the "blessing" by Anthropic [1]

But I have yet to verify the Anthropic claim.

[0] https://www.reddit.com/r/selfhosted/comments/1q94uu9/selfhos... [1] https://www.reddit.com/r/ClaudeAI/comments/1rklvr7/anthropic...

The Linux terminal app on Android reddits are full of reports of instability. It is far from being useful as far as I understand. I had so much hope for this being a good way to use my phone as a portal for development, but it's a dud. At least we have termux and proot.

I think many saw this coming and it's probably a good thing. Personally I went with Kysely as a thinner abstraction with less risk of being acquired and turned into something that no longer aligns with my objectives. Still this is probably a nice boost to the major rewrite the Drizzle team is working on.

I believe the obsession with streaming is a major factor in the new constraints. Together with supporting the lowest common denominator, edge runtimes.

We're pretty much there. I ditched my monitors for the XReal One Pro. In Ultra Wide Mode (3840x1080 32:9) I can be productive for 1 or 2 hour sessions. Only bummer is some blurry spots in the lens, which I can see when looking through the glasses disconnected as well as when looking at rendered text. Support wasn't very helpful asking for proof with a photo or video recording even though it's near impossible to get a camera in front of the glasses and take a reasonable clear photo.