Update agent prompt to extract actual JSON values from previous step results #287
Conversation
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
Member
|
This is the right approach. We will do reverse injection when generating deterministic executions instead. AKA look for words in the destination data and map them back to previous data. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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's changed ?
The issue: Agent decisions failed with "shuffle_variable_error: Failed finding 'step_0_response'"
The fix is minimal change to the agent prompt rule to extract actual JSON values from raw_response. Which prevents failed variable resolution in Singul
Alternative approach: We could add a more detailed example in the prompt, but that might make it too long.