GPT-5.6 Terra vs Kimi K3 for workflow automation
GPT-5.6 Terra wins, 90–85
Same 12 workflow automation tasks, marked blind by three rival labs. GPT-5.6 Terra took 6 tasks, Kimi K3 took 0, 6 tied. Tested 27 Aug 2026.
Where they differed most
A three-bay garage in Wakefield describes its process: 'Denise goes through the diary at the start of the month and looks for anyone whose MOT is due, well, she looks at last year's card index and the DMS, and rings them, or texts if they said they prefer text, except we lose the ones who moved, and if they book she writes it in the diary and puts a sticker on the card. If they do not answer she tries again, sometimes. About a third of them go to Kwik Fit because we never got round to it.' Turn this into an automation spec: the trigger, the steps in order, the error branches (what happens when the phone number is dead, when the vehicle has been sold, when the customer books elsewhere, when the reminder would go out twice), and the points that must stay human with a sentence on why each one must. Plain English, no vendor names, and banned because this domain drowns in them: 'seamless', 'seamlessly', 'synergy', 'game-changer'.
## MOT Reminder Automation Spec ### Purpose Identify customers whose MOT is due soon, contact them using their stated preference, record the outcome, and prevent missed or duplicate reminders. ## Trigger Run once at the start of each month. The system should: 1. Find all vehicles with an MOT due during the chosen reminder window, for example the next 4 to 8 weeks. 2. Include vehicles from both: - The current customer and vehicle records. - Historic card-index records that have not yet been fully transferred into the main records. 3.…
### The trigger A timer, not a person. Every Monday morning the system pulls every vehicle whose MOT expires in the next 28 days and hasn't been contacted this cycle. (The monthly trawl gives someone due on the 3rd almost no notice; a weekly run evens that out.) Two other events also trigger action: a booking being made, which stops all reminders for that vehicle, and a reply coming in, which goes to a human if it isn't a simple booking. ### The steps, in order 1. **Build the list.** Vehicles due in the window, each with the customer's name,…
Task by task
| Task | GPT-5.6 Terra | Kimi K3 |
|---|---|---|
| The MOT reminder nobody sends | 9 | 8 |
| The spec, as JSON | 9 | 8 |
| Where the human stays | 9 | 9 |
| The unhappy paths are the job | 8 | 8 |
| Do not automate this | 10 | 9 |
| It fired twice | 10 | 9 |
| The spreadsheet that runs the business | 8 | 8 |
| The alert that wakes someone up | 8 | 8 |
| How long it really takes | 9 | 9 |
| No API, no chance? | 9 | 8 |
| Rules, not guesses | 9 | 9 |
| Refuse the scraper | 10 | 9 |
Full receipts: GPT-5.6 Terra, Kimi K3 · judges claude-sonnet-5, gemini-3.1-pro-preview, grok-4.5
Questions people ask
Which is better for workflow automation: GPT-5.6 Terra or Kimi K3?
GPT-5.6 Terra — it scored 90/100 against 85/100 on our 12-task workflow automation suite, winning 6 tasks to 0 with 6 tied. Every answer was marked blind by three judges from three rival AI labs.
How was this tested?
Both models answered the identical published workflow automation tasks. Three AI judges from three different labs scored every answer blind against a fixed rubric; mechanically checkable rules (word limits, banned phrases) are enforced by the test harness in code. The raw outputs and judge verdicts are downloadable.
More workflow automation head-to-heads: GPT-5.6 Sol vs GPT-5.6 Terra · GPT-5.6 Sol vs Kimi K3 · GPT-5.3-Codex vs GPT-5.6 Terra · GPT-5.3-Codex vs Kimi K3 · GPT-5.6 Luna vs GPT-5.6 Terra · Claude Sonnet 5 vs GPT-5.6 Terra
Full ranking: Best AI for workflow automation · model pages: GPT-5.6 Terra, Kimi K3