Real head-to-head · same prompt, one shot

GLM-5.2 vs Kilo Code

The never-forgets agent — 1M context, open weights. vs Fable 5-class intelligence at ~59% less. The split-the-cost play.

GLM-5.2 · context1M tokens
Kilo Code · contextVaries (Kilo dispatches across models)
GLM-5.2 · priceOpen weights · free for individuals
Kilo Code · price~59% less than Fable 5 solo
GLM-5.2 · vendorZhipu / Z.ai
Kilo Code · vendorKilo

What I tested — same prompt, two models

I run the same fixed prompt set through every new model the day it drops — same string, one shot, single HTML file out — and I score the result 0–10 on whether it ran, how close it hit the brief, and how good it looked. Below is what came out when I gave the exact same prompts to GLM-5.2 and Kilo Code, side by side, on 0 shared tasks inside the Agent Operating System.

Both models were given identical prompts inside the Agent Operating System — no help, no iteration, no "best of N" tricks. I run each prompt once, save the HTML file the model produces, and score it 0–10 on whether it ran, how close it hit the brief, and how good it looked. The scoring is mine. The verdicts below are pulled from my source comparison guides at agentos.guide where I publish every score and the reasoning behind it.

GLM-5.2 · Default model inside Agent OS for any task that touches a long context — codebase Q&A, multi-file refactors, agent memory replay.

Kilo Code · Used inside Agent OS as a routing layer: Fable 5 generates the plan, cheaper models execute. Bench scoring pending a head-to-head comparison.

Side-by-side on 21 shared tasks

Click any cell to play that model's actual one-shot attempt. Medals are derived from my 0–10 scores per task (highest = 🥇, second = 🥈, third = 🥉).

Task ↓
GLM-5.2
Kilo Code
Game
🥈GLM-5.2 on Arcade
— not attempted —
Game
GLM-5.2 on Dogfight
— not attempted —
Game
🥉GLM-5.2 on Doom
— not attempted —
Game
🥇GLM-5.2 on Neoncity
— not attempted —
Game
🥇GLM-5.2 on Outrun
— not attempted —
Game
GLM-5.2 on Pool
— not attempted —
Game
GLM-5.2 on Racing
— not attempted —
Game
🥉GLM-5.2 on Raycaster
— not attempted —
Game
GLM-5.2 on Rpg
— not attempted —
Page
🥇GLM-5.2 on Landing
— not attempted —
Sim
🥈GLM-5.2 on Blackhole
— not attempted —
Sim
— not attempted —
Sim
🥇GLM-5.2 on Fluid
— not attempted —
Sim
🥉GLM-5.2 on Fractal
— not attempted —
Sim
🥈GLM-5.2 on Galaxy
— not attempted —
Sim
🥉GLM-5.2 on Orbit
— not attempted —
— not attempted —
— not attempted —
Sim
🥇GLM-5.2 on Solar
— not attempted —
Visual
GLM-5.2 on Terrain
— not attempted —
Visual
🥇GLM-5.2 on Voxel
— not attempted —

Strengths & weaknesses I logged

GLM-5.2

Strengths

  • 1M-token context window — best-in-class long-document and large-codebase work
  • Open weights — runs locally, no vendor lock-in, no token meter
  • Top of the bench for cinematic visuals (neon city, synthwave, voxel runner)

Trade-offs

  • Faceplanted on the Goldie Bench raycaster — the engine was great but it spawned the player inside a wall
  • First-shot reliability lags Opus by a hair on consistency

Kilo Code

Strengths

  • Kilo's own rubric: Fable 5 plan = 9.1/10, GPT-5.5 plan = 8.3/10 — Kilo isolates where the intelligence actually lives
  • Plan quality stays high while execution cost drops
  • Drop-in for Agent OS — Kilo Split framework already wired

Trade-offs

  • Adds routing complexity — two model providers in one workflow
  • No per-task goldiebench head-to-heads yet

Pricing & context — the spec sheet

