Greg Bell

Legal education is about to change. Today, we’re launching the Legal AI Scholars Program in collaboration with leading law schools. AI is becoming a core part of how legal work gets done. Graduates need to understand how to use it effectively, responsibly, and in real workflows. Together with faculty, we’re developing a curriculum focused on applying AI to legal tasks, understanding its strengths and limitations, and developing the judgment required to use it well. The program is already rolling out across select schools, with more to follow in key jurisdictions over the coming months. I can't wait to help shape a generation of lawyers better equipped to navigate how the profession is changing together with all of our great partners. Full story: legora.com/newsroom/legor…

Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

This feels like physical product design's ChatGPT moment. This team just ran an autonomous agent against the entire chip design process: 219-word spec in, tape-out-ready silicon layout out, 12 hours later. The agent ran continuously against a simulator, found its own bugs, rewrote its own pipeline, and iterated to a working CPU! Chip design costs well over $400M and takes up to 9 years. Not because writing hardware code is hard (it is actually brutally hard) but because a respin costs 10 of millions. So teams spend more than half their total budget just verifying the design is correct before a single transistor is placed. That cost structure is why most chip designs never get built. Entire product categories that were previously too low-volume to justify a tape-out are now buildable.

if your skill depends on dynamic content, you can embed !`command` in your SKILL.md to inject shell output directly into the prompt Claude Code runs it when the skill is invoked and swaps the placeholder inline, the model only sees the result!

I have been dreaming of this day for a long time. Arena is now a book publisher, and our first volume, "Silicon" is open for preorders. It's quite unlike anything you've seen: a coffee table book capturing the ecstatic beauty of silicon technology. arenamag.com/silicon

@simonw “He fed the paper to Claude Code and used a variant of Andrej Karpathy's autoresearch pattern to have Claude run 90 experiments and produce MLX Objective-C and Metal code that ran the model as efficiently as possible.” I love how quickly this technique is growing

Wrote a bit more about this on my blog simonwillison.net/2026/Mar/18/ll…

Dan says he's got Qwen 3.5 397B-A17B - a 209GB on disk MoE model - running on an M3 Mac at ~5.7 tokens per second using only 5.5 GB of active memory (!) by quantizing and then streaming weights from SSD (at ~17GB/s), since MoE models only use a small subset of their weights for each token

Happy 80th anniversary, ENIAC spectrum.ieee.org/eniac-80-ieee-…

$550M Series D led by @Accel. $5.55B valuation. One year into our U.S. expansion, we’re doubling down: accelerating across America and building AI with the lawyers who use it every day. Grateful to our customers, partners, and team. More: legora.com/blog/series-d

Today, we announced our acquisition of Walter AI. They’ve built agent-native systems alongside lawyers that handle real workflows. We share the same blueprint for the future - and I'm excited to welcome the Walter team to @WeAreLegora! legora.com/newsroom/legor…

@waltersoftware Thank you! I could not be more excited about joining this amazing team with so much opportunity ahead of us. 🚀🚀🚀

@emilykeyyyyyyyy 😂🔥

Big congrats to everyone at @1Password! 🇨🇦🚀

@debracleaver Thanks! Looks like our Heroku instance is VERY old. Working on getting it back up and running now.

@theemilykey Yay! Does this. Mean I get to buy some raspberry pi’s and program our mirror!?!?

Chaos engineering is one of the best ways to test (and thus improve) the performance and resilience of your distributed systems. AWS Fault Injection Simulator makes it easier and safer to run chaos engineering experiments on AWS. Coming soon! aws.amazon.com/fis/

Big #shoutout to the S3 Replication team in #YVR who shipped all these features! Amazing team, building big things 👏🎉🔥

Second 🚀, we added support for two-way replication. This feature gives you the flexibility of replicating object metadata changes for two-way replication between buckets aws.amazon.com/about-aws/what…

🚀A couple of great launches yesterday from our S3 Replication team. First, we launched multi-destination replication rules. You can now replicate from a single source to multiple destination buckets... aws.amazon.com/about-aws/what…