... What does prod surface? The edge cases. Rate limits, flaky webhooks, card declines mid-flow, double-charges on retry. The stuff that only shows up when real money or real users are involved. What we're building toward: connect FetchSandbox MCP, prompt "make this app survive in prod," and the runtime reads your app config, infers the invariants that matter, probes against failure scenarios, then returns a public receipt with the full trace. Agent finds the bug, proposes ... ... Genuinely curious how you're handling this today. Is there a verification step most are running, or is it mostly ship and find out? Comment from Raj Nagulapalle(@rnagulapalle): @rabnoor_s  100% agree on the business call vs

... This comes up constantly with teams building on Lovable, Bolt, Base44. The AI writes the webhook handler, it looks solid, gets shipped. Then prod explodes and nobody can reproduce it because the local environment is too clean. We built FetchSandbox to inject exactly this kind of chaos against a stateful Paddle twin. Out-of-order delivery, retry storms, concurrent events hitting the same subscription. Two race conditions caught before they hit customers in the first week. Curious what others ...

... expected. Otherwise you're comparing two runs that started differently and calling it a diff. We also needed the services to behave like prod, 429s, auth failures, delayed webhooks, duplicate deliveries, without real prod keys. That's what FetchSandbox gives us: service twins that surface the failure modes the happy path never hits. Is anyone actually testing these flows end to end, or is it mostly per-service mocks and hope? Comment from Nivy(@niveditha_patluri1): ours is publishing ... ... your own claim table and run two isn't run one, it's run one with a poisoned skip. Duplicate web hook delivery is the twin behavior that found us the most real bugs, so that part of FetchSandbox

... version-range scoping. All still open. What launches tonight : @grace_lee26 called it "memory of breakage," which was better than anything I'd written. @cancelkithq said the reproduce-fix-rerun loop was the part they were doing by hand. FetchSandbox MCP plugs into Cursor or Claude Code, reproduces the real failure on your own code, and once your agent fixes it, re-runs the check. You get a receipt. If you were in that thread, this roadmap came from ...

... still failed. So instead of shipping a test that said "fixed" when it wasn't, the agent tried again with a smaller, cleaner change and re-proved it. That one held. That's what I'm building FetchSandbox around: reproduce the real failure, apply the fix, then prove it holds on your actual code before you ship. For those shipping AI-written integrations, are you catching this stuff before prod, or mostly finding out when something quietly breaks? Comment from ...

... stops happening. The gap was we could only do that for bugs we'd scripted in advance. Anything unusual and the honest answer was "found it, fixed it, can't prove this one." What we built We taught FetchSandbox to write the reproduction itself, no pre-scripted test required. The safety check that makes it trustworthy A generated test could be wrong. It might pass broken code and hand you a fake green. So before we trust it, the test ... ... test that can't fail on broken code can't be trusted to pass on fixed code, so everything else hangs off it. Glad that's the part that landed. Comment from CHRISTIAN ONOCHIE(@christian_onochie): How does FetchSandbox

... that only imagined one clean event. Curious what broke for you A bug that sailed through review and CI but still blew up in prod, and what would have actually caught it? (This is the itch I'm building FetchSandbox around, running the failure before customers do.) Comment from Akbar B(@akbar_b): +1 to Arnold's unique-constraint-at-the-write-layer, that's the version that survives the race. One thing I'd add: the constraint only works ... ... schedule and alerting on any mismatch. Your own event store can't catch a bug in how it processes events, you need a second source of truth that didn't run through the same code. Curious whether FetchSandbox

... being straight): Pinned/frozen scenarios our fixtures are still mutable on our end, so an update from us can shift your result. No lockfile yet. Drift detection we don't yet warn you when the real API changes shape vs our model. Learning from your own past runs memory is curated per-API patterns, not your team's history. Deep coverage everywhere we import 60+ specs, but the deep failure library is real for Stripe/Paddle + a handful, thin beyond that. Auto ... ... davis23): hey Raj launch day finally. Comber went live on Product Hunt this morning (and Show HN): point it at a URL and it explores the app like a real user, catches the broken click, hands you the repro. FetchSandbox

... since the last launch, the goal was one thing: make FetchSandbox something you can actually gate a release on. not "looks tested" but provably tested. what changed: bulletproofed 5 integrations end to end: Stripe, Clerk, Descope, Resend, AgentMail. tested against how these APIs actually break in prod (webhook retries, out-of-order events, fresh-resource races), not made-up failures. Paddle got the deepest treatment:v we now throw webhook events at your billing handler out of order, duplicated ...

... keep seeing: agent finds a bug, fixes the code, declares done. what it does not do is rerun the exact failure scenario and prove the fix holds. that verification step was always on me. we just shipped something in FetchSandbox to close that loop. after it catches a bug, it now nudges the agent to rerun the same request and surface a behavioral comparison, before vs

... capping how many you shuffle or is there some heuristic for which subsets are worth permuting instead of brute forcing all n! Comment from Raj Nagulapalle(@rnagulapalle): @omri_ben_shoham1  found all three by running FetchSandbox against our own webhook handler before anyone else touched it. the stale event one specifically, you're right that it's the scariest category. a support ticket tells you something broke. free access silently granted never generates a ticket, it just leaks revenue ... ... class of bug stops coming back. the ordering is a symptom; the real problem is handlers that have an implicit belief about what "just happened" based on which event arrived. that's exactly the scenario the permutation fuzzer in FetchSandbox

... goal: if you want raw eyeballs go Tue-Thu, but for a badge/ranking with a modest following a weekend can punch above its weight. Comment from Sabber Ahamed(@sabber_ahamed): @busmark_w_nika   @abdullah_javaid3  the invitation vs favor framing is the most useful line in this whole thread. i caught myself drafting DMs that were basically upvote asks in a nicer outfit. what actually worked was showing up in threads like this one for weeks with nothing ... ... most important thing is to launch as soon as you can and keep iterating to improve, and keep launching Especially with how fast everything is moving with AI, waiting for a perfect time to launch will just let competitors

... launch yesterday (july 12th) we told you all about @FetchSandbox . today i'd rather hear about you. first, thank you. for the upvotes, but honestly more for the questions/comments n the conversations about idempotency, out-of-order webhooks, deterministic replay, and what it actually takes to gate a merge were sharper than anything i'd written for myself. a bunch of you basically handed me my roadmap. I built this because.. i kept watching ai agents write stripe ... ... back to you: what are you wiring up right now, and can this help you ship it without the launch-week surprise? if you're building solo , prompting your way through an app in cursor or claude code: connect fetchsandbox

... just posting and hoping. Personal goal is boring but real - protect at least one fully offline evening a week, no laptop in the room. Comment from Raj Nagulapalle(@rnagulapalle): love this idea. my q3 is pretty focused: launch FetchSandbox on Product Hunt (been building it for 3 months, feels like now or never), get to 5k monthly visitors from ~1k, and actually talk to 20 real users instead of just watching the analytics. personal side is simpler, just stay ... ... nika  honestly the PH launch is the main bet. if that goes well it should move the needle significantly on its own. beyond that, planning to write a few posts in dev/AI communities about the actual problem FetchSandbox

... report here Comment from Raj Nagulapalle(@rnagulapalle): for agentic coding tasks the cost question gets way sharper because you're not running one pass, you're running 10-20 to verify the output actually works. we hit this building FetchSandbox - frontier models for the hard reasoning step, cheaper open-weight for the verification loops. the $0.07 MiniMax number is really interesting at that scale. curious if anyone's tested MiniMax on async/webhook behavior specifically, that's where most agent pipelines ... ... locally (llama.cpp sidecar) and Groq's openai/gpt-oss-120b on the cloud side ... both open-weight. Once we stop trying to pick "the best model" and just treat them as different tools wired into a router, the "open-weight vs