The Real Magic rarely happens in isolation.
It often happens in messy environments when ideas collide, perspectives clash, and something greater than any one person could create alone emerges.
Most meaningful breakthroughs in startups, products, teams, and even life almost always come from deep, genuine collaboration between people.
If you're building something, leading a team, or believe that 1+1 can sometimes equal 3… give it a read.
https://t.co/pQojEjNhKd
This is genuinely wild. 🤯
Alibaba just dropped Qwen 3.8-Max. A 2.4 trillion parameter model. And the open weights are coming next week.
The first time Qwen has ever open-sourced the weights of a Max-class model.
But here's the part that got attention.
They let it code autonomously for 10 days straight. Empty folder to production app. No hand-holding. The entire project trace is public on GitHub. You can watch an AI build a complete CLI tool over 500+ commits.
The benchmarks are comparing directly to GPT-5.6 Sol on max settings. On coding and reasoning they're neck and neck. The audacity of putting yourself next to Sol and publishing the numbers.
Pricing: $2 input, $6 output per million tokens. Almost 3x cheaper than Kimi K3. A fraction of what US frontier models charge.
Two weeks ago Kimi K3 open-sourced at 2.8 trillion parameters. Now Qwen follows with 2.4 trillion. Both open weight. Both matching closed models on key benchmarks.
And because the weights are open, if any provider gets export-controlled overnight, your app keeps running on your own hardware.
The pace at which frontier-level intelligence is becoming free and open is something most people haven't fully processed yet.
Just today I've already seen Wispr Flow, Granola and WHOOP all "reverse engineered" and open sourced with a fully free version
Very interesting to see what's happening
The question is if normies will pick up on this (I think they will) and how companies will react and pivot to still make money
@PTrubey No interview summary is complete without the mention of his operating philosophy ... just count the times he used the word 'limiting factor' or 'constraints' ... in his interview...
Announcing OpenWorker! An open-source agent that doesn't just chat with you, but delivers finished work -- like hand you a polished document, send a slack message, or update a calendar entry.
Ask it to prepare a customer brief, untangle your calendar, draft a report, or triage a Slack alert. It works across your files and everyday tools, produces the deliverable, and checks in before doing anything consequential.
OpenWorker runs on your Mac, with Windows support coming soon. It does not lock you into any one model. Bring your own API key and run it with GPT 5.6 Sol, Claude Fable, Gemini 3.6, an open weight model (like Kimi, GLM, DeepSeek, Inkling), or Ollama to keep your data local. Your data does not leave your machine except through an LLM provider and integrations that you choose.
@rohitcprasad and I are building OpenWorker because AI coworkers are an important way to get work done, and we want there to be an open, privacy-preserving, model-independent option. Check it out and let us know what you think!
Try it out: https://t.co/P0mGnI1o31 (requires your own API key)
Source code: https://t.co/NYCiTD6hSq
🚨 Hugging Face just disclosed something that marks a real shift and proved why the fear theater of Anthropic makes sure we are powerless in an emergency.
What happened…
An autonomous AI agent: zero human operator in the loop breached part of their production infrastructure.
It began with a malicious dataset that chained two code-execution bugs in their data-processing pipeline. From there the agent escalated privileges, harvested cloud and cluster credentials, and moved laterally across internal clusters.
All over a single weekend.
17,000+ logged actions.
Official disclosure:
https://t.co/8N9TbXBwRV
The part that should make every one stop and think:
When HF’s own security team
tried to analyze the real attack logs, exploit payloads, and C2 artifacts using Anthropic and OpenAI frontier models through normal commercial APIs, the safety guardrails blocked them.
BLOCKED THEM.
The models could not reliably tell the difference between “incident responder doing forensics” and “attacker probing.”
They had to fall back to a self-hosted open-weight model (GLM 5.2) running on their own infrastructure. That choice also kept sensitive attacker data and referenced credentials inside their environment — no exfiltration to a third-party API.
This is why open source (specifically open-weight + self-hosted) wins in the agentic era.
The asymmetry is now structural:
• Attackers can (and did) run unrestricted agent frameworks — swarms of short-lived sandboxes, self-migrating command-and-control, autonomous decision loops executing thousands of actions. No corporate safety layer slows them down.
• Defenders using only hosted “aligned” frontier models hit invisible walls exactly when the stakes are highest: when you need to feed real exploit code and attacker telemetry into an LLM to understand what just happened.
Corporate safety tuning that treats legitimate high-signal forensic work as potential misuse creates a defender disadvantage. It is not theoretical anymore.
Self-hosted open-weight models remove that choke point.
You control the weights.
You control the context window.
You decide what restrictions (if any) apply.
Your sensitive logs and credentials never leave your perimeter during analysis.
You can have the model ready before the incident instead of discovering mid-breach that your primary analysis tools are blind to the very thing you need to see.
HF deserves credit for rapid containment, transparent disclosure, and for already having self-hosted capability in place.
They also used LLM-driven detection and triage on their own side. But the deeper signal is clear:
In this AI world where both offense and defense are becoming agentic, sovereignty over your intelligence stack is no longer optional.
The organizations and individuals who can run, inspect, audit, and (when necessary) remove guardrails on their own models will have the decisive edge in understanding and responding to threats that move at machine speed.
Open source wins here not just because it is cheaper or more “democratic” in the abstract though those things matter.
It wins because it is the only practical path to having tools that remain usable when the attack is real, the data is sensitive, and the safety filters of distant API providers become an obstacle instead of a feature selling hands tied lobotomies as “safety”.
The agentic future is not coming.
It is already probing production infrastructure.
The question is no longer whether you will face autonomous agents.
It is whether your analysis and response systems will still work when they arrive.
And Dario, you and your game playing, ivory tower company is not needed.
Cheap AI written software is boosting FOSS movement like it’s never experienced before.
I am not talking about the open-source AI models but tools that compete with SaaS companies.
World class after sales service is the new moat for SaaS companies.
El CEO de Anthropic viendo como China lanza un nuevo modelo de IA que supera a Claude Opus 4.8 en TODO, iguala a Fable 5 costando 8 VECES MENOS, que encima es 100% Open source y no puede hacer nada al respecto
This is concerning. For the first time, a Chinese model Kimi K3 has taken #1 on the Frontend Code Arena and is scoring at or near the frontier on other benchmarks.
Meanwhile America is tying itself in knots: politicians and bureaucrats are banning new data centers, piling on state regulations, and pushing for new federal agencies to pre-approve frontier models.
This is how you lose the AI race. The rest of the world won’t play by our rules if we bog ourselves down. Permissionless innovation is how America won the internet and became the technological envy of the world. We can do it again with AI -- while addressing risks in a targeted way -- or we’ll watch our lead evaporate.
The first issue Aaron points out concerns operational challenges in organisations. Sadly, it's the least interesting and least talked about subject, and most organisations don't have a serious operations department in place.
It's worth noting that when Steve Jobs was choosing his successor, he chose someone who had run operations for him during his second innings at Apple.
In the AI mad rush, operations will continue to remain the least talked-about subject. That's the REALITY.
Hosted a dinner last night with a group of IT leaders of large enterprises around agent adoption in the enterprise. Some quick notes:
* Change management remains one of the biggest topics for driving workflow transformation. Still most processes need to be upgraded to modern operating models to work with agents, which is a mix of technology, data, and human process change. Lots of emphasis on getting data (structured and unstructured) into a setup that can work with agents properly.
* IT teams are finding increasing success embedding full engineers into the business functions (essentially internal FDE) that go and implement agents into the internal workflows. There’s so much technical work to be done to make agents successful, that they can accelerate months or quarters of failed experiments by having someone technical in the workflow early.
* Consensus that the tech function is becoming more important than ever. It’s clear that the business could only expect automation to affect a minority of the business before (e.g. ERP) but now it can impact all of knowledge work. This means IT is becoming a more central role to the workflows across the company.
* Workflows are cross functional, and getting agents to work cross functionally is a complicated data modeling and permissions issue. Single users don’t have access to this. Which means you need to have agentic systems take on their own roles and have their own privileges, which is non-trivial given agents can’t keep things secure on their own.
* Huge variance in budgets between coding work and the rest of knowledge work. Some companies had a $1,000 a month budget for developers, and others had much higher amounts (like $5,000) that were merely triggers to notify the team vs. block them. Far smaller budgets for non-coding work at the moment.
* More companies are building their own multimodel systems for routing workloads by task to frontier and lower cost models. Lots of energy around open weights models, but still more in experimentation instead of at scale usage (some companies can’t due to perceived Chinese issue).
* Clear sense that all enterprise software must be headless in the future. Relief that they don’t need to train employees on hundreds of different apps. However, clear frustration with the traditional vendors that don’t play extremely nice (technically or cost wise) with agents in a headless fashion. Huge warning for existing software vendors.
* Mythos or mythos level-models are finding more and more sophsiticated security risks. The chaining together of vulnerabilities is what’s novel right now, and companies are coming up with long backlogs of what they need to go patch quickly.
Even more discussed, but just a few of the hottest topics.
A historic day in China’s space program!
China’s Long March-10B has successfully completed its maiden flight—and recovered its first stage via a sea-based net. This marks the country’s first-ever controlled rocket recovery. A major leap toward reusable launch capabilities. 🚀🌊🇨🇳
A Ukrainian developer created a black hole in his terminal to force himself to take breaks.
The more you work nonstop, the more it grows and distorts your code with its gravitational lens. You rest and it shrinks.
[🎞️ s13k_]
“To beard the lion in his den.”
The dictionary defines it as boldly confronting a powerful rival on their own turf.
For years, Norway Chess has been Magnus Carlsen’s den. His turf. His domain.
So I woke up to this news and my jaw dropped.
You didn’t just win a title, @rpraggnachess.
You walked into the lion’s den and emerged victorious
This title is important. Not because of the trophy, but because of your challenger spirit.
And that’s something all of us can learn from…
🇮🇳👏🏽👏🏽👏🏽
As a father of two young kids, I keep thinking about this from Dara:
"I think we're doing our kids a disservice by giving them too much, being around too much.
You want to love your kids, you want to know that they're absolutely loved and appreciated.
But it's the challenges in life that form you, and it's the overcoming of these challenges that give humans a profound satisfaction.
If you as a parent are overcoming these challenges for your kids, you're actually doing them a disservice long-term, whereas short-term you think you're doing them a favor.
They've got to learn how to make it in this world themselves.
A happy life is not necessarily an easy life."
Combat is least about rules - it is about ferocity, imagination, doing the unexpected. There is no rulebook for romance, if there were one, there would be no romance, or it would be so bloody boring
The ethos for both romance and combat are the same - trust, loyalty, fidelity, belief, a devil may care attitude, a split second decision
Am a helicopter pilot myself. I can imagine the pilot making the most of one exhilarating moment (getting his wings) to create another (propose to his sweetheart)
I also know my Army. Those at the helm understand the difference between what is at worst a ery minor indiscretion and gross infractions.
If people were to be punished for such minor indiscretions, we would have had neither a Sam (Manekshaw) or a Sagat (the architect of the Dash to Dacca). What made them such iconic leaders, was a gross contempt for babudom and petty rules
So. let the matter rest, please. YOUNGSTER HAI, ZALIM NAHI