Telex is an experimental Automattic tool that generates Gutenberg blocks from natural-language prompts. A user can include a Figma mockup or screenshot, receive a working block, download the code, edit it in an IDE, and return to Telex for another AI-assisted iteration.
That output boundary is important. Many vibe-coding products stop at a disposable page. Telex produces a component that belongs to the WordPress editor and can be inspected before installation. Automattic's internal experiments describe designers creating blocks and patterns without first opening an engineering ticket.
This moves engineering later in the cycle rather than removing it. A designer can bring an installable first version, so the conversation starts with behavior instead of a static handoff. Business logic, data access, security, accessibility, performance, and long-term maintenance still need engineering ownership.
Review starts in the zip, not the inserter
Telex delivers a block that installs. That shortens the path from mockup to Gutenberg. It also invites a shortcut: if it opens in the editor, it is done.
Before any shared environment, open the code. Check the block name and slug, category, attributes, save versus server render, enqueued scripts, and what the JavaScript assumes about the theme DOM. The February round-trip exists for that: download the zip, open it in VS Code or Cursor, adjust, send the file back, and keep iterating with the model.
Automattic described designers creating blocks and patterns without opening a ticket at the start. That shows a shorter cycle. Review is still required, only now it starts from an artifact that already runs. HTML escaping, performance, security, and who maintains the block remain engineering decisions.
Visual interaction and the block that touches data
The experiments Marko Ivanovic, Noam Almosnino, and Nick Hamze published are, in large part, expression: a text scrambler, a carousel, notes, icons, blocks nobody would have paid to exist. That is the territory where Telex shortens the distance from idea to something installable.
A block that reads a post type, checks a capability, writes user meta, calls an external API, or builds a query from a URL parameter belongs in another queue. The model generates the shell. It does not know the site's data contract or the team's sanitization policy.
A static content block arrived? Review can be visual, keyboard, and contrast. A block that "fetches products" or "shows the logged-in user" arrived? Stop in PHP and REST. Where the data comes from, what happens with empty input, who is allowed to insert the block.
A cutoff between the experiment and the repository
Version history now creates a new version when you restore the past, instead of overwriting current work. You can explore without destroying what is good. Pair that with the zip: stay in Telex while the problem is layout and micro-interaction; leave for the IDE when the problem is behavior, data, or build.
Write a cutoff. After two Telex loops and one pass in the local editor, the block enters the theme or plugin repository, with a test and a name attached. Without that cutoff, the zip sits on the machine of whoever generated it. Three months later, nobody knows which file is the source.
Telex is available in seven languages and remains a free experiment. The public changelog helps you follow along. Do not pin a product roadmap to an SLA Automattic has not published. Use it to shorten the cycle. Keep another path if price, model, or availability change.
There is a data limit as well as a code limit. Prompts and reference images go through Claude and Gemini. A mockup of an unreleased product, confidential copy, and a screenshot of a panel with user data should not go into the upload without a written rule. A shorter cycle does not justify leaking what the team would not paste into a public chatbot.
What does not ship on a site with traffic
Do not install the generated block straight into production. First a development site, Studio, Playground, or staging. Test in the inserter, the post editor, the site editor, with short and long text, with the real theme, and with a user who is not an administrator.
Look for duplicate scripts and styles, layout shift, keyboard focus, contrast, and the state with an empty attribute. The playful blocks from the internal posts are good for learning the tool. They are poor candidates for the home of a site with page cache and CSP until someone reads the JavaScript.
A shorter cycle moves engineering to another moment in the flow. That moment needs a calendar slot. If the team only celebrates the installable component, Gutenberg gains another block with no owner and a prompt in the history.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.
