You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Use case:
I have three sequential LLM nodes in a workflow, and I want to enhance the prompt for LLM2, which depends on the output from the previous LLM1 node.
Current approach:
There are two options for debugging the node:
Testing from scratch: This option takes more tokens and time since the first LLM node is already working fine.
Viewing the last test log, copying the inputs for LLM2, and pasting them into the debug form: This is my preferred option but could be made more convenient.
Desired improvement:
It would be great if there were a shortcut in the target node’s debug window to use the inputs from the last test log.
2. Additional context or comments
No response
3. Can you help us with this feature?
I am interested in contributing to this feature.
The text was updated successfully, but these errors were encountered:
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Use case:
I have three sequential LLM nodes in a workflow, and I want to enhance the prompt for LLM2, which depends on the output from the previous LLM1 node.
Current approach:
There are two options for debugging the node:
Desired improvement:
It would be great if there were a shortcut in the target node’s debug window to use the inputs from the last test log.
2. Additional context or comments
No response
3. Can you help us with this feature?
The text was updated successfully, but these errors were encountered: