HN

Comments (53)

• Menu

  JulianPaul
  Why is this better than running Opus 5.5 directly against my app with a custom Playwright-based harness for in my own subscription?
• Menu

  podoman
  > Mo is a custom agent harness for catching bugs that builds on the past 3 years of Momentic and millions of test traces from complex, real-world applications. Mo is built for recall: it finds the most real bugs, though Codex is a bit more precise at 86% vs 84%. The tradeoff is cost: Mo costs $2.67 per bug vs $0.80 for Codex, less than Claude Code and Devin.is this good? so Mo costs more money per bug? I'm confused.
• Menu

  staindk
  Congrats on the launch!Some questions are top of mind after having done POCs and trials with other companies that have products in this space (excuse me if they are answered somewhere obvious - I skimmed the site and your post before drafting this):1. What is vendor lock-in like with Momentic? In my mind there's space for a mature QA platform that agentically generates and maintains playwright/similar tests, but perhaps I'm wrong.1.b. will Momentic code or testing standard or some aspect be open enough that it is feasible to move away from it if needed, or continue using it if Momentic goes under/deploys major breaking changes?2. How deterministic are Momentic tests?3. Who is your target user? Product owner / developer / SDET / ?----Also - is this saying Codex is better and cheaper than Mo?"... though Codex is a bit more precise at 86% vs 84%. The tradeoff is cost: Mo costs $2.67 per bug vs $0.80 for Codex, less than Claude Code and Devin."
• Menu

  bortimus
  So, what's the moat?
• Menu

  brahyam
  tried testing it with my ios app but got: "The selected XXX build (com.XX.XX) cannot be installed because it is incompatible with the hosted iOS simulator. No XXX behavior could be tested."would be great to have more details about whats not compatible, I assume iOS version? app requires 27
• Menu

  aliasxneo
  So is this yet another SaaS product that's going to attempt to charge me for token usage? Sorry to sound negative, but nowadays it's an instant turn off because it's like the current subscription crisis on steroids. BYOA should be a default.To be more constructive: let's say I have 2 frontier subscriptions and I end up with 20% left on each at the end of the week. It feels awful knowing that I would _love_ to use that with Momentic but I can't because I have to pay for yet another set of proprietary non-transferable tokens. It's like dealing with airline rewards.
• Menu

  sailorganymede
  In my company, we already have agents messing around on our internal systems interacting via Playwright to try break things
• Menu

  schainks
  What does this do that UAT doesn't do? Sounds like you're combining UAT with gloves-on red teaming and I guess property testing APIs.
• Menu

  lejohnq
  congrats on the launch, agentic testing makes a lot of sense.how does this fit in to fixing the bugs? how do we close the loop with the agents we have coding?
• Menu

  adwn
  The last 3 years saw tons of "custom agent harnesses" come up, only for them to be superseded by the next generation of frontier models, which could do the same (and more) in their generic harness. So, what will you sell when Opus 6.0 swallows Mo's edge in 5 months from now? And probably cheaper, when using a Claude subscription instead of paying API prices.
• Menu

  adwad
  Are you open to listing other agents on the benchmark? I’m building my own and would like to run it on the full suite, but want to check before putting in the effort.
• anon
  undefined
• jon128
  Keep developing apps in Javascript and Typescript instead of bug-unfriendly ReScript. https://rescript-lang.org/
• vancekai
  [dead]
• georgestones
  [dead]