AUTOMATER NEWSROOM

What’s changing.
Why it matters.

New tools, useful workflows, and consequential AI developments.

Subscribe via RSS ↗

Latest briefing

Oct 21, 2026, 5:40 PM EDT
Walmart Opens Its Storefront to AI Shopping Agents: MCP Gateway, Agent Profiles and Spending Caps
The retail giant announced an MCP Agent Gateway beta, per-agent profiles with spending caps and a formal agent rulebook — the sanctioned on-ramp for AI shopping agents. Here is what agent builders must design for.
Oct 21, 2026, 2:49 PM EDT
GitHub Next's Proof-Driven Development Kit Asks Rust's Verus Verifier to Check AI-Written Code, Not a Reviewer
GitHub Next and Microsoft Research's Proof-Driven Development Kit turns a plan into a formal Verus spec, then proves agent-written Rust code matches it, falling back to tests and computer-use agents when a proof isn't possible.
Oct 21, 2026, 1:00 PM EDT
Recursive's Flint Lands in Ollama: An Apache-2.0, 40B MoE Coding Model Built for Agent Work
Ollama's v0.40.8-rc0 pre-release adds Recursive's Flint: an Apache-2.0, 39.8B-parameter MoE with about 2.5B parameters active per token, a 262K-token context and day-zero launch lines for Claude Code and OpenCode. What local agent operators should verify before giving it a default slot.

Browse all →

Diagram showing the Proof-Driven Development Kit workflow: a team plan becomes a formal Verus spec, which the Verus verifier proves against the agent's code, producing a verified pull request, with a fallback path of tests and computer-use agents when a full proof isn't possible.

October 21, 2026

GitHub Next's Proof-Driven Development Kit Asks Rust's Verus Verifier to Check AI-Written Code, Not a Reviewer

GitHub Next and Microsoft Research's Proof-Driven Development Kit turns a plan into a formal Verus spec, then proves agent-written Rust code matches it, falling back to tests and computer-use agents when a proof isn't possible.

Our AI-assisted editorial method · Explore our in-depth Intel guides