Announcement post published on the **official Z.ai blog** (formerly Zhipu AI, Chinese lab) on **August 14, 2026**, **with no individual byline**, ~2,000 words plus footnotes. It announces **GLM-5.3**, successor to GLM-5.2, opening with a methodological thesis: *« Scaling post-training is all we did for GLM-5.3. »* Same base model as GLM-5.2 — *« every gain comes from post-training »*. Three announcements. **(A) An open-weights coding model**: +50% claimed on **Z.ai Code Bench**, an unpublished in-house benchmark. **(B) A cyber capability presented as "emergent"**, which the body of the text traces to a training choice — *« As part of post-training, we introduced vulnerability discovery data and environments into the training mix. We expected this to make the model better at finding and reasoning about vulnerabilities »* — what came as a surprise was the speed and the change in nature: the model moves from identifying isolated flaws to *« coherent plans for complete exploitation chains »*. Gains grow with position in the exploitation chain: CyberGym 77.2 → **84.5%**, ExploitBench 24.4 → **54.4%** (×2.2), ExploitGym 29 → **105** tasks in 2h (×3.6), with the gap to the closed frontier remaining wide (181 and 247 tasks). Z.ai puts it this way: *« Capability is growing fastest exactly where we are furthest behind. »* The post also publishes a **Z.ai Security Disclosure Ledger**: **2,436 vulnerabilities identified across 269 open source projects** — kernels, OSes, browser engines, infrastructure, web applications, network protocols — the oldest introduced in **1981**, average lifetime before discovery **26.6 years**, of which **53 disclosed** and **2,383 under embargo**. **(C) A weight release** *« within two weeks of launch, once safety evaluation and hardening are complete »*. The most reusable methodological contribution: **environment and verifier synthesis**, the latter produced without access to the reference solution and admitted only after a triptych of negative controls — **oracle**, **no-op**, **unsolved-state**. All agentic evaluations are conducted **in Claude Code 2.1.207**.
#GLM-5.3#GLM-5.2#Z.ai
**Z.ai** (anciennement **Zhipu AI**) · laboratoire d'IA chinois · éditeur de la famille **GLM**. Billet **institutionnel et non signé** : aucun auteur nommé · aucun chercheur mis en avant · aucun lien vers un rapport technique ou une carte de modèle. Publié le **14 août 2026**. La page est une SPA React — le HTML servi est un `<div id="root">` vide · et le texte comme les scores ont dû être extraits du bundle `glm-5.3-BCnx8T5_.js` · où ils figurent en valeurs source.
Letter "Dear friends" from Andrew Ng in *The Batch* (DeepLearning.AI, issue 359) on **loop engineering** applied to **0-to-1** product development. Ng shares his **3 key loops** — agentic coding loop (~minutes), developer feedback loop (~hours), external feedback loop (~days) — nested by increasing time scale, connecting *coding agent → product spec/evals → developer vision → external feedback*. Central thesis: humans retain a **context advantage** (rather than a "taste") that makes human-in-the-loop indispensable; engineers take on a partial product management role. Domain: coding agents, product engineering, agentic methodology.
Sunday tinkering post by **Mark Dembo** (Head of Solutions, Developer Platform & AI at **Cloudflare**) published on **June 7, 2026** on his personal blog. **Narrative**: inspired by **Steve Ruiz**, the author buys a small **M5Stack Stick 3** device (~€30) and, taking advantage of the release of **Opus 4.8**, builds himself a **DIY AI agent** "out of pure curiosity, with no goal." **Iteration 1 (45 min)**: he throws the device's documentation at **Claude Code**, which generates Python scripts (~200 LOC, *"zero blast radius"*) displaying the weather in Munich, then several cities; a **Cloudflare Workers + Workers AI backend** adds **text-to-speech (TTS)**, **push-to-talk** (speech-to-text), and a central **small LLM** to answer questions. **Iteration 2 (a real agent)**: switching REST endpoints to **WebSocket** transport via the **Cloudflare Agents SDK** + **Dynamic Worker execution** → the ***"Code Mode"*** pattern (the agent writes and executes code to accomplish its task). The agent then answers public-data questions (11! = factorial, the Champions League winner via `fetch()` on Wikipedia, the weather in any city). **Iteration 3 (real powers)**: connecting to **Todoist** via an **MCP OAuth** flow → 50 tools at once, hence two problems: **context bloat** and **real damage risk**. The fix draws on Cloudflare's **MCP Server Portal** + Claude connector settings: per tool, **Always allow / Ask for approval / Disable** (*Disabled* tools never enter the context; an **LLM classifier** accepts only distinct "allow" grants and **defaults to deny**). **Stated posture**: reducing his role to ***"idea generator, executor and judge"*** (and rarely technical guide), a "human-in-the-loop" flow he considers not very *"2026"* (copy-pasting into UIFlow). **What he did NOT do**: no latency/streaming optimization, no optimistic LLM calls, no evals, ***"I did not even look at the code once."*** **Wonder**: €30 + one Anthropic session window + a few cents of Cloudflare inference → an object that listens and speaks, driven in natural language; *"the true unlock is how accessible it is."* Sharp contrast with [[thomas-pragdave-failing-faster-code-rot-ai-velocity-2026-06-06]] (here *"zero blast radius"* justifies never looking at the code); concretely illustrates *Code Mode* / *"the agent just writing and executing code,"* the **MCP** pattern ([[claude-skills-bigger-than-mcp-willison-2025-10-16]]), *Ask for approval*-style tool governance (uber-engineering-agent-identity-crisis-zero-trust-spire-2026-05-21), and the *systems around the model* doctrine from dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28.
#BYO agent#bring your own AI#tinkering
**Mark Dembo** (@darkmembo / @mdembo) · **Head of Solutions – Developer Platform & AI** chez **Cloudflare** (auparavant auteur sur le blog Cloudflare). Billet personnel publié sur son blog *markpauldembo.com* le **7 juin 2026** (description : *« Thoughts about tinkering on a Sunday »*).
Manifesto-style X thread by Rohit (@rohit4verse) laying out the *2026 AI engineer roadmap*: a $150k gap between prompt engineer and systems architect, the end of *generic wrappers* "sherlocked by big tech," and 5 portfolio projects ranked by complexity level (offline mobile SLM, self-improving coding agent, multimodal *Cursor for video editors*, privacy-first personal life OS agent, autonomous enterprise workflow agent). Each project describes its *key architectural decisions* (lazy loading, sliding window, sandboxing, scene detection, personal knowledge graph, event-driven multi-agent, audit trail, RBAC, observability). Structuring slogan: *"the replaceable: building wrappers / the unfireable: shipping autonomous systems"*. Injunctive, viral tone typical of X in 2026.
#2026 AI engineer roadmap#Rohit#rohit4verse
Rohit (@rohit4verse) — créateur de contenu IA sur X · vulgarisateur d'architecture et roadmaps de carrière en ingénierie IA.
IA générative strategic framework - 4 deployment quadrants - Access paradox - Data as moat - Strategic differentiation - Harvard Business Review - Bharat N. Anand - Andy Wu
#generative AI strategy#competitive advantage#four quadrants framework
Bharat N. Anand (NYU Stern School of Business Dean) · Andy Wu (Harvard Business School)