- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The authors introduce HALo, a hierarchical agentic loop for image generation organized into three layers: the layout layer specifies what the image should contain via a structured plan of constraints, the draft layer prepares supporting material (e.g., sketches or references) for constraints that a textual prompt alone cannot enforce, and the render layer generates the final image. Self-improvement operates at two levels: an inter-layer loop that propagates plans and materials upward while routing unresolved failures downward for localized repair (with satisfied constraints held fixed), and an inner loop that enables each layer to check and refine its own output within a local context.
Critical strengths
- The motivation is well-founded. The three-layer workflow combined with the two-level self-revision mechanism addresses limitations of flat, single-loop agentic generation, particularly the risk of omitting requirements or disturbing already-satisfied constraints during revision.
- HALo achieves the best overall performance among the compared methods across four benchmarks spanning world knowledge, compositional generation, knowledge-intensive generation, and image editing.
Critical weaknesses
- The proposed inter-layer loop and inner loop introduce additional LLM calls, which increase token cost and latency. This may limit practical application value and constitutes an inherent drawback of a workflow-centric approach.
- The ideas of hierarchical and multi-level organization are not new and have already demonstrated effectiveness in prior works.
Questions for authors
- The authors note that GenClaw is particularly close to HALo, with a notable difference being the choice of backbone. Could the authors provide results obtained when using Claude-Opus-4.6 (as GenClaw did)?
- Could the authors share additional details on the design and implementation choices for the inter-layer loop and the inner loop? Clarifying whether these constitute a non-trivial module would help assess the insights they offer for future work.
6 comments
Overall, the response addresses the cost and design-detail concerns. I am satisfied with the clarifications and look forward to the promised additions in the final version.
I appreciate the explanation of how the task is decomposed by the source of failure, which provides a reasonable motivation for the proposed organization. That said, the ideas of hierarchical and multi-level organization are not new, and it is unsurprising to see performance improvements from this classic design pattern.
Follow-up to Reviewer SGL2: Motivation and Design of Failure-Source Decomposition
Thank you very much for the thoughtful follow-up. We are glad the cost and design concerns are resolved and that decomposing by failure source is seen as a reasonable motivation. All promised additions will be included in the final version.
We would also note that HALo achieves the best overall results on all four benchmarks, with the largest gains where the division acts. Compared with GenClaw under the same models, recording physical laws and time-zone reasoning as explicit derived entries lifts WISE Physics (84.2 → 91.7) and Time (82.5 → 99.2), and explicit preserve entries raise RISEBench appearance consistency (88.1 → 93.8) and strict accuracy (46.7 → 54.7).
We agree that hierarchical organization is a general pattern and do not claim it as our contribution. What we hope to highlight is the problem it solves in this task. Constraint- and knowledge-heavy image generation fails for three different reasons, which a single loop rewriting one prompt cannot tell apart:
| Problem in the task | Why a single loop struggles |
|---|---|
| The target is underspecified: it depends on implicit knowledge or reasoning | The conclusion lives only in the prompt and can be lost or overwritten before rendering |
| Text cannot enforce exact counts, orderings or visual identities | Rewording does not supply the missing structure or reference |
| Fixing one constraint can break others | A global rewrite resamples every constraint, so repair is never local |
The value of dividing generation here is that each failure becomes attributable to its cause and repairable where it arises. Our contribution is how the division is made:
- By failure source, not production stage. The layout layer asks whether each constraint is correctly specified, the draft layer whether it has checkable support, and the render layer whether the image follows both.
- A shared, entry-level target. Requirements become typed entries with provenance. A derived entry keeps its basis and the reading it rules out, so a counterintuitive conclusion is protected rather than "corrected". Once checked, the target is fixed and serves as the unit of verification and repair in every layer.
- Support bound to entries. Sketches and references attach to the entries they support instead of being appended to the prompt.
- Repair routed by cause. A failure is retried in the render layer, or returned to the draft layer when its support is insufficient; every entry is then re-checked against the same target.
We believe this principle, dividing generation where its failures arise, is a transferable insight for future agentic systems. Thank you again for your time and constructive feedback. We hope this clarification is helpful, and we would be truly grateful for your support of our work.
Response to Reviewer SGL2: Cost, Decomposition by Failure Source, and Loop Design
We thank the reviewer for the careful review. We will add the new results to the revised paper.
Q1. Cost and latency.
The overhead of the two loops is small relative to agentic baselines. Per-sample cost over the four benchmarks, compared with GenClaw:
HALo adds 1.2 LLM calls (+22%), 205 tokens (+12%) and 16 s (+8%) per sample on average, and the medians differ by one call and 16 s. With the same backbone and image model, this difference comes only from the self-check and repair loops. For both methods the mean exceeds the median, so a minority of difficult cases accounts for much of the cost.
This overhead is not a fixed cost of the workflow; it is incurred on demand:
In exchange, HALo outperforms GenClaw on all four benchmarks (Q2).
Q2. Novelty and difference from GenClaw.
HALo's contribution is not a multi-level structure as such, but how the task is decomposed: by the source of failure rather than by production stage. Agentic generation fails in two ways (Fig. 1): requirements are omitted or derived conclusions are lost before rendering, and fixing one failed requirement by rewriting the whole prompt disturbs requirements that already hold. HALo therefore separates three questions that decide whether a constraint is met: is it correctly specified (layout), does it have checkable support (draft), and does the image follow both (render). The plan is checked once and then kept fixed; a render failure is repaired in the render layer or, when its support is insufficient, in the draft layer, so repair touches only the failed entries.
GenClaw, on which HALo is built, organizes generation by stage, from conceptualization to a code canvas to rendering. The main difference is therefore the organization rather than the backbone: in HALo, the entry-level target is the unit of verification and repair, and code-rendered sketches are one type of supporting material, alongside retrieved facts and references, each attached to a specific entry.
The results support this decomposition:
Q3. Design of the two loops.
Inner loops. The layout layer reasons over the query and retrieves facts when needed; its plan is revised, within a bounded budget, until it passes a structural check against the schema and a semantic check for consistency and query coverage. The draft layer builds a code-rendered sketch or retrieves a reference for each entry that requires support, and rebuilds any item that fails its own check. The render layer checks the image entry by entry, records a correction for each failed entry, and retries once.
Inter-layer loop. Each layer passes its output upward only after its own checks pass, and later layers treat the plan as read-only. After the render retry, the reviewer diagnoses the cause of each remaining failure, and only failures attributed to insufficient support are returned to the draft layer. The draft layer rebuilds the material for those entries and keeps the rest; the image is then re-rendered, and every entry is re-checked, so a previously satisfied entry that regresses re-enters the failure set.
The module is non-trivial in two respects: the diagnosis that separates rendering noncompliance from insufficient support, and the fixed entry-level target that keeps repair and re-checking local. The routing is selective in practice: draft returns occur in 0–8.93% of initially failed cases, and 71.79–91.30% of initially failed cases pass after repair (Table 4). We will add pseudocode and the full routing rules to the appendix, and release the prompts and code.
We hope these clarifications address the reviewer's concerns and would appreciate it if the reviewer would reconsider the score.