I'm happy to share that Mojo and MAX are now fully open - for development, extension, and commercial use! This includes the full Mojo programming language, but also the MAX graph compiler, MLRT runtime internals, and hardware abstraction logic. Get your agents going!👇

Ruby 4.0.8 Released ruby-lang.org/en/news/2026/1… This is a routine update that includes bugfixes. We recommend upgrading your Ruby version at your earliest convenience.

You've gotta patch your dependencies super fast because they're full of vulns (PHP, Node, eMudhra, etc), but not _too_ fast because they're full of backdoors (LiteLLM). Good luck!

What’s the common theme behind 4, 56, 66, 115, 155, 156, 230, 237 except that they are all really terrible private keys? Someone please give me a hypothesis how that happened.

The last agent harness.

Here's a repo demoing these compound AI patterns with DSPy + Jev! github.com/cmpnd-ai/dspy-sys…

I want to share how I have developed celld - because it's a bit different and it's working well for me. You might have noticed that the github.com/denoland/celld repo is pretty bare - this is because it's an export of a much larger private repo: denoland/celld.dev This larger repo contains: an llm-wiki with an enormous amount of design docs, a large test suite, a spec written in TLA+, the code for the website, scripts for spinning up fleets of celld instances on various clouds and running tests against them, and a speculative centralized managed control plane that I might someday release as a commercial product. My llm-wiki is modified to fit my workflow - diff here gist.github.com/ry/c56dfa7b1… I find llm-wiki extremely useful for gathering context. Reviewing wiki/design/ is a primary development activity. celld is open source, but the development happens in private. The test suite and design docs are private. Why do this? First of all, I don't need the public following my every commit - it's oversharing. Secondly, in the age of coding agents, I don't really need external contributors. I'll always appreciate a patch, but most properly reported issues are one-shottable solutions. Third, it's just a bit of IP that might be valuable someday. I do a lot of experiments with celld on Vultr with a VPC. I'll spin up between 2 and 10 VMs at a time, run some experiment, and usually try to tell some story via a chart of some sort (one below). My own coding agent setup is ssh/tmux to mac mini, with various codex and claude sessions running. I don't use an enormous number - something like 2-4 at a time. (Why a mac mini? idk someone just gave me it)

IMO less than 6 months before Anthropic offers repository hosting