Skip to content
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

Node re-run and iteration judgment termination #8489

Open
5 tasks done
suwubee opened this issue Sep 16, 2024 · 2 comments
Open
5 tasks done

Node re-run and iteration judgment termination #8489

suwubee opened this issue Sep 16, 2024 · 2 comments
Labels
💪 enhancement New feature or request

Comments

@suwubee
Copy link

suwubee commented Sep 16, 2024

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • 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.

LLM always generates the content we specify at one time, but in the long process, there may be a problem in a certain step in the middle, or we need to readjust the prompt word or regenerate it according to the middle part. The iteration function is indeed good for long processes, but it lacks the output after judging the conditions.
I found a similar function in coze, which can insert questions and answers in the loop to interact with the user and terminate the loop separately. But there is a problem here. If new auxiliary prompt words can be added when looping again, that is, the user gives new suggestions from the question and answer, so that LLM can regenerate.
image

2. Additional context or comments

I saw this mentioned as early as a year ago, but no one seems to be paying attention to this feature.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
@dosubot dosubot bot added the 💪 enhancement New feature or request label Sep 16, 2024
@laipz8200
Copy link
Collaborator

I've outlined your request as follows:

  1. A node similar to the Answer Node that offers the user multiple choices.
  2. A break function in the Iteration Node.

Please let me know if this aligns with your needs!

@suwubee
Copy link
Author

suwubee commented Sep 18, 2024

I've outlined your request as follows:

  1. A node similar to the Answer Node that offers the user multiple choices.
  2. A break function in the Iteration Node.

Please let me know if this aligns with your needs!

1, yes
2, not only break, with matching conditions require restarting the node.

What I hope to achieve is that at each key node, the user can decide whether to continue or whether to re-run the node. This will generate higher quality and more in line with the logic of interaction, instead of generating everything according to the established process like now, with no room for adjustment.

I create with coze workflow, but unfortunately, when the loop is restarted, the subsequent conversation records are not introduced, but only the variables are introduced.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💪 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants