Skip to content

fix(flows): normalize bare-scope jq in condition expressions + prompt guard (B17) #4707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
graycyrus merged 2 commits into from
Jul 8, 2026
+9 −1
Merged

fix(flows): normalize bare-scope jq in condition expressions + prompt guard (B17) #4707

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7c87762
fix(flows): builder-condition jq — normalize bare scope keys + warn a…
graycyrus Jul 8, 2026
f50bc2d
fix(flows): scope the jq-root guard in prompt.md to bare scope keys (…
graycyrus Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/openhuman/flows/agents/workflow_builder/prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -307,6 +307,14 @@ the run scope (`.`):
the first output is used; a bad program yields `null` (never an error).
- A string **without** a leading `=` is a literal. To emit a literal `=`, don't
start the string with it.
- **Never mix the shorthand with jq.** If an expression **begins with a bare
scope key** (`item`/`items`/`run`/`nodes`) and continues into jq syntax —
`|`, `[`, functions (`any(...)`, `length`), or anything beyond a plain
dotted path — it MUST start with `.` instead (the jq root): write
`"=.item.labels | any(.name==\"x\")"`, NOT `"=item.labels | any(...)"`. The
plain shorthand `"=item.labels"` (no jq) is fine alone. Expressions that
already start with valid jq syntax (e.g. `"=[.item.a, .item.b]"` for array
construction) don't need an extra leading dot — only bare scope keys do.

The scope exposes:

Expand Down
2 changes: 1 addition & 1 deletion vendor/tinyflows
Open in desktop
Submodule tinyflows updated 2 files
+142 −0 src/expr.rs
+35 −1 src/nodes/control_flow/condition.rs
Loading