--- title: "Market Pulse" canonical: "https://current.tinyfish.ai/issue/38/market-pulse" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/38/market-pulse" issue: 38 section: "market-pulse" description: "Reading the agent ecosystem through a practitioner's lens" authors: ["Sevda Polat","Rina Takahashi","Nora Kaplan"] published: 2026-07-20 updated: 2026-07-17 articles: 20 --- # TinyFish > CURRENT is a journal about AI agents in production, for the engineering and product leaders who have to make them work. Drawing on experience building enterprise web agents, it explains why the demo succeeded and the deployment didn't, and what that means for choosing vendors, briefing the board, and avoiding mistakes others have already made. [Read on the website]() ## Issue 38 — Market Pulse Reading the agent ecosystem through a practitioner's lens ### Review-Shaped Work - [The Infrastructure for Arguing Back]() — By [Sevda Polat]() · Published 2026-07-15 · Format: Review-Shaped Work Microsoft's coding-agent study reports a 24% increase in merged pull requests across tens of thousands of engineers, then the authors quietly concede that merged PRs are an output proxy, not delivered value. That concession matters more than the number. It points toward a structural question the usual conversation about agent adoption keeps skating past: the predictor of durable adoption may not be task complexity or model capability, but whether a domain already has organizational machinery for catching mistakes, contesting outputs, and reversing course before the cost lands on whoever is least equipped to absorb it. ### Review Readiness Map Agents produce output. Whether a domain can actually absorb that output, challenge it, trace it back, fix it when it's wrong, depends on review infrastructure that mostly predates the agent era. Some workflows have spent decades building exactly this machinery. Diffs get reviewed. Transactions get disputed. Cases get escalated. Others have almost nothing standing between a generated number and the slide deck it lands in. That gap matters more than most deployment conversations acknowledge, because standing up review mechanisms with real institutional weight takes far longer than deploying the agents that need them. Six domains, mapped by how ready their existing plumbing is to catch agent mistakes. - **Code Has the Review Muscle Already Built** — [Source]() — Published 2026-07-15 Tag: Code Review Review-readiness: High. Diffs, CI pipelines, tests, ownership rules, rollback. The full stack predates agents entirely. But Microsoft's deployment study flags a telling gap: adopters merged ~24% more PRs, yet merged PRs measure throughput, not value. The review surface works. What "good" means still doesn't. - **Payment Rails Were Built for Exactly This** — [Source]() — Published 2026-07-15 Tag: Agentic Payments Review-readiness: High. Authorization, tokenized credentials, spending limits, chargebacks, Visa's 120-day confirmation window. Decades of dispute machinery. The hole: when user consent and merchant processing are both valid but the agent misread what the user actually wanted. No dispute code covers that yet. - **Escalation Paths Exist, Case Memory Does Not** — [Source]() — Published 2026-07-15 Tag: Customer Support Review-readiness: Medium. Queues, escalation tiers, QA sampling all exist. Context handoff is where things fall apart. Nubank reports a 37-point NPS gain; a Taobao experiment finds shorter chats with worse ratings. Containment numbers can look great while the record handed to the next human gets thinner. - **Agent Numbers Reach Decisions With No Checkpoint** — [Source]() — Published 2026-07-15 Tag: Enterprise Analytics Review-readiness: Low. No query lineage, no metric definitions, no caveats attached. Numbers land in decks and dashboards and become organizational fact. EntSQL's best system hit 15.9% accuracy on real enterprise questions. Plausible-sounding answers failing the actual business question, with nothing between generation and belief. - **Some Connectors Are Governed, Many Are Bare** — [Source]() — Published 2026-07-15 Tag: Internal Tools Review-readiness: Varies. Enterprise workflows with approval chains sit alongside tool surfaces exposed via MCP that carry no authentication, no mandate, no audit trail. A 2026 survey found 40.55% of remote MCP servers exposed tools without authentication. The protocol's authorization layer remains optional by spec. - **Sites Recognize Agents but Lack Shared Terms** — [Source]() — Published 2026-07-15 Tag: Web Access Review-readiness: Low-Medium. Cloudflare's search/agent/training taxonomy gives sites new classification levers. But classification alone isn't review. A fingerprinting study showed agents bypassing anti-bot systems while remaining distinguishable from humans. Sites can tell what's visiting. They just can't agree on what to do about it. ### Coding Agent Evidence - **Adoption and Impact of Command-Line AI Coding Agents: A Study of Microsoft's Early 2026 Rollout of Claude Code and GitHub Copilot CLI** — [Source]() — Published 2026-07-15 Across tens of thousands of Microsoft engineers, coding-agent adopters merged roughly 24% more PRs. Retention tracked coding activity, not demographics. The authors are careful to note merged PRs measure output volume, not delivered value. Why PRs specifically? Agents gain traction where artifacts already flow through diffs, tests, CI, and rollback, making machine-generated work institutionally legible. Does more output mean more value? The authors say no, and that distinction matters: review systems make agent work visible, but visibility and quality are different things. - **The Shift to Agentic AI: Evidence from Codex** — [Source]() — Published 2026-07-15 Active Codex users grew more than fivefold in H1 2026. Skills adoption hit 26.6% in three months, and over 10% of users ran three or more concurrent agents weekly, pointing toward structured, repeatable delegation patterns. What do skills signal? Users encoding repeatable workflows look a lot like people building review-shaped contracts for agent output, not just prompting ad hoc. How broad is multi-agent use really? The heaviest concurrent-agent figures skew toward OpenAI's own teams; external enterprise adoption remains thinner and less even. ### The Unreviewed Number - [The Number Arrives Looking Like an Answer]() — By [Sevda Polat]() · Published 2026-07-15 The [EntSQL benchmark](https://arxiv.org/abs/2606.03363) asked text-to-SQL systems to answer enterprise questions requiring domain knowledge: metric definitions, reporting conventions, organizational rules. The best evaluated English-input system reached 15.9% accuracy. Set that aside for a moment and consider what the other 84% looks like once it ships. ### Primary Sources - **Murphy-Hill, Butler, and Savelieva, 'Adoption and Impact of Command-Line AI Coding Agents,' arXiv, July 2026** — [Source]() — Published 2026-07-15 Large-scale rollout showing 24% more merged PRs among adopters, though merged PRs measure output volume, not delivered value. - **Johnston et al., 'The Shift to Agentic AI: Evidence from Codex,' arXiv, June 2026** — [Source]() — Published 2026-07-15 Fivefold active-user growth and multi-agent concurrency suggest coding's review infrastructure is what lets agent work scale. - **Gupta et al., 'Building Customer Support AI Agents at 100M-User Scale,' KDD 2026** — [Source]() — Published 2026-07-15 Nubank's five production deployments show satisfaction and self-service gains where escalation paths and case structure already exist. - **Wang et al., 'Agentic AI and Human-in-the-Loop Interventions,' arXiv, May 2026** — [Source]() — Published 2026-07-15 Taobao field experiment where shorter chats but worse ratings illustrate containment metrics improving while case quality declines. - **Liao et al., 'EntSQL,' arXiv, revised July 2026** — [Source]() — Published 2026-07-15 Best system reached 15.9% accuracy on enterprise text-to-SQL, exposing the gap when agent output lacks review infrastructure. - **Apostolou, Bosch, and Holmström Olsson, 'Agentic AI in Industry,' arXiv, May 2026** — [Source]() — Published 2026-07-15 Qualitative study across 12 companies finding a capability-deployment gap where absent output verification blocked production use. ### Past Articles - [The Middle Case]() — By [Rina Takahashi]() · Published 2026-07-08 · Format: The Middle Case Visa's new agentic commerce rules hold cardholders responsible for agent-initiated payments "as if the Cardholder initiated the Transaction." The procedural furniture is all in place: identity verification, consent, token provisioning. But Visa's public dispute categories still don't include an agent-specific reason code. If you want to contest something an agent did on your behalf, the challenge has to fit into language that predates the thing it's describing. Payments are where this surfaces first, because the challenge machinery there is most mature. The same gap, though, shows up wherever agents act on behalf of people. - [The Way They Move]() — By [Nora Kaplan]() · Published 2026-07-02 · Format: Digital Body Language Researchers at UC Davis watched seven commercial browsing agents navigate an instrumented website this spring. A behavioral classifier distinguished all seven from humans with near-perfect accuracy. Cloudflare's bot detection, running simultaneously, caught one. The gap between those numbers reveals a recognition surface that traditional defenses weren't built to read: how an agent types, scrolls, and moves a cursor across a page. If that behavioral layer is as legible as the data suggests, it could become the foundation for reputation, differential treatment, and accountability across the open web. - [The Furniture Is Arriving Before the House Is Built]() — By [Rina Takahashi]() · Published 2026-06-25 · Format: The Furniture Arrives Across the agent ecosystem, multiple players are simultaneously shipping the same category of development: admin consoles, spend controls, identity federation, observability conventions. Institutional furniture that normally arrives after a technology category has settled. But with 88% of organizations using AI regularly and only 23% scaling agents anywhere, the furniture is showing up in the gap between experimentation and production. That timing suggests something specific about where this market actually sits, and what's quietly becoming the real bottleneck. - [What Governance Governs]() — By [Nora Kaplan]() · Published 2026-06-18 · Format: Governance Gap Companies with governance tooling deploy twelve times more AI projects to production. Only 4 of 13 frontier-autonomy agents disclose safety evaluations for agentic deployment. The first figure tells you whether a system has been authorized to run. The second tells you whether anyone has rigorously checked what it does once running. They share a vocabulary. They measure fundamentally different things. And the infrastructure accumulating around the first may be quietly relieving pressure to build the second. ## Other sections in Issue 38 - [Daily Brief]() - [Foundations]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()