Here's a teaser of our Mac-1 model.
> 6.6B model
> runs locally (on any Mac)
> requires 7GB RAM (12GB ideal)
> can use 487 MacOS native tools
> perform multi-tool chained tasks
> reasoning: ON
> output: ~65 tok/s
We built a robust application layer around the model to make UI/UX MacOS native. The "model-focused" SaaS era is here.
Stay tuned for more.
Made a decision today, and I am going 80% local. Moving ALL my agents to DSv4 Flash & Qwen 3.6 27B. Running my orchestrator, ONE Agent on Opus 4.8 to lead the charge. We will build automations & Skills that will help teach and shape the team. Workflows = Success. Wish Me Luck !
I just shipped oMLX v0.4.0, the first official release with the new native Swift macOS app.
https://t.co/AJT6hKvMPL
oMLX now ships with a redesigned onboarding flow, settings UI, Hugging Face cache discovery, and a much more native-feeling way to manage and run local models on macOS.
- Huge thanks to GitHub contributor popfido for the excellent work that drove the Swift transition.
My goal is still the same: I want oMLX to be the app someone can open on a Mac and immediately try Local AI with, without needing to understand all the machinery first.
If you try 0.4.0, I’d really appreciate feedback on the macOS app experience, especially first launch, model discovery, server start/stop, update checks, and anything that still feels confusing.
instead of watching 2 hours of Netflix tonight, watch this 40-minute masterclass from the founder of a $20B China AI company
it's the clearest explanation I've seen of how Agent Swarms and AI systems actually work at scale
useful whether you've never built an agent in your life or have been using Claude every day for the past year
I took the key ideas and turned them into a practical guide on how to actually build with Kimi
find it below
It's past time for a law that ANY company that undergoes a layoff MUST lay off all H1B Visas before laying off a single American Citizen, and any company undergoing a layoff is banned from hiring an H1B Visa for at least 3 years.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.