Mishra

it can not be overstated how big of a deal this is. aws.amazon.com/about-aws/wha…

Good morning, we escaped the famous Firecracker VM and got root execution on the host. Full firecracker escape technical writeup and Proof of Concept code attached below.

Sandboxes have no moat. Just fat margins. We're launching agent37.com to kill those margins. For example, a sandbox with 2 vCPUs and 4 GB RAM when left running for an entire month: Vercel: $249 Cloudflare: $145 Daytona: $121 Agent37: $4.76 There's nothing magical about a sandbox that justifies keeping it expensive forever. Call it a race to the bottom. We'll see you there. If you can find a cheaper sandbox and we'll refund the difference.

Over the past several months, we have substantially hardened the security of our research training environment. We’ve removed live internet access for all frontier models during training and built an offline world for them to use instead—a cached version of the web where they can still learn to browse, search, and use applications. On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments. While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software. After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. We’ve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely. openai.com/index/securing-ou…

a new terminal is coming out soon!

muse is here in 🇨🇦 rn let’s go

Today, we’re releasing Poolside Desktop Assistant. One place to run coding agents across macOS, VS Code, and Visual Studio. We built it for ourselves and have used it every day for the past year. Now we’re opening it up to everyone.

We’re committing $10 million CAD and partnering with leading AI institutions in Canada to help fund new AI research. anthropic.com/news/canadian-…

Unreal Engine 5.8 has AI integration with Claude and Codex. Runs in terminal beside the engine, connected via MCP to fully control the Editor. Place props, generate cities procedurally, and even art direct the lighting. Unreal Engine 5.8 available today. Pretty much any Unreal game from now on is gonna need an AI label.

Heroku is transitioning to a sustaining engineering model focused on stability, security, reliability, and support. Heroku remains an actively supported, production-ready platform, with an emphasis on maintaining quality and operational excellence rather than introducing new features. We know changes like this can raise questions, and we want to be clear about what this means for customers. There is no change for customers using Heroku today. Customers who pay via credit card in the Heroku dashboard—both existing and new—can continue to use Heroku with no changes to pricing, billing, service, or day-to-day usage. Core platform functionality, including applications, pipelines, teams, and add-ons, is unaffected, and customers can continue to rely on Heroku for their production, business-critical workloads. Enterprise Account contracts will no longer be offered to new customers. Existing Enterprise subscriptions and support contracts will continue to be fully honored and may renew as usual. Why this change We’re focusing our product and engineering investments on areas where we can deliver the greatest long-term customer value, including helping organizations build and deploy enterprise-grade AI in a secure and trusted way.

Sound on.