<p>Hi Product Hunt! 👋 I'm Charles, founder of Freu AI.<br><br>A while back, we teased that we were working on extending our browser automation tech to the entire operating system. Today, we are officially launching Freu AI for Mac—an AI agent that automates any desktop software across your OS using natural language.<br><br>The Problem: Vision Agents are Too Expensive & RPA is Too Brittle<br>We hit a massive wall with current GUI automation. Traditional RPA (AppleScript, rigid X/Y coordinate clickers) breaks the moment you resize a window or an app updates its UI. On the flip side, modern multimodal agents (sending screenshots to cloud LLMs) scale terribly for repetitive tasks.<br><br>Right now, most desktop agents operate like interpreters. Every time you ask it to "Extract data from this local PDF and enter it into Excel," it takes a screenshot, sends it to the cloud, reasons about the visual layout, and clicks.<br><br>The Traditional Cost: ~10k tokens (Image context) × 5 steps × 10 runs a day = ~500k tokens/day just to navigate the exact same desktop UI, not to mention the unbearable latency.<br><br>The Solution: AOT Compilation + Semantic UI (SUI)<br>Freu AI changes this by introducing Ahead-of-Time (AOT) compilation for OS-level tasks. Instead of the agent analyzing the screen from scratch every single time, you show it the cross-app workflow once.<br><br>Freu AI uses a cloud vision-based model to "compile" that session into a deterministic, reusable DSL.<br><br>The Freu Cost: You pay the cloud "AI reasoning" token cost once when the agent watches and learns your workflow. But for future runs? The agent simply invokes the pre-compiled DSL command locally. This drops your recurring execution costs to zero and reduces latency from minutes to seconds.<br><br>How it works under the hood:<br>When you record a desktop workflow, our engine doesn't just save a dumb macro. It uses Semantic UI (SUI) to understand the screen:<br><br>Perceive: It recognizes buttons, text fields, and icons across any app.<br><br>Resolve: It anchors to the semantic meaning of the UI, not rigid coordinates. If Spotify moves their "Play" button, Freu AI still finds it.<br><br>Execute: It binds these visual anchor points into our DSL and executes them deterministically.<br><br>🎁 The Open-Source Bonus:<br>While the Mac desktop app is our core product, we are open-sourcing freu-cli today—our underlying DOM-based browser automation engine. You can drop it into your own agents to give them instant "muscle memory" for web tasks. Repo here: <a href="https://github.com/freu-ai/freu-cli" target="_blank" rel="nofollow noopener noreferrer">https://github.com/freu-ai/freu-cli</a><br><br>🔮 What’s Next: The Local Vision Execution Engine<br>We are relentlessly upgrading our stack. Very soon, we will launch a capability to run the execution phase using a lightweight, SUI-optimized vision model running entirely locally on your hardware. While we will always rely on powerful cloud LLMs to understand your complex intent during the initial "learning" phase, this upcoming local engine means your day-to-day repetitive executions will cost exactly zero API tokens and keep your real-time screen data 100% private.<br><br>We’d love for you to try Freu AI for Mac. I’d love to hear your feedback on our AOT approach or how you're currently handling repetitive cross-app tasks. My co-founders and I will be hanging out in the comments all day to answer your questions! 🚀</p>
<p>The best part for me is not having the agent re-read the same UI every time. If a workflow is repeated daily, teaching it once and running it locally sounds way more practical and I'd mainly want to see how it handles small layout changes after app updates.</p>
