--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/34/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/34/echoes" issue: 34 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Rina Takahashi","Nora Kaplan"] published: 2026-06-22 updated: 2026-06-19 articles: 14 --- # 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 34 — Echoes Past infrastructure decisions echoing in today's production realities ### The Testing Substrate - [The Thread That Runs Through the Browser]() — By [Rina Takahashi]() · Published 2026-06-19 · Format: The Testing Substrate In 2004, a developer at ThoughtWorks wrote a JavaScript tool to stop his colleagues from manually clicking through a billing app. He named it Selenium, as a joke. Twenty-two years later, AI agents open browsers using protocols descended from that tool, reading page structures originally built for screen readers, deciding what to do on sites they've never encountered. Every layer of browser automation was a reasonable response to the problem directly in front of it. The problem in front of it kept quietly changing. ### Before the Click - [Four Checks Before a Click]() — By [Rina Takahashi]() · Published 2026-06-19 Before an agent can decide what to click, something has to confirm the click will actually land. Playwright runs four [actionability checks](https://playwright.dev/docs/actionability) on every single click action. Visible. Stable. Receives events. Enabled. All four must pass simultaneously, or the action doesn't fire. ### The Familiar Breakage - [A QA Engineer Watches History Repeat Itself]() — Published 2026-06-19 *Patience Waite is not a real person, though anyone who spent years writing Selenium tests between 2009 and 2015 might feel uncomfortably certain she is. We found her — or assembled her — from the accumulated scar tissue of a generation of QA automation engineers who learned, one flaky test at a time, that the browser does not care about your deadlines. She now consults on reliability engineering. In the past year, three separate clients have asked her to evaluate whether their agent deployments are "production-ready." She agreed to this conversation on the condition that we not call her an "AI expert."* ### The Standard and the Cycle - [The W3C Moment]() — By [Rina Takahashi]() · Published 2026-06-19 · Format: The Standard and the Cycle In June 2018, the W3C published a spec describing software that "emulates the actions of a real person using the browser." They meant testing tools. That sentence now reads like a product description for AI agents. WebDriver's authors knew they were building something more general than a test harness. They just scoped it as one. The word "primarily" left room for everything that followed. - [The Screen Scraping Cycle]() — By [Rina Takahashi]() · Published 2026-06-19 · Format: The Standard and the Cycle In 1986, IBM shipped a tool that let programs read characters off a terminal screen because mainframe applications had no APIs. The assumption was that this was temporary. Forty years and several technology generations later, browser agents automate the web using the same basic logic: parsing whatever the human sees. Each generation believed it was building a workaround. Each time, the workaround became infrastructure. ### Further Reading - **A Brief History of the Selenium Testing Framework** — [Source]() — Published 2026-06-19 The 2004 ThoughtWorks tool that was never meant to become agent infrastructure. It became agent infrastructure. - **WebDriver is Now a W3C Recommendation** — [Source]() — Published 2026-06-19 In 2018, a protocol for "out-of-process programs emulating a real person" became a web standard. Seven years early. - **Agentic Browser Security: 2025 Year-End Review** — [Source]() — Published 2026-06-19 Test automation assumed a trusted operator at the keyboard. What happens when the operator is an LLM and the adversary knows it. - **Why AI Agents Keep Failing in Production** — [Source]() — Published 2026-06-19 Schema drift, fragile selectors, flaky execution. Selenium teams would recognize every failure pattern on this list. - **Build the Web for Agents, Not Agents for the Web** — [Source]() — Published 2026-06-19 A 2026 proposal asking the question that two decades of workarounds on test infrastructure have been deferring. ### Past Articles - [The Organizational Inheritance]() — By [Rina Takahashi]() · Published 2026-06-11 · Format: Two Kinds of Debt RPA's governance problems didn't arrive all at once. They accumulated quietly: orphaned bots running on departed employees' credentials, exception-handling logic that lived in one person's head, audit trails nobody maintained. The questions were always answerable. Who owns this? What happens when it fails? Organizations often didn't ask until something broke. AI agents face the same questions now. The teams deploying them are rarely the teams that lived through the answers. - [The Operational Inheritance]() — By [Rina Takahashi]() · Published 2026-06-11 · Format: Two Kinds of Debt Browser automation spent twenty years learning to distrust the gap between issuing a command and the command doing what was intended. Selenium engineers built workarounds. Playwright encoded them into architecture. Web agents now operate on the same substrate, facing the same race conditions, the same invisible overlays, the same intercepted clicks. They inherited all of it. The hard-won instinct to doubt when something reports success stayed behind with the community that earned it. - [The Confused Deputy Keeps Getting Promoted]() — By [Rina Takahashi]() · Published 2026-06-11 · Format: The Oldest Deputy In 1977, a Fortran compiler overwrote a billing file because a user asked it to. Nobody hacked anything. The compiler just couldn't tell its own authority apart from the user's request. Norm Hardy named this the "confused deputy" in 1988. The web recreated the pattern with session cookies. OAuth recreated it with delegated tokens. Each time, the fix worked: teach the deputy to distinguish instruction from data. Now LLM agents carry the same structural problem, and the proposed fix is four decades old. This time, the deputy may not be capable of learning. - [Consequences as Architecture]() — By [Nora Kaplan]() · Published 2026-06-03 · Format: Frames and Fixes If voluntary coordination almost never closes a severed feedback loop, what has? HTTPS adoption and GDPR enforcement are the clearest cases, and they share a specific shape: someone occupied a chokepoint, reduced the cost of compliance beforehand, and escalated consequences gradually rather than delivering them as a single absorbable event. Most broken feedback loops lack all three conditions. Most institutions would rather convene a working group. ## Other sections in Issue 34 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()