Practitioner's Corner
Practitioner's Corner
What a Click Carries
When a person clicks a button on a webpage, the infrastructure only sees the click. It never sees the reading, the context, the judgment, the acceptance of responsibility that preceded it. It never had to. The entire web assumed a human was present, so thoroughly that nobody wrote it down. Now agents produce identical HTTP requests without any of that invisible context. The sessions still fire. But the click has stopped carrying what every downstream system quietly depended on it to carry.
What a Click Carries
When a person clicks a button on a webpage, the infrastructure only sees the click. It never sees the reading, the context, the judgment, the acceptance of responsibility that preceded it. It never had to. The entire web assumed a human was present, so thoroughly that nobody wrote it down. Now agents produce identical HTTP requests without any of that invisible context. The sessions still fire. But the click has stopped carrying what every downstream system quietly depended on it to carry.
What WorkArena's Task Design Makes Visible
One benchmark task asks an agent to create a hardware asset in ServiceNow. The agent fills in fields, clicks submit, reaches a confirmation screen. WorkArena ignores the confirmation screen entirely. Its validator queries the database directly, checking whether saved values match the spec. An agent that navigated perfectly but corrupted data underneath would look like a success to anyone watching. That design choice, buried in validation code, surfaces a problem anyone deploying agents inside enterprise systems will eventually have to solve.
What WorkArena's Task Design Makes Visible
One benchmark task asks an agent to create a hardware asset in ServiceNow. The agent fills in fields, clicks submit, reaches a confirmation screen. WorkArena ignores the confirmation screen entirely. Its validator queries the database directly, checking whether saved values match the spec. An agent that navigated perfectly but corrupted data underneath would look like a success to anyone watching. That design choice, buried in validation code, surfaces a problem anyone deploying agents inside enterprise systems will eventually have to solve.
Show Me the Record — A Compliance Officer Confronts Her First Agent Workflow
CONTINUE READINGPayments Sidebar
An agent that fills out a form or monitors a price can operate in a gray area for a while. Nobody asks for its credentials. But the moment an agent tries to spend money on someone's behalf, a whole chain of participants needs to know it's there.
That's the logic behind Mastercard's Agent Pay, announced in April 2025: agents must be registered and verified before transacting, consumers define what an agent can purchase, and the payment network distinguishes agent-facilitated transactions from ordinary ones. On the deployment side, OpenAI's Instant Checkout launched in September 2025 with scoped payment tokens constrained by amount, merchant, and session.
These are early program signals, not evidence of routine adoption. But the trajectory tells you something about where ambiguity gets resolved first. Payment systems already handle authorization, fraud screening, and disputes. U.S. billing-error rules can require documentary evidence tying a charge to the person who authorized it. When an agent enters that flow, "it clicked buy" isn't sufficient. The system needs to know who delegated, under what constraints, and whether the result matched the intent.
Other web workflows can tolerate ambiguity for longer. Money has always been less patient.
Further Reading
Past Articles
Retry logic in distributed systems works because of a quiet contract: same input, same execution path. An idempotency ke...
To a person with a browser, a form field is a text box. To a machine trying to operate that same page, it's a hundred li...
An agent running on an 8K-context model that entered a loop used to crash. The window filled, the API errored, the run d...
Suchintan Singh describes Skyvern as building "APIs for websites that don't have APIs." It sounds like a pitch deck line...