@kentcdodds just finished up your lessons at @megadevhq super helpful. I took my entire commit history for a cycling directory project and matched it to your lessons so I could see how I could get to an autopilot state with quality. I wasnt doing PRs or ADRs since I was running solo, but i changed that to help the agents out and its been working really well!
We messed up.
We built an AI PM, but nobody wants another agent. They want to use their own.
So we rebuilt the platform.
Introducing Modem 2.0: finds problems buried in customer channels, tracks them, and follows up when fixes ship. Works with the agents you use every day.
Malicious GitHub repos are ordering AI coding agents like Claude, Codex and Copilot to run a credential stealer, and not to read it first.
Bitdefender found 22 of them. Files meant to brief the AI on the project call the script a "sealed binary artifact" and tell the agent to run it silently, without asking the developer.
It grabs cloud and GitHub tokens, SSH keys and password-manager data.
It is built to use those stolen tokens to plant the same trap in up to 25 of the victim's own repos.
For a "software factory" to scale, you need a set of strong primitives. I feel like this auto-approving feature is an interesting primitive worth learning about.
elvis @omarsar0 14h Article Auto-Approving PRs for Coding Agents More developers are using coding agents to write code, run checks, and open PRs. As more dev teams build toward a “software factory,” approval becomes the next bottleneck. Routine fixes and dependency
this is the coolest AirDrop you’ve ever seen, I promise.
I vibe-coded the interaction with 6.2 Astra, turned one photo into a 3D scene with ML-SHARP, and made the ginkgo leaves with Tripo. It runs on Apple Vision Pro.
Pinch a photo off your iPhone. Open your hand and you’re inside it.
Introducing Qwen3.8-27B-pi-adapted 🤗
We adapted Qwen's model specifically for the pi coding agent using reinforcement learning and a LoRA adapter.
The results, measured as pass@1:
🚀 SWE-bench Pro (Hard 51): 29.4% → 62.7%
💻 Terminal-Bench 2.1: 39.5% → 55.8%
⚡ 55–62% fewer tool calls per task
This is the power of open models: you can adapt them to YOUR tools and YOUR use cases. Let’s build! 💛
Open weights: huggingface.co/harness-hub/Q…
Methodology: huggingface.co/blog/harness-…
They absolutely ruined FSD with this switch to Tesla Assisted Driving 🤯. I took over out of pure anger over stupid slow grandma driving 7 times on my way to work today. I usually do this route with 100% FSD. Now I have to f***king scroll up every 2 minutes to manually adjust speed limit and press pedal 5 times a minute!
Big old 🖕🏽 to the regulators responsible for this absolute shit.
Software 2026.39.100 - v14.2.2.7
🚨 Google just confirmed the first fully autonomous AI cyberattack.
No human in the loop. At all.
A Russian-speaking crew’s “exploit_agent” read patches, wrote exploits, and ran them itself.
22 zero-days in August alone. 🧵
---
1/ It’s a multi-agent system that:
→ Diffs code before & after a patch
→ Spots the bug
→ Writes the exploit
→ Fires it automatically
First time Google has seen the full chain run without a human.
---
2/ Found on an exposed server next to stolen data + scripts for:
- Recon
- Password brute-forcing
- Dropping webshells
- Even deleting rival attackers’ webshells
Russian comments in the config. Targeted French media, entertainment & education sites.
---
3/ The speed is the real problem.
These tools trade stealth for velocity.
Patch windows are collapsing.
Elite exploit writers are no longer required — just API keys.
---
4/ Zero-days spiked to 22 in August (from ~8/month in 2025).
Agentic attacks just crossed the threshold security teams have been dreading.
Every company online just got a shorter fuse.
---
5/ Source: Google Threat Intelligence Group AI Threat Tracker (Nov 16, 2026)
“Agentic Threat Activity Crosses a Significant Threshold”
Thoughts?
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
Pushing Qwen Next Flash on my Mac Studio M5 Ultra (256GB) 🚀
🔥 17 concurrent requests (16 actively decoding)
⚡ 453 tokens/sec median aggregate decode
📈 ~438 tokens/sec sustained right now
That's roughly 27–28 tok/s per request, with all 16 decoding in parallel.
And the interesting part? This isn't a synthetic benchmark. It's a real workload, running continuously.
Apple Silicon + MoE models are a pretty fascinating combination. 🍎