ResearchResearch paper

AesCode separates visual quality from verifiable code correctness

Submitted October 13, AesCode uses generated images as style guidance for editable HTML/CSS artifacts such as dashboards.

Why it matters

Prompts remain the content authority; attractive references are not ground truth.

A closer look

A design graph routes properties to deterministic checks or visual-model judging, with separately normalized rewards. Authors evaluate 300 infographic samples with three unselected generations each.

Who this is for

UI-code generation, visualization and model-evaluation teams

Original sources

Revisions & corrections (1)

— New research candidate discovered through October 14 papers, original arXiv submission October 13 verified against author project and repository; no unreplicated ranking or performance advantage asserted.

Related events

Research

A second, independent VeriCUA turns GUI-task acceptance into active evidence gathering with abstention

A Google and University of Hong Kong team submitted a separate project also named VeriCUA on October 29. It inspects an environment or recording before constructing a task rubric, then gathers missing evidence through GUI, accessibility-tree, file and database reads, marking requirements met, unmet or unknown. In online experiments it reduces false positives against baselines on AndroidWorld, OSWorld and ScienceBoard.

Research

GUI‑JEPA replaces token-by-token action decoding with candidate-conditioned latent scoring

Submitted October 27, GUI‑JEPA targets single-step mobile GUI action selection. It transforms JEPA representations pretrained on unlabeled interface screenshots for each action and region candidate, then scores accessibility-tree candidates in one batch instead of asking a 7B vision-language model to decode an action token by token.

Research

TAM turns verified task advancement into online state and reusable operations for GUI agents

Submitted October 27, Task Advancement Memory (TAM) uses what has been reliably accomplished at two timescales: it maintains verified progress, remaining goals and visual evidence during a task, then extracts reusable operations from locally successful segments after the task, including segments inside an overall failed workflow.