What AI agents can actually do for your business today

What we're tracking

• •How much support an AI agent really closes The most useful number of the day came from a review of real resolution rates across thirteen vendors. "Resolution rate" sounds precise but hides a choice: does it mean the customer's problem was solved, or only that the conversation ended without a human stepping in? When you compare tools, insist on the second, stricter reading, because the first is easy to inflate.
• •Letting an agent act without letting it improvise If the first story is about how much an agent can do, the second is about how to let it do anything safely. Salesforce published a piece on giving AI autonomy without, in its words, letting it run wild. The mechanism it describes is worth understanding because it is becoming the standard pattern: pair the part of the system that is good at open-ended reasoning with a separate part that enforces fixed rules.
• •Folding agents back into the workflow Zapier made a change today that reflects where thinking about agents has moved. It is retiring Zapier Agents as a separate product and folding its capabilities into the ordinary automation editor. In the company's description, "Every capability that made Zapier Agents powerful — tool calling, reasoning, autonomous action — now lives inside a single AI step in the Zap editor, using AI by Zapier" [3].
• •Building for when the author is a machine GitHub described rebuilding the infrastructure underneath its version-control system to prepare for a future where far more code is written by agents than by people. In its framing, the company is "rebuilding GitHub's Git infrastructure while GitHub keeps running, creating a foundation for agent-scale software development" [4].
• •When writing code by hand becomes the exception The sharpest statement of the day came from Basecamp's David Heinemeier Hansson, who used a talk at a developer conference to argue that hand-writing code is on its way to being the exception rather than the rule. He recounts: "Two weeks ago at Rails World, I told my fellow programmers that it's time to put down the pencils" [5]. His reasoning is economic, not sentimental — "We're not going to write the vast majority of code by hand any longer" [5].
• •What ties the day together Read across all five, and the thread is clear: the industry is settling into a view where agents do a great deal but finish less than the marketing implied, and where the safe designs are the ones that keep a human and a set of fixed rules in the loop. That is a healthier place to be choosing tools than a year ago, because it lets you ask better questions. What share of the work does this finish alone, measured honestly? Which decisions are governed by rules the model cannot override? Where does the handover to a person happen, and can I see it?