Spec GLM-5.2 Kilo Code
VendorZhipu / Z.aiKilo
Context window1,000,000 tokensVaries — Kilo splits planning from execution across multiple models
PriceOpen weights · free for individuals~59% less than Fable 5 solo
Pricing detailOpen-weights release: weights downloadable from Hugging Face for self-hosting, or runnable for free on z.ai for individuals (commercial use has separate licensing).Kilo Code is a routing layer that splits planning (heavy model) from execution (cheaper model) so you get Fable-5-class plans driving GPT-5.5-class builds. Total spend lands at ~59% less than running Fable 5 end-to-end.
Release2026-06-142026-06-16
Bench coverage13/21 scored · avg 8.23/100/0 scored · avg —

The verdict — which should you pick?

Not enough scored shared tasks yet for a head-to-head average. The live demos for both are on the matrix above — play them and form your own opinion.

If you only run one of these inside your stack, the head-to-head average above is the call. If you can run both, my honest play is to wire GLM-5.2 and Kilo Code both into the Agent Operating System and dispatch each from the kanban by task type — long-context agent loops — pasting a whole codebase into one prompt → GLM-5.2, cost-conscious operators who run high-volume agent loops → Kilo Code. That's the same setup I run for the 3,600+ founders inside the AI Profit Boardroom.

FAQ — GLM-5.2 vs Kilo Code

Which is better, GLM-5.2 or Kilo Code?

On Goldie Bench, GLM-5.2 averages no scored verdicts yet across the shared tasks, with 6 gold, 3 silver, 4 bronze overall. Kilo Code averages no scored verdicts yet, with 0 gold, 0 silver, 0 bronze. Not enough scored shared tasks yet to call a winner.

How much does GLM-5.2 cost vs Kilo Code?

GLM-5.2: Open-weights release: weights downloadable from Hugging Face for self-hosting, or runnable for free on z.ai for individuals (commercial use has separate licensing). Kilo Code: Kilo Code is a routing layer that splits planning (heavy model) from execution (cheaper model) so you get Fable-5-class plans driving GPT-5.5-class builds. Total spend lands at ~59% less than running Fable 5 end-to-end.

What's the context window for GLM-5.2 vs Kilo Code?

GLM-5.2 has a 1,000,000 tokens context window. Kilo Code has a Varies — Kilo splits planning from execution across multiple models context window.

When should I pick GLM-5.2 over Kilo Code?

Pick GLM-5.2 for: Long-context agent loops — pasting a whole codebase into one prompt; Cinematic visual builds — landing pages, voxel scenes, synthwave runners; Anyone who needs to run a frontier coder locally for $0. The trade-off is the weaknesses we logged on the bench: Faceplanted on the {{SITE_NAME}} raycaster — the engine was great but it spawned the player inside a wall; First-shot reliability lags Opus by a hair on consistency.

When should I pick Kilo Code over GLM-5.2?

Pick Kilo Code for: Cost-conscious operators who run high-volume agent loops; Multi-step workflows where the plan is the expensive part; Teams already paying for Fable 5 who want to keep the plan but drop the execution bill. The trade-off is the weaknesses we logged on the bench: Adds routing complexity — two model providers in one workflow; No per-task goldiebench head-to-heads yet.

How does Goldie Bench score GLM-5.2 vs Kilo Code?

Every demo on this page was built by Julian Goldie inside the Agent Operating System — same fixed prompt for both models, one shot, single HTML file out. Each result gets a 0–10 score on whether it ran, how close it hit the brief, and how good it looked. The highest score on each task gets gold; second gets silver; third gets bronze. See methodology for full provenance.

The same stack Julian uses

Run this stack yourself.

Every demo on this bench was built inside the Agent Operating System — one prompt, one shot, single HTML file out. The Agent OS, the prompts, the templates, the weekly walkthroughs and 3,600+ founders shipping with it every day all live inside the AI Profit Boardroom.

3,600+founders
258documented wins
38countries
$100k+/mocommunity MRR