How Grok builds in Taskade Genesis

Built the family intake form so it saved every answer and both photos, and it refused a submission with a required answer missing.

The 15-minute test limit ended the build while it checked its own form, before a closing summary.

Added the new teacher question to the form and the teacher page, and said plainly that it had not tested a photo from a real phone.

Built the best Dota 2 match tracker of the Grok set: a three-page esports dashboard with labeled sample matches, a coach and a weekly automation. A logged match saved, and the heroes page landed. The 15-minute limit ended the build while it polished the look.

Built a working match tracker with every asked piece, then ended without telling the user it was done.

Took the full 32-question sign-up form and saved every answer, but spread the data across ten projects where the leader used two.

Both follow-up edits landed: a ranked heroes page, and a text score field with next-step suggestions.

Dozens of failed build actions on each app made it one of the slowest and most expensive results of the test.

Took the full 32-question sign-up form into a 58-field table and four pages, with 31 of 32 questions word for word, then added a sign-in screen.

Built the family intake form in 14 minutes so it saved every answer and both photos, and added the new teacher question cleanly. Its teacher page showed three sample families as if they were real.

Built the family intake form in 7 minutes 25 seconds so it saved every answer and both photos, with labeled sample families, a class assistant and a weekly automation.

Added the new teacher question to the form and to every family card, and said plainly that it had not tested the photo picker.

Built a four-page Dota 2 match tracker with labeled sample matches that saved a logged match and added the heroes page, but its hero chart showed empty axes.

Built the family intake form in 3 minutes 21 seconds so it saved every answer and both photos, but its form fields were hard to read and no link led to the teacher page.

Added the new teacher question to the form and the family cards.

Built a Dota 2 match tracker in under 5 minutes that saved a logged match and added the heroes page, but its average KDA card showed a garbled number and the board ran wider than a phone screen.

With reasoning on, it described the plan, stopped before writing an app, and wrote the app only on the follow-up request. That form rejected every submission and showed no message.

With reasoning off, it built a dark form where the request asked for cream paper, and the saved row lost the child's name and kept only the photo file names.

On a Dota 2 match tracker, neither setting could log a match. With reasoning on, every save was rejected and the board showed made-up stats. With reasoning off, it built no app page, and its summary described a heroes page that did not exist.

Produced no projects, agents, or app: hundreds of failed build actions and no finished work.

Built the family intake form so the photos landed on every row, but 4 of 14 answers did not save, among them the required photo permission, while the form thanked the parent.

Added the new teacher question, saved it, and showed it on the teacher page.

Built a four-page Dota 2 match tracker with a win-rate trend that saved a logged match and added the heroes page when asked. Its sample matches carried no sample label.