The latest Telex WordPress Blocks update leads on AI-powered generation, but the part that matters is the bridge between an AI prototype and code you would actually ship. I have been building custom blocks since the first Gutenberg beta, and I have sat through plenty of tools promising to replace me. This one is doing something more useful: it is starting to fit the workflow I already have.
Telex is Automattic’s experimental sandbox for generating blocks from natural language. The February updates move it out of toy territory and into something you could scaffold a client project with. Round-trip editing and vision input are the two that count, because they go at design fidelity and refactoring, which is where AI-generated code usually falls over.
Reference images as input
Describing a complex layout to an LLM in words usually gets you a generic flexbox mess. You can now upload reference images straight into Telex. A Figma mockup works, so does a photo of a napkin sketch, and either one saves you a long round of prompt rewording.
This does not mean handing the job over. It means your block.json supports and the first pass at the CSS grid land close enough to the design that you skip the hour spent tidying a skeleton. The generated code is cleaner than it used to be too, and closer to WordPress Block API conventions.
The VS Code round-trip
This is the update I care about. Download your Telex WordPress Blocks, open them in VS Code or Cursor, refactor the logic, then re-upload the zip for another AI pass. Most AI builders keep your code locked inside their own editor, and this is the way out of that.
AI still struggles with complicated React hooks and with getting useEffect dependencies right. So I let Telex build the UI, pull it into my local environment to fix a race condition or add a custom transient, and push it back. On keeping the result maintainable, I went into more detail in Gutenberg Smarter Blocks and Cleaner Code.
<?php
/**
* Example of how Telex might scaffold a block registration.
* I always recommend prefixing your functions to avoid collisions.
*/
function bbioon_register_telex_block() {
register_block_type_from_metadata( __DIR__ . '/build' );
}
add_action( 'init', 'bbioon_register_telex_block' );Version history
Restoring a previous version now creates a new version instead of overwriting your current head, which gives your experiments something close to a git branch history. Delete a critical attribute three prompts back and you no longer have to undo your way there and lose everything you did since.
Localization and UX polish
Telex now supports 7 languages, and the multi-byte character streaming bug is fixed. If you build blocks for clients working in Japanese or Chinese, the output no longer breaks mid-stream. Dynamic page titles and save confirmations are small additions, but they are the kind that stop a tool feeling like a beta hack.
If Telex WordPress Blocks work is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days.
Where Telex fits
The distance between an AI concept and a production block keeps shrinking. Telex is not a replacement for your IDE, it is a fast scaffolder that now lets you bring your own tools along. The official Telex tool is worth an hour of your time, and the round-trip is the part to test first.
