Refactor ActionsSubtask for more precise initialization logic #1626
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.
Describe your changes
Fixed
Answer:
being trimmed from LLM's final answer even when using native tool calling.This PR changes the logic of
ActionsSubtask
to be more precise about how it parses the input Actions. Previously, it followed the decision tree of:use_native_tools=False
.use_native_tools=True
.The problem is that even Prompt Driver with
use_native_tools=True
eventually generates a TextArtifact. Now the decision tree looks like:use_native_tools=False
.use_native_tools=True
.The way ReAct Artifacts are "marked" is via a metadata field,
is_react_prompt
. Technically this change of behavior is a breaking change but I highly doubt anyone is passing inputs intoActionsSubtask
directly.Issue ticket number and link
NA