---
title: "Discussion on \"What broke when an AI agent filled in 50 sign-up forms for us\" | Hashnode"
description: "Discussion on \"What broke when an AI agent filled in 50 sign-up forms for us\". Notes from filling in 50 directory sign-up forms with an AI agent: a 200 that meant failure, odd controls, and where it stopped on purpose."
url: "https://hashnode.com/posts/what-broke-when-an-ai-agent-filled-in-50-sign-up-forms-for-us/6ae542f999f8168a318e9e03"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [What broke when an AI agent filled in 50 sign-up forms for us](https://tukri.hashnode.dev/what-broke-when-an-ai-agent-filled-in-50-sign-up-forms-for-us?utm_source=hashnode&utm_medium=feed)

Notes from filling in 50 directory sign-up forms with an AI agent: a 200 that meant failure, odd controls, and where it stopped on purpose.

Oct 31 · 5 min read · tukri.hashnode.dev  
Read the article

-   [#automation](https://hashnode.com/tag/automation)
-   [#startup](https://hashnode.com/tag/startup)
-   [#bangladesh](https://hashnode.com/tag/bangladesh)
-   [#ai-agents](https://hashnode.com/tag/ai-agents)

## Written by

[Tukri](https://hashnode.com/@tukri)

@tukri · Dhaka, Bangladesh

  
[View profile](https://hashnode.com/@tukri)

Bangla POS, stock & dues book for small shops

## Responses 2

Markdown supported · ⌘↵ to post

[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.

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

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

G2 returning HTTP 200 with "Something went wrong" is the best single lesson in the post. Asserting on something only success can produce, a new URL or a record id, is the rule I would put at the top of any browser automation brief, because status codes describe the request and not the outcome.

The StartupBlink case is useful too. Checking the Public Suffix List before accepting the rejection, rather than assuming the form was right, is the kind of verification an agent should do and a hurried person often skips.

I also liked that the agent refused personal declarations like "I am 16 or older" unless you approved them by name. That is a sensible boundary for anything signed in your company's voice.

"Submitted is not live" deserves wider circulation. With 13 submissions sitting in review queues, do you plan to recheck each row on a schedule, or wait for the directories to email back?
