logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·30.10.26
← Back to news

One month coding with GLM 5.3 Flash

Original article
wagtail.org|210 points|165 comments|by ThibWeb|Oct 2, 2026

One Month Coding with GLM 5.3 Flash

By Thibaud Colas | Wagtail Core Team | Published: 2 Oct 2026

"Setting a challenge to spend the whole of September on only one efficient open model felt like a great idea at the time."

In a nutshell: 2 billion tokens later, the mission was a total success 🤖 task failed successfully.


📊 The Token Distribution

To track AI consumption, we utilized AgentsView, a tool recommended for agentic engineering. The primary objective was to rely exclusively on GLM 5.3 Flash (represented in teal in the data).

Screenshot of AgentsView tokens usage for September 2026 over 2B tokens

The Breakdown

  • The Win: For the first two weeks, I stuck strictly to the plan.
  • The Cost: Usage for the target model remained highly efficient:
    • Spend: $68
    • Energy: ≈4kWh\approx 4\text{kWh}≈4kWh
    • Carbon Footprint: ≈365g CO2\approx 365\text{g } \text{CO}_2≈365g CO2​
  • The Slip: In the latter half of the month, approximately 1 billion tokens leaked into other models.

Tree map of agents token usage over September 2026, with half going to GLM 5.3 Flash


⚠️ Unexpected Hurdles

1. The Price of "Vibe Coding"

We've been open about the fact that our experimental Wagtail MCP server is a vibe-coded prototype. While "vibe coding" isn't our standard for production, it's perfect for rapid prototyping.

However, I selected the wrong model for this specific task, leading to a massive spike in resource consumption almost overnight:

  • Tokens: 450M
  • Cost: $150
  • Energy: 5kWh5\text{kWh}5kWh

While the MCP server is now a functional and impressive demo, it serves as a stark warning: be cautious with agentic patterns and model selection. We likely could have reached the same result for 15\frac{1}{5}51​ of the cost with minimal extra effort.

2. Infrastructure & Availability

We have previously discussed the nuances of comparing inference providers. While our chosen providers are usually reliable, they lack the massive GPU hoarding capacity of the "big labs."

We noticed a performance dip in GLM 5.3 Flash, likely because it sits so high on the Pareto Frontier of efficiency and utility for our specific needs.

Efficiency=Agentic IndexCost per Task\text{Efficiency} = \frac{\text{Agentic Index}}{\text{Cost per Task}}Efficiency=Cost per TaskAgentic Index​

Scatter plot with Pareto frontier of models agentic index cost per task. Agentic index compared with cost per task

Note: The data above is filtered for open models available in European data centers.

Because of these capacity issues, I had to pivot to alternatives like DeepSeek V4.1 Flash and Qwen 3.8 Flash.

3. The R&D Tax

Beyond daily engineering, it is vital to keep a pulse on the industry. We are currently benchmarking model performance on Wagtail-specific tasks, which requires a diverse dataset across many models.

This data helps us steer users toward leaner options and informs the development of our new CLI prototype, designed specifically for agent compatibility.

Sneak peek at our benchmark data:

ModelAccuracy (%)Energy (Wh)Cost ($)
DeepSeek V4.1 Flash95%14.90.09
............

Data table of 14 AI models reporting their accuracy as a percentage, energy use in Wh, Cost in $


✅ What Actually Worked

Despite the "failure," I intend to continue this approach for ≈50%\approx 50\%≈50% of my daily production work (excluding R&D). GLM 5.3 Flash is exceptionally well-suited for this because:

  1. Massive Context: A 1M token window makes extended coding tasks feasible.
  2. Multimodal: Vision support allows for building from screenshots or visual QA.
  3. Competitive: Availability across multiple providers keeps costs down.

🚀 Takeaways & October Roadmap

Technically, the challenge failed, but the lessons learned are invaluable. For October, the strategy is as follows:

  • Implement local monitoring: Track not just tokens, but energy+spend→outcomes\text{energy} + \text{spend} \rightarrow \text{outcomes}energy+spend→outcomes.
  • Strategic Prototyping: Be more intentional about which prototypes get built and how.
  • Explore Efficiency: Investigate Jev-style decision diffusion models and latest flagship efficiency gains.

Final Thought

For the average developer, focusing on one or two "flash-tier" models is entirely viable. The goal should be to ensure the bulk of AI inference is handled by efficient models, measuring success by energy and cost rather than arbitrary token counts.

Want to hear the results? Come visit us at Wagtail Space 2026 this November!

Thibaud Colas


Related Reading:

  • Open models only: back to school challenge (3 Sep 2026)
  • Agentic engineering recommendations (Our guiding principles for LLM-assisted software engineering)
# Example of a lean agent call
def call_efficient_model(prompt):
    model = "glm-5.3-flash"
    return ai_provider.generate(model=model, prompt=prompt)