How GPT builds in Taskade Genesis

Built the family intake form three times. All three saved every answer and both photos, and parents could fill them in without an account, as the request asked.

In two of the three builds the teacher page listed every family with their photos. In the third it read the saved answers wrong and showed "No photos saved" for a complete entry.

Added the new teacher question in all three apps, saved it with each submission, and put the change live.

Every closing summary said what it had not tested and pointed out that the teacher page was open to anyone with the link.

Built a newer version of the family intake form in about 12 minutes: a four-step form, a teacher page and a printable summary page, with the closest fit to the requested look in its test. It did not save the date and time of each submission.

Built the most complete Dota 2 match tracker of its test in about 12 minutes, with four tabs, a date filter, and win rate, KDA and MMR tiles. Before the first match was logged, its win rate tile showed two black blocks.

Built a polished five-step client sign-up form with a review queue in about 18 minutes, but its automation only filled in fields, so staff had to score each applicant by hand.

Built a match tracker that saved a logged match and took any hero name, but its dashboard opened empty because the app hid every sample match. The build took about 18 minutes.

Built the Dota 2 match tracker in about 10 minutes with every detail the request named (hero, result, kills, deaths, assists, duration, notes, win rate and streaks), a coach agent and a weekly recap automation.

Added the heroes page and its menu link in about 8 minutes and put the change live. A logged match saved and showed in the app.

Reproduced all 32 questions of a real client sign-up form word for word. The only model to get all four of its builds word for word across more than one test.

The only model to build a working scoring grid: 33 rows by 5 ratings, with every score saved straight back into the workspace.

The best client sign-up form Luna has built: nothing stalled, and a human reviewer called it beautiful.

The only model to explain its own design choices, and both builds carried all 32 questions word for word.

Built an app in about 11 minutes and changed it in about 6.

Its match tracker crashed on the first real entry and its sign-up form rejected the first submission; later tests finished cleanly.

Built every app in a five-model test of identical prompts.

Same result after a large Taskade update, with fewer failed build steps.

Kept a build checklist inside both apps, so the finished work could be checked against the request.

Built the client sign-up form with four pages and a scoring automation that ran on its own.

Built the fleet-inspection app with both weekly automations live in 7 minutes 18 seconds.

Built the AI governance office in 6 minutes 38 seconds with all 24 named items in place.

Built a complete match tracker with a live dashboard and a weekly recap automation.

Passed all five follow-up-edit tests on its habit tracker.

Its recipe box rendered as a warm printed cookbook in light and dark, with every page loading cleanly.

Built a two-page match tracker in 8 minutes 19 seconds, the fastest complete build of its test, and a match saved from the app came back with all eight details in place.

Built the family intake form so it saved every answer and both photos, and added the new teacher question cleanly.

Its public class assistant told an anonymous visitor a child's name from a saved form.

Built the family intake form twice. One build saved every answer and both photos in under 5 minutes. In the other, every parent submission failed on the photo permission question, although its closing summary said the form had worked.

Built the Dota 2 match tracker twice in about 5 and a half minutes each. Both saved a logged match with every detail and added a ranked heroes page when asked.

Built the same Dota 2 match tracker five times. Every build saved a logged match with every detail and showed it on the dashboard. Three were complete. One counted every win as the current streak, and one was a single page that offered six heroes and no match history.

Built the reading list five times, four of them in about 4 minutes. Every build saved a book added from the app with its author and status, and each status filter showed the right book. One build stopped after writing its plan until it was asked to go on.

Built the family intake form five times, in about 4 to 6 minutes each. Every build saved each answer and both photos, and the new teacher question saved and showed on the teacher page each time. Only one saved the date and time of each submission that the request asked for, and one teacher page showed raw answer codes.

Built the Dota 2 match tracker five more times, in about 5 minutes each. Every logged match saved and showed on the dashboard, and one build counted the current streak wrong.

The first model to pass all five checks in one run: built the app, took a submission, saved every answer in the right field, ran the automation, and answered questions about the data.

Fastest of the test: 8 minutes 26 seconds.

Both builds carried all 32 questions word for word, after three tests where none of the four came through. A change of setting turned it around.

Terra's premium setting delivered less than Luna on the client sign-up form: a single page rewritten 19 times.

Best all-round match tracker and best client sign-up build of the test: form to saved score worked on the first try.

The quality pick in a five-model test of identical prompts.

Fastest complete client sign-up build of the test at 5 minutes 6 seconds; it left the scoring automation out.

Finished a two-page sales pipeline with a daily call brief in 10 minutes 47 seconds.

Finished the governance office in under 6 minutes and the fleet inspection in under 5.

Passed all five follow-up-edit tests; its recipe box was a single page.

Built a clean match tracker in about 11 minutes, but its match form offered only four heroes from its own sample list, so a player could not log the hero they played.

Built the family intake form twice, about 4 minutes each, and both saved every answer and both photos. One opened in a dark look where the request asked for cream paper. The other asked first who could open the teacher page, then put it behind a teacher sign-in.

Built the Dota 2 match tracker twice in under 4 and a half minutes, and both added a ranked heroes page when asked. One build labeled its starter matches, and the other ran wider than a phone screen on every page.

Built the client sign-up form twice, in about 5 to 6 minutes each. Both had a staff page and an AI scoring automation that writes each applicant's score and outcome. One saved no scoring guide in the workspace for its assistant to read.

Built a newer version of the family intake form twice, in under 7 minutes each: a three-step phone form with photo upload and a teacher page. Neither drew the colored-pencil doodles the request asked for, and one put a teacher sign-in link in the parents' header.

Built a Dota 2 match tracker twice from a two-word request, in under 7 minutes each. One showed live stats, a match form and a heroes page in a plain design. The other had the most polished design of its test, but its four stat tiles showed a dash while its match history held five matches.

Added a sign-in screen the brief never asked for, and did not say so.

Added the same unasked-for sign-in screen again. Repeatable enough that it shaped how we score a build that answers a different brief than the one given.

Added a sign-in gate to the match tracker again, the third time in three tests.

Put an unasked sign-in screen in front of two of its three finished client sign-up builds, over complete data and three scoring runs.

Built a 34-field fleet-inspection form and left the Thursday reminder switched off.

Built the widest governance office of the test, with seven pages and every named item, behind a sign-in screen.

Built a two-page match tracker with no sign-in screen.

Passed all five follow-up-edit tests, but the habit tracker sat behind a sign-in screen it added itself.

Put a sign-in screen nobody asked for in front of a personal match tracker, and its summary did not mention that an account had to be created first.

Built the family intake form so it saved every answer and both photos, labeled its sample family, and said on the teacher page that it needs no sign-in. The new teacher question landed.

Built the Dota 2 match tracker with its sample matches labeled as a demo, saved a logged match with every detail, and put the new heroes page in both the desktop and the phone menu.