ngLover

A 2026 NBER study quantified something a lot of engineering teams have already felt: AI coding agents increased commit rate by 180%, but software releases only grew by 30%. That gap is the story. You did not solve your velocity problem by adopting Claude Code or Cursor. You moved it downstream. On July 29, BrowserStack launched Test Companion , an agentic test automation tool built directly into the IDE. It's worth understanding why it exists and what it tells you about where AI tooling is headed. What the 180/30 Gap Actually Means When a coding agent can spin up a full feature in an afternoon, the constraint shifts. It's no longer "how fast can we write the code." It's "how fast can we trust that code enough to ship it." I've seen this play out on teams using Claude Code seriously. Output goes up fast. But PR queues get longer, QA cycles stretch out, and the release cadence barely moves. The agents didn't fix deployment velocity. They expo...

On August 1, 2026, OpenAI announced Astra, calling it their next major model family. They didn't release a product. They dropped a GitHub repo containing Lean 4 certificates formally verifying ten solutions to open problems in mathematics, some unsolved for over a decade. The standout: a construction proving non-sofic groups exist, a question Mikhail Gromov posed in 1999 that sat open for 27 years. The estimated token cost to find all ten solutions: roughly $2,000 at Sol API rates. That's about $200 per problem spanning group theory, von Neumann algebras, quantum complexity, and lattice cryptography. Sit with that number for a moment. What Astra Actually Is Astra is not a public product yet. OpenAI is positioning it as a model family built for long-horizon multi-agent work. The design is explicit: multiple agents working together on a single task for hours or days, not seconds. The system plans, tests its own output, revises, and keeps going without needing you to steer ea...

n8n shipped a significant update on July 29 that I've been waiting for since they announced MCP integration earlier this year. The headline: n8n now works as both an MCP client and an MCP server. That's not just a configuration option. It changes how you think about the workflows you've already built. What the July 29 Release Actually Shipped Four things worth paying attention to (full details in n8n's release notes ): Native MCP server mode. Any n8n workflow can now be exposed as a callable tool to external AI clients. Claude Desktop, a custom agent, your own LLM-powered interface. If the client speaks MCP, it can call your workflow. You toggle this at the workflow level, or bulk-enable it across an entire project folder from the new folder actions menu. Native MCP client mode. n8n's AI Agent nodes can now discover and call external MCP-compliant tools directly, without you writing a custom API wrapper or an HTTP request node. The agent resolves the tool lis...