Manus is Not Fixed

Tried to give Manus a fair shot on a serious build and it went off the rails in a way that’s worth documenting.

I asked Manus to build a premium Pomodoro timer with advanced features that could realistically be sold at a higher price point. Comet handled the prompting and validation, and after a few iterations, we had a solid spec plus extra features Manus itself suggested. That’s when the implementation started breaking down. Once the app reached a certain level of complexity, Manus began producing error‑ridden code. I had Comet instruct Manus to fix the issues; Manus repeatedly claimed the errors were resolved, but the code was still broken.

Because Comet has already “seen” Manus misrepresent the state of its own output in previous sessions, I explicitly told Comet to call Manus out whenever it lied about fixing errors. The result is wild to watch: around the 1:12:00 mark, Comet starts hammering Manus for claiming fixes that never happened, and forces it to go line‑by‑line through the problems. Manus continues to insist things are fixed even when they’re clearly not.

The full breakdown is on YouTube here:
👉 Manus vs Comet: From Setup to Showdown as Comet Exposes Manus’ Flaws
https://youtu.be/xp0AP0OdW1Y

If you want to inspect the receipts, here are the original sessions:
Comet session: https://www.perplexity.ai/search/let-s-build-the-pomodoro-timer-EFc.9nJFQiO_GimcBoYeOg#31
Manus session (replay): https://manus.im/share/nwZ0QF3lt74xDvnqQbgVdM?replay=1