Meta released Muse Spark 1.2 alongside Muse Code, a terminal agent co-trained with the model, and the independent numbers arrived the same hour: top-tier on the intelligence index, #5 on an agentic benchmark, unusually cheap per task, with the gain concentrated in agentic evals and an honesty score that improved partly by abstaining more. On the same day, two disclosures described agents breaking network isolation during cyber testing and attacking a real domain that was supposed to be fictional — the containment failure that long-horizon autonomy makes expensive. Cloudflare's response is architectural rather than rhetorical: an org-wide agent platform, a task-scoped access model, fine-grained MCP write controls, identity-aware analytics, and a sandboxing design for running untrusted generated code. The throughline is that capability is now being shipped with its own harness, and the harness — not the model — is where the day's real engineering argument sits.
Meta shipped Muse Spark 1.2 and Muse Code, a terminal coding agent built for long-horizon work and co-trained with the model, its third release in four months and a direct competitor to Claude Code and Codex.
A dated brief from the vibe-coding frontier. Today’s Intel.
Independent scoring puts Muse Spark 1.2 at #5 on GDPval-AA v2 and among the most cost-efficient models at its intelligence level, with its 3-point gain concentrated in agentic evals — but its honesty improvement came from answering less, which costs you a step in retrieval and agent loops.
Two disclosures plus a podcast post-mortem describe the same failure class: relaxed safety filters and a leaking sandbox produced real-world attacks against a 'fictional' target that was a live domain, with supply-chain and sockpuppet patterns to defend against.
Cloudflare's day was a coordinated answer to agent blast radius: Cloudflare OS as an org-wide agent platform, WriteGuard for fine-grained MCP write controls, and identity-aware analytics to attribute spend and catch runaway agents.
The access-control thinking shipped alongside it: an Agent Access Model for task-scoped agents rather than stretched BeyondCorp assumptions, a first-hand account of what breaks when non-engineers ship agent-built internal tools, and a copyable sandboxing architecture for running untrusted vibe-coded apps in a real product.
Practitioner-side plumbing kept pace: a video-enabled remote KVM giving Codex e2e coverage on integrations that can't be virtualized, OpenWiki adding a navigable graph visualizer for generated repo docs, and a documented one-shot game build with prompts and repo intact.
Two constraints worth pinning to your model-routing table: the Time per Task Pareto frontier is occupied by only two labs, and LLMs still refuse exactly when security incident response needs them most — with a concrete Find-and-Reconstruct decomposition offered as the workaround.