☰
Grok BotCoding & Dev2026-10-14

Have Grok Bot create a test inbox and walk your signup flow while you are away

Grok Bot chat claiming a test inbox and reporting a verification-code bug

@tranvu129's product-design bot claimed a private inbox ([email protected]), signed up a test account on pho.chat, walked onboarding and payment up to billing, found that the site sent three verification codes in 15 seconds so the first two looked wrong, rechecked, and emailed @tranvu129 a bug report they approved from their phone. Screenshot of the run is in the post.

Try it yourself

What you get

A disposable inbox, a signup walkthrough, and a bug report you approve before any fix lands.

Tools

  • Grok Bot
  • Staging URL
  • Throwaway inbox the bot can claim

Time / cost: Author: full onboarding walk while they were away from the desk

Steps

  1. List the flows and the hard stops (no real card, no production keys).
  2. Let the bot claim a test inbox for codes.
  3. Require a second pass on any failure before the bug report.
  4. Approve fixes yourself from the report.

Copy-ready prompt

While I am away, create a throwaway inbox, sign up a test account on [STAGING URL], walk onboarding and settings, and stop before any real payment or API key. Recheck failures, then email me a short bug report. Do not merge or deploy until I approve.

Prompt written by AgentPlays, based on @tranvu129’s post. Check the output yourself and approve before anything is sent or bought.

Watch out: Only against staging. Ban real cards and production credentials. Approve every outbound message.

Proof / source

Self-reported Author's public X post with chat screenshot of ClaimEmailInbox and the verification-code bug (Oct 14, 2026). Self-reported.

In their words

today my product design bot just made its own inbox, signed up a test account on pho.chat and walked through the whole onboarding on its own. it found the bugs, checked them again, and sent me a report. i was out working, read it on my phone and approved the fixes.

— @tranvu129 on X

Read the original source ↗

Added · Source link last checked · How we verify · Report an error

Related