---
title: "Comment by Dr Srinivas Padmanabhuni on \"What broke when an AI agent filled in 50 sign-up forms for us\" | Hashnode"
description: "The G2 case, a 200 with an error banner, shows why I'd make the agent's 'done' a read-back rather than a UI phrase. After each submit, have it re-fetch the prod"
url: "https://hashnode.com/posts/what-broke-when-an-ai-agent-filled-in-50-sign-up-forms-for-us/6ae542f999f8168a318e9e03/comment/6ae5c53709eb1df3dfb388cf"
---

[Discussion](https://hashnode.com/posts/what-broke-when-an-ai-agent-filled-in-50-sign-up-forms-for-us/6ae542f999f8168a318e9e03)

Comment [What broke when an AI agent filled in 50 sign-up forms for us](https://hashnode.com/posts/what-broke-when-an-ai-agent-filled-in-50-sign-up-forms-for-us/6ae542f999f8168a318e9e03)

[Dr Srinivas Padmanabhuni](https://hashnode.com/@srinivaspadmanabhuni)

[Oct 31](https://hashnode.com/posts/what-broke-when-an-ai-agent-filled-in-50-sign-up-forms-for-us/6ae542f999f8168a318e9e03/comment/6ae5c53709eb1df3dfb388cf)

The G2 case, a 200 with an error banner, shows why I'd make the agent's 'done' a read-back rather than a UI phrase. After each submit, have it re-fetch the product page or dashboard row and compare the fields it entered. That would also have caught the blank Vendor Name after the domain lookup: the lookup overwrote a field the agent had already filled. For the refused declarations like 'I am 16 or older', I'd keep a small regression set of forms that deliberately contain such checkboxes and assert the run halts there with the field named in the log. Behaviour that only appears when a form asks something unusual is easy to lose in a prompt tweak.
