For my Mac friends here that don't want to use cloud solutions for Dictation and Meeting Transcriptions:
I was too annoyed with other options, so I built https://t.co/cLw0f7ksHU. One-time purchase, on-device, agent first, fine-tuned and fully optimised (59ms voice to insert).
@ivanfioravanti As long as they stay away from the EU AI Act, time will tell.
They are well positioned to lean into AI, just like they did during the crypto wave
@ivanfioravanti Is this really still not available? I just assumed it was because we have it over here in Switzerland. Dare I hope Switzerland gets the AI stuff?
@Dimillian It was even worse when I was trying to launch AI-powered assistants in the healthcare space a year ago or so. These EU regs are serving absolutely no one and they're certainly not really protecting anyone.
It's been a fun journey with this thing that started off as a little plugin for my own usage and which has now grown into something that a ton of companies across Europe use as their only way to develop, both in terms of tooling and methodology.
Off to the ๐๏ธ in Italy for a week tomorrow, remoting to codex set up of course.
Got some OSS work done before leaving, https://t.co/RvoHCvyQMv now also works in @cursor_ai and @grok build (in addition to the claude code and cursor)
@cfabetterworld Yep. Most of them are progressively exposed but can certainly be optimized. Also fun to see everyone else adopting the same patterns, a lot of convergence right now
Finally sat down and rebuilt Flow-Next's Codex support from scratch. Native plugin, pre-built agents with sandbox modes and nicknames, skill metadata for the Codex UI, the works. Was tired of the "clone repo and run a shell script" install.
Now it's just /plugins โ install, same as Claude Code. 20 agents, the whole workflow. One hook short of full Ralph parity on Codex (they don't intercept Edit/Write yet) but everything else works.
Cross-model reviews can still go through @repoprompt or Codex CLI depending on what you like (hint: use RepoPrompt, it's awesome).
https://t.co/X2H4XLzde4
Yes, that is the trade-off currently. What started out as something for my own dev work and then primarily for solo devs has morphed into a fully-featured thing for 100s of orgs. I do have a todo to see what can be streamlined and simplified without changing the best-in-class output
@cfabetterworld manually reviewed - not sure what you mean by this. I review the skills in flow-next thoroughly, there is a lot of the bloat that comes from supporting multiple review backends etc, something that I'm trying to optimize
@cfabetterworld Yes the successor is. It's easy to only use the parts of flow-next that you need though. That being said it's increasingly geared towards reproducible workflows and collaboration in large projects and R&D orgs. Mainly because it is what I roll out to all of our 40+ companies.