fix(agent): create loops through HTML import#70
Merged
Conversation
DavidBabinec
marked this pull request as ready for review
June 17, 2026 12:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
list_loop_sourcessite AI tool that exposes loop source ids, data table ids, ordering/filter metadata, and valid{currentEntry.field}binding tokens.<instatic-loop>support to the HTML importer so AI-authored HTML creates a realbase.loopnode instead of a plain container.{{post.*}}bindings.Why
The site agent could previously guess loop bindings and source ids, but it had no read tool for the available dynamic data tokens. More importantly, the HTML import path had no loop marker, so attempts to create a loop through
replaceNodeHtmlimported as ordinary container markup.Impact
Agents can now create post/data loops through the existing HTML-native write surface using
<instatic-loop data-source-id="data.rows" data-table-id="...">, and loop children can use returned{currentEntry.*}tokens reliably.Verification
bun installbun run buildbun testbun run lint