AI Page Builder Gets Web Search and Visual Checks

ملخص

Pixel’s announcement covers openconstructor updates that help AI agents build more reliable pages. The studio now detects overlapping elements, searches the web for current information, edits large pages in sections, and supports interactive tabs and filters without JavaScript, with 31 AI providers including free GPT-6.1 Sol.

DEV Community

My AI page builder couldn't see its own pages. Here's how I gave it eyes (and free GPT-6.1 Sol)

openconstructor is a free, open-source page builder. You describe a page, AI agents build it on a canvas, and you export plain HTML. This update came from watching it fail. A friend asked for "a site about the current strongest LLMs with charts", and the AI: listed GPT-4o and Claude 3.7 as the newest models, drew filter buttons that did nothing, laid a line chart on top of the table, and when I asked it to fix that, said "fixed the overlaps" and changed nothing. Every one of those has the same root cause: the model writes blind. It never sees the page, it never sees today's world, and it gets cut off when a page is long. Here's what I changed, with the code that does it. TL;DR The studio now checks every result for overlapping parts and sends them back to the model Requests about anything current trigger a web search before the model writes Big pages are edited part by part instead of rewritten whole Tabs, filters and accordions work without JavaScript 31 AI providers, some with no key at all, and GPT-6.1 Sol free through Pollinations A stop button, phone models for screens, real icons and company logos 1. Giving the model eyes: an overlap check after every answer The model can't see that its chart sits on top of the table. The browser can. After each answer is drawn on the canvas, the studio walks the rendered page and collects everything you'd actually see: text, form controls, and charts (an with at least three marks). Then it compares every pair that isn't nested. const w = Math.min(a.box.right, b.box.right) - Math.max(a.box.left, b.box.left);
const h = Math.min(a.box.bottom, b.box.bottom) - Math.max(a.box.top, b.box.top);
if (w > 2 && h > 2 && w * h >= Math.min(a.area, b.area) * 0.25) found.push(${describe(a.el)} overlaps ${describe(b.el)});
If anything is found, the model gets one concrete fix request. That means " “Google” overlaps “All models”", not "please check the layout". It gets one round only, so it can't loop. The tricky part was false alarms. A giant headline with line-height: .8 "overlapped" the nav under it, though the letters were nowhere near it. A text node's client rect is the font's whole content area, accent room and descender room included. Trimming each line box to roughly the letters fixed it: const top = q.top + fontSize * 0.16, bottom = q.bottom - fontSize * 0.2;
Overlaps that are part of the design pass the check: text on a photo, a collage of prints over a big word, the invisible radios behind custom tabs. 2. The model lived in 2024: fresh facts before writing Models confidently present what they remember as current. Mine could ask for a web search, but it almost never did. So now the studio searches before the model writes, whenever a request mentions news, prices, "latest", rankings, a year, or AI models: The model writes 1–2 search queries. The studio runs them, then opens the two best results and reads them in full. Rankings and scores live on those pages, not in snippets. For anything about AI models, it also pulls OpenRouter's public model list. It's updated daily and has release dates, context sizes and prices. Everything goes to the model, and to every agent of the page swarm, under one rule: take names, numbers and dates from these facts; if a number isn't in them, write "—". That last rule matters more than it sounds. Before it, the model filled the "score" column with plausible numbers it made up. Now it leaves a dash. 3. Buttons that did nothing: interactivity without JavaScript The pages are HTML + CSS only. Scripts are off on the canvas and in exports, on purpose. So every "All · Code · Math" filter the AI drew was a picture of a button. Instead of letting it write JS, I gave it one markup pattern and add the CSS myself after the answer:


All
Code

…overa... ![Embed Image](https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fo59cy5ruvy85drwhyas1.png) *Powered by Readybot.io*

الأحدث من Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …