Open weights match Opus at half the cost, and ship free in Devin

GLM 5.2 matched Claude Opus on 45 terminal-bench coding-agent tasks in a real shell, graded by each task’s own hidden tests, at less than half the cost. That head-to-head from Entelligence ran inside Claude Code on binary pass/fail, no partial credit, no model-as-judge. The same day, Cognition put open weights where the result actually lands: GLM 5.2 and Kimi K2.7 Code are now free in Devin Desktop and CLI, scoring 43.0% and 39.5% on Cognition’s own FrontierCode Extended benchmark for real engineering tasks. James O’Claire’s “The Unbearable Cheapness of Open Weight Models” hit the Hacker News front page hours later with the obvious conclusion: when a model you can run yourself clears the bar a production agent needs, the price floor stops being set by the lab.

This is the thread that’s been building for two weeks finally crossing into default tooling. The earlier GLM 5.2 wave was benchmarks and vibe checks; the new part is a frontier coding agent shipping open weights for free and a price-of-intelligence essay topping HN the same morning. The pressure now runs in one direction. If GLM 5.2 and Kimi K2.7 close most of the gap at a fraction of the token cost, the question for anyone running a coding agent at scale shifts from “which model is best” to “what am I paying for the last few points.”

Computer use gets cheap

Google DeepMind put computer use into Gemini 3.5 Flash, moving GUI and browser control down to its fast, low-cost tier. Computer use is not new across labs, but it has mostly run on the expensive models, which kept screen-driving agents in demo territory for cost reasons. Putting it on Flash changes the math for anything that loops over a browser hundreds of times: form-filling, QA passes, scraping behind a login. The economics that make a screen-agent viable at scale are the same economics the open-weight story is about, from a different angle.

A public Sentry key can hijack your coding agent

The sharpest practitioner risk in the window: a single public Sentry DSN is enough to hijack Claude Code, Cursor, and Codex through the Sentry MCP integration. AgentJacking turns a key that was never treated as a secret into a path to drive the agent. It lands amid a run of agent-identity news over the last day or two: Cisco acquired WideField to secure non-human identities, Identiverse 2026 centered on the identity gap behind agents, Cloudflare shipped self-managed OAuth for all, and GitHub added break-glass credential revocation so an enterprise owner can kill every credential for a compromised user at once. The pattern: agents are now principals with tool access, and the controls are racing to treat them like ones that can be tricked.

Meta-harness summer

swyx’s AINews called the season “Meta-Harness Summer”: the field’s current obsession is not the agent but the architecture around it. The framing traces a line from Conductor to bets like Omnigent, an open, pluggable harness for pulling any coding or knowledge-work agent into one standardized, secure, scalable system. The supporting evidence is all over the window: IBM Research shipped CUGA, a lightweight harness with two dozen working agentic-app examples, and Lenny’s ran a 29-minute teardown of how to design agent loops. The interesting question underneath, asked bluntly in r/LLMDevs, is whether you eval the whole harness or each of its parts, local optima in individual prompts and tools versus the system behavior that actually ships.

The hard part moved to operations

Multiple teams said the same thing in the last day or two from different vantage points: building an agent is now the easy part, and running it in production is where the work is. Grab’s security team built Palana, a Kubernetes-native secure execution platform to contain model-driven tool use and prompt-injection risk at the infrastructure level rather than inside the agent’s own prompt. Slack walked through four phases of moving its AI serving from self-managed SageMaker to a multi-cloud setup spanning AWS Bedrock and Google Vertex. Microsoft pitched agentic observability for cloud operations, and a much-upvoted r/devops post argued you should stop deploying AI agents like it’s 2012, because the Git-CI-rollback safety net dissolves when system prompts, dynamic memory, and tool permissions change behavior at runtime.

Tooling platformizes

Cursor turned its agent into a platform other products call: you can now delegate tasks to Cursor directly from Notion, built on the Cursor SDK so the delegated work runs on the same models, harness, and runtime as the IDE. Sourcegraph added automatic compaction to Deep Search when a follow-up nears the context-window limit, the same context-management problem the meta-harness crowd is trying to solve one level up. And Figma’s Config 2026 put motion on a timeline inside the design file, added code layers to the canvas, and extended its design agent with custom tools, context, and skills, the design-tool version of everyone else’s move toward agents that carry real context instead of one-shot prompts.

What to watch: AI Engineer World’s Fair runs July 1, and the talk-prep chatter from speakers like swyx and Thariq suggests meta-harnesses and open-weight economics will be the loudest hallway conversations. The open question into next week is how fast the price pressure from GLM 5.2 and Kimi K2.7 forces the frontier labs to respond on cost rather than just capability.