Vercel Sandbox switches to versioned managed images
Sandbox runtimes deprecated in favor of versioned container images (universal, node, python, ubuntu, arch) pinned or rolling via tags, defaulting to Ubuntu with Node 24, Python 3.14, and preinstalled coding agents.
Eliminates custom image builds for most workloads and guarantees automatic security patches nightly while maintaining reproducibility via digest pinning. Shifts from Amazon Linux to Ubuntu aligns local dev environments with broader industry standard.
Replaces the deprecated `runtime` property with `image` property; existing code still works but should migrate. Requires SDK version 3+. Ready now—no breaking changes for existing sandboxes, but new projects should adopt managed images immediately to get automatic updates and smaller footprint.
- “Starting with version 3 of the Sandbox SDK, new sandboxes default to `vercel/sandbox/universal:latest`”
- “Every managed image gets a nightly release”
- “Rolling tags such as `latest` and the major-version tags pick up operating system and dependency updates automatically, including security patches and new releases of Node.js, Python, and the preinstalled coding agents”
- “The universal image switches our default operating system from Amazon Linux to Ubuntu”
- “The previous `runtime` property is deprecated, not removed, so existing code keeps working”
vercel-sandboxcontainer-imagesdeploymentmigrationsecurity-patching
Bun.serve now deploys directly on Vercel Functions
Drop `Bun.serve()` into Vercel Functions without framework wrapping; WebSocket support routes to Fluid compute with per-message billing.
Eliminates the adapter layer between local Bun development and Vercel deployment—what you test locally deploys unchanged. WebSocket pricing shifts from connection time to CPU time, making real-time apps cheaper to operate at scale.
Replaces framework-based function wrappers for Bun projects. Requires setting `"bunVersion": "1.x"` in `vercel.json` and restructuring entrypoints to use `Bun.serve()`. Ready now for new projects; existing Vercel function code needs migration. Worth trying if you're already in the Bun ecosystem.
- “The Bun runtime for Vercel Functions now supports Bun.serve() as a function entrypoint, including WebSocket handlers.”
- “The server you run locally with Bun deploys as-is, without being wrapped in a framework.”
- “WebSocket connections run on Fluid compute with Active CPU pricing, so you pay only for time spent processing messages, not idle connection time.”
- “Enable the runtime by setting "bunVersion": "1.x" in vercel.json.”
bunvercel-functionswebsocketsdeploymentruntime
Claude Code auto mode becomes default for Pro users
Anthropic defaults Claude Code to autonomous tool execution with a classifier that blocks irreversible actions instead of prompting, eliminating approval friction while matching human safety decisions.
Removes manual approval overhead that causes reflexive clicking (97% approval rate) and cuts session interruptions, letting long-running tasks complete unattended. Pro/Max/Team users get this automatically starting August 14; Enterprise admins retain control.
Replaces manual permission prompts with a learned classifier that routes tool calls through safety gates. Requires nothing—opt-in status remains on API/Enterprise/cloud platforms until next month. Safe to adopt now if you're on Pro/Max/Team; production data shows it catches 89% of dangerous commands vs. 13.6% human detection rate.
- “auto mode matched or outperformed manual review”
- “users approve 97% of permission prompts in Claude Code”
- “human review caught just 13.6% of dangerous commands, while auto mode caught 89%”
- “Among Teams & Enterprise adopters, auto mode users ship about 25% more PRs”
- “starting on August 14, new sessions on Pro, Max, and Team plans will run in auto mode”
- “we're no longer charging Claude Code users on Pro, Max, and Team plans for that classifier overhead, effective today”
claude-codeagent-autonomysafety-classifierworkflow-automationrelease Meta releases Muse Glimmer open weights model
30B dense multimodal model optimized for local agent loops, quantizes to 18GB 4-bit, ships with logit distillation from frontier base and agentic training data.
Eliminates API dependency for agent workflows; developers can now run always-on local inference on consumer hardware without cloud latency or per-token costs. Reduces friction for building stateful agent systems.
Replaces cloud-first agent APIs (Claude, GPT) for local inference use cases. Requires 18GB VRAM minimum (4-bit) or 60GB (BF16), quantization tooling, and agentic prompt engineering. Worth trying now for offline-capable agents; benchmark data shows competitive tool-use performance but weaker hallucination control than peers.
- “Muse Glimmer, a 30B dense, multimodal, agent-focused model under Apache 2.0”
- “designed for long-horizon agent loops, tool use, and local deployment”
- “~18GB 4-bit, 128K context, and memory-efficient hybrid attention suitable for single-node deployment”
- “logit-distilled from Muse Spark and trained from the outset on agentic traces”
open-weightslocal-inferenceagent-loopsquantizationmultimodal
Cloudflare Workers deploy without account setup
wrangler deploy --temporary spins up live Workers on ephemeral accounts valid for 60 minutes, eliminating OAuth/MFA friction in agent-driven workflows.
Removes authentication bottleneck that blocks autonomous AI agents from deploying code. Developers can prototype and test Workers instantly without account creation overhead, then claim the deployment into permanent ownership.
Replaces the manual account-setup → OAuth → MFA → token-copy workflow for agent deployments. Requires Wrangler 4.102.0+. Worth trying now for agent-driven CI/CD and copilot workflows, but watch claim-URL security and 60-minute expiry window in production scenarios.
- “wrangler deploy --temporary”
- “accounts and their deployments expire automatically after 60 minutes”
- “This temporary deployment stays live for 60 minutes, during which time you can claim the temporary account, making it permanently your own”
- “temporary accounts are subject to rate limits and abuse-prevention checks”
- “require that claim URLs be handled securely because they grant account ownership”
- “requires Wrangler 4.102.0 or later”
cloudflare-workersai-agentsauthenticationdeployment-automationwrangler