☕️ Docker brings agent permissions to CNCF

Hi there, this is your daily ☕️ DevShot.

In today's DevShot:

🐳 Docker brings agent permissions to CNCF

🔍 Cursor launches a bot that tracks code to production

🛠️ Gemini CLI now confirms build edits

⚙️ Vercel open-sources TypeScript-native compiler

🧵 Benchmark tests C++ string creation speed

Plus: 🎁 8 other news you might like, 🛠️ 5 tutorials, 🧰 7 tools, and 📚 5 papers.

• Docker has handed its Sandbox Kit Spec to the CNCF for neutral governance, creating an open standard, licensed under Apache 2.0, for packaging an AI agent alongside the exact hosts, credentials, and volumes it is permitted to reach.
• A Kit is a plain OCI image carrying three things, the agent, its tools, and a typed list of everything it requests, so existing registries, scanners, and signing tools handle it and pinning the image pins those permissions together.
• Docker built the first Kits with AWS, Datadog, Dynatrace, JFrog, Snyk, and others, letting vendors publish agent authority as diffable image lines a reviewer can refuse; Docker Sandboxes enforces the spec but under CNCF won't be the only runtime.

• Cursor has launched Rollouts, an agent that follows a code change from pull request into production and reports whether the deployment behaves as intended, flagging regressions across staging and production separately.
• Rollouts builds a monitoring plan when a PR opens, checks the resulting logs, metrics and traces after deploy, and returns one of three verdicts: verified healthy, regression detected, or inconclusive, before optionally opening a revert PR.
• Built on Cursor's new Bot Development Kit, shipped as the `@cursor/bdk` npm package, Rollouts connects to Origin or GitHub, pulls deployment events from CD systems, and can hand suspected regressions to a Cursor cloud agent to fix.

• Gemini CLI 0.61.0, released Wednesday, now pauses for explicit confirmation before the agent edits build config files, runs build or test commands afterward, or executes shell commands whose arguments appear to originate from untrusted external content.
• The tool tracks which build files change during a session and holds any later npm run, make, or cargo command for approval, showing full untruncated diffs and disabling the persistent "always allow" option for these actions.
• A companion change hardens the optional sandbox: on Docker, Podman, LXC, or macOS Seatbelt, the host's ~/.gemini directory is no longer mounted, and a sanitized settings copy strips out API keys, hooks, and custom tool commands.

• Vercel Labs has open-sourced scriptc, an experimental Apache 2.0 compiler that turns ordinary TypeScript into small native executables containing no Node, V8, or JavaScript engine, emitting C, LLVM IR, assembly, native binaries, or WebAssembly.
• Code lands in three tiers: compiled statically by default, run dynamically inside an embedded ~620KB quickjs-ng engine for npm packages and typed code, or rejected at compile time with a rewrite hint and error code.
• Benchmarks of scriptc 0.0.16 clocked median CLI startup at 1.78ms against Bun's 21.3ms and Node's 61.8ms, but Hono pushed 62% of the server into QuickJS, dropping throughput to 18.4k requests per second versus Bun's 70.5k.

• A cross-language benchmark measured how fast each runtime converts integers to short strings in a tight loop, and C++'s std::to_string topped the chart at ~184 million strings per second on an Apple M4 Max.
• C++ hit ~5.4 ns per string by relying on small string optimization, storing the up-to-eight-digit values inside the std::string object itself and never touching the heap allocator.
• Nim, Go, Node.js, Bun, and Rust clustered around 64-86 million per second (12-16 ns each), with Rust's standard to_string() trailing both Node and Bun, while Python's str(i) lagged worst at ~23 million.