tpae retweeted
can we all agree hadamard should be the standard for lower bit models? the speed tradeoff is miniscule at this point for the quality gains.
tpae retweeted
This is near-frontier AI reading a lease with the Wi-Fi off.
Then the insurance policy. Then it flags the one deadline that matters.
Nothing leaves your Mac.
tpae retweeted
Journalists can't upload a leak to the cloud.
So we turned off the Wi-Fi.
A 1.7B model read the whole case file, followed the money, and cited its sources.
LFM3. Day 0 on Osaurus.
Introducing 𝙻𝙵𝙼𝟹: our new generation of Liquid Foundation Models. With a new tri-hybrid architecture and new multimodal encoders, the LFM3 family is the ideal model suite for specialized intelligence.
> 6 model instances, across text, audio, vision, and omni modalities, generative and decision models.
> 𝙻𝙵𝙼𝟹-𝟷.𝟽𝙱: text, 256k context window.
> 𝙻𝙵𝙼𝟹-𝚅𝙻-𝟸𝙱: vision-language model with video-input support for spatial understanding
> 𝙻𝙵𝙼𝟹-𝙰𝚞𝚍𝚒𝚘-𝟸𝙱: tool calls, voice chat, reasoning in 18 languages.
> 𝙻𝙵𝙼𝟹-𝙾𝚖𝚗𝚒-𝟸𝙱: an omni model combines vision, audio, and language.
> 𝚍𝟷-𝟸𝙱 and 𝚍𝟷-𝙾𝚖𝚗𝚒-𝟸𝙱: decision models with typed outputs and calibrated probabilities in a single pass. Omni adds audio input.
> fine-tune on 1 GPU.
> a new tri-hybrid architecture
> architecture optimized for 14 processor classes across GPUs, CPUs, and NPUs.
> 𝙻𝙵𝙼𝟹-𝚅𝙻-𝟸𝙱 is a beast. It performs competitively with Gemma 4 12B (6x larger), and Gemini 3.5 Flash Lite, and GPT-5.6 Luna, with 1.9B parameters.
> 𝙻𝙵𝙼𝟹-𝟷.𝟽𝙱 is #1 on the Pareto frontier of device intelligence 𝚙𝚒𝚙𝚎𝚝𝚝𝚎.𝚕𝚒𝚚𝚞𝚒𝚍.𝚊𝚒
Every modality for specialized intelligence. Pick the one that fits your use case, customize it, and run it on-device.
1/ 🧵
tpae retweeted
more ppl needa be talking about how it kills the whole point of being local if you have to go point claude to an engine to startup the model, and then get claude to once again wire the api and params into the config to even get it working? isnt this super redundant to the whole local ai thing? being local doesnt just mean running on your hardware but also being accessible for as many users as possible, do ppl really want to use tab indents and all spacing/syntax to write out a proper toml/json config file for usage in a harness
tpae retweeted
Nanbeige actually lived up to its expectations, with reasoning on it tended to over reason (not in a way of thinking about things that didn't matter too much like the Qwen series, but much more in a "plans out all the specifics even in a simple job" kind of way), and while I had it turned off for the demo, I know just from the tests I did that it lives up to the claims and competes with Qwen 3.8 27b as a heavy coding capable model.
While cache may be larger due to older arch, Osaurus' efficient cache handling allows for smooth turn by turn usage without your RAM usage going higher than the model's ~20gb.
tpae retweeted
Local-first is antifragile by default. When agents run on your own hardware, there’s no central endpoint to breach and no single outage that takes everyone down.
We need an "Antifragile Internet" built for the agentic era.
The hacks over the past few days (PHP, Railway, eMudhra, LiteLLM etc) show how fragile the existing Internet has become. AI agents are challenging the Internet's structure in 3 distinct ways:
1/ On the offense side, agents are a weapon - AI finds and exploits bugs on a scale not seen before, and the cost of attack asymptotes to 0. Bugs that used to take human experts weeks and months are easily found, adapted, and exploited by AI agents. Decades of legacy code that ran on "security by obscurity" no longer holds against agents.
2/ On the defense side, agents are a target - AI generated code is often bug-prone. AI agents themselves, as machines of unconstrained output are liable to prompt injections and other types of attacks that can leak keys, PII, and other pieces of information.
3/ On the identity side, agents are dominating Internet activity - this year, machine traffic has already passed human traffic, and may continue to grow 1000x over the next few years. Content and webpages used to human requests and behavior are breaking with agents, and it is increasingly difficult to tell human content from AI content.
All this means we will need to see a ground-up redesigning of the Internet, one with more cryptographic verifiability, identity protocols, rule-enforcement, and other security primitives that eliminate bug categories rather than simply patch them - an "Antifragile Internet" that gets stronger and more secure as more agents participate in it.
This is an emerging thesis area for us at @usv, if you're building in the space please reach out!
More thoughts soon.
tpae retweeted
Nanbeige4.3-33B, day 1 on Osaurus.
Neoclouds are dying. It made a game about it. On a Mac.
🚀Excited to announce Nanbeige4.3-33B!
To push the performance ceiling of small agents, our strategy in Nanbeige4.3 starts with building a powerful teacher first.
Nanbeige4.3-33B delivers SOTA agentic performance among open models at ~30B parameters:
* Strong results on agentic coding and cowork benchmarks.
* When integrated into mainstream agent harnesses, it tackles real-world tasks with cost-efficient inference.
* It will serve as a teacher for upcoming smaller Nanbeige models, starting with Nanbeige4.3-3B.
huggingface.co/Nanbeige/Nanb…
huggingface.co/Nanbeige/Nanb…
#LLM #Agent
tpae retweeted
Venice AI, Experiential Labs, Maple AI, thank you for being transparent.
No gating the models, no collecting emails. I release these models for free, often with @jordanschenck also pitching in thousands of dollars to provide compute.
It’s sad that we’ve reached a point where simply asking for public acknowledgment of your work is even necessary. I’ve seen far more instances of people not receiving proper credit than instances where they do.
If you’re one of those people who aren’t properly crediting the people behind open source work, please don’t ruin it for the rest of those who do. And I don’t mean just in my case, but in general.
Open source is how EVERYONE benefits, and undermining the trust within that ecosystem is detrimental to us all. Stealing work and refusing to give credit makes you no different from OpenAI or Anthropic.
tpae retweeted
It’s now public! No invite required.
Try it out and tell me what you think!
Pairs great with @NVIDIARTXSpark devices like the @surface Laptop Ultra!
tpae retweeted
Here's a snippet of the @OsaurusAI iOS app that I'm currently working on. It's being built entirely in UIKit with no traces of SwiftUI for maximum performance and backward compatibility.
Excited to bring the Mac app to mobile with Day 0 support for the new iPhone Duo!
tpae retweeted
Osaurus is coming to your pocket.
Native UIKit. Day 0 on iPhone Duo.
Here's a snippet of the @OsaurusAI iOS app that I'm currently working on. It's being built entirely in UIKit with no traces of SwiftUI for maximum performance and backward compatibility.
Excited to bring the Mac app to mobile with Day 0 support for the new iPhone Duo!
tpae retweeted
Building on the frontier.
Local models. Your Mac. Electrons you already paid for.
Thanks for calling local models the frontier.
Intelligence per watt is improving fast on its own curve. Soon local models will match what feels like frontier today.
When that happens, there’s an enormous opportunity: tools, infrastructure, and support for people building businesses on the electrons they already paid for.
Labs like @ornith_ , @Alibaba_Qwen , @liquidai , and @nanbeige are already pushing this forward with almost no revenue model.
We’re building the infrastructure for it. Reach out if you want to learn more.
tpae retweeted
I don't think people realize how capable Local AI has become.
People compare them to the frontier models and conclude they are useless. That's like comparing a Honda Accord to a Bugatti Chiron.
Not everyone needs a hypercar, and not every task needs a frontier model.
tpae retweeted
NVIDIA spent its keynote selling AI factories.
A Mac read the whole thing and built a webpage about it.
The model found itself in the coverage.
Flint 40B. Running locally. Native Swift. No Electron.
Introducing Flint, @Recursive_SI’s first model: a fast local coding model built with our automated research system, the Eureka Machine.
• Best-in-class fast local coding
• Up to 2x faster than comparable models: 125+ tokens/sec on a MacBook Pro, 150+ on RTX Spark
• Built from scratch in under 4 months
Private, unmetered intelligence on your own machine. Open weights available now on @huggingface, run it locally on your favorite framework or try it for free on @opencode or @pidotdev.
tpae retweeted
6 of 7 local-first ideals, adapted for agents. The seventh is being built.
Replying to @OsaurusAI
@OsaurusAI does the muscle, Ornith does the hustle.
🙌 Two bros took all daily grind.
Check out the amazing work from Osaurus team!!
🔗 osaurus.ai


















