-
Notifications
You must be signed in to change notification settings - Fork 0
Add planner tools, model, executor and UI support for data nodes #408
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.
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
zhongkaifu
merged 7 commits into
main
from
codex/add-data-node-type-with-schema-support
Jan 26, 2026
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
cb8c454
Add planner tools for data nodes
zhongkaifu 7a55be7
Improve ask_ai empty response handling
zhongkaifu 208a49c
Fix ask_ai token parameter fallback
zhongkaifu 75e2512
Rework reasoning node LLM tool execution
zhongkaifu e0d2aeb
Log reasoning request parameters
zhongkaifu 0c3b949
Raise reasoning token default
zhongkaifu 94d89df
Validate reasoning toolset via search
zhongkaifu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a non-action node has
out_params_schema, this branch returns even if the requestedfield_pathis not in the schema. That meansresult_of.<dataNode>.missingFieldpasses validation and only fails later at runtime when_get_from_contextraises aKeyError. This is a regression from the stated goal (“allow … when out_params_schema provides the requested path”): it should error when the schema exists but the path is absent, otherwise broken bindings slip through plan-time checks and crash execution.Useful? React with 👍 / 👎.