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

Allow to modify the system prompt after the playground interactions started #618

Open
slemeur opened this issue Mar 21, 2024 · 6 comments
Open
Assignees
Milestone

Comments

@slemeur
Copy link
Contributor

slemeur commented Mar 21, 2024

After #617, the user will not be able to modify the system prompt, once the playground interactions started.

In this issue, we would to better handle the situation and let the user modify it, but also understand the impact of that change.
In order to allow the comparison of the behavior of the model with a different system prompt, the user should still be able to see the previous interactions (and eventually continue testing with more interactions, with the different system prompts).

Proposal:
When the user changes the system prompt after having started interacting, we should bring the user into a new playground environment with the new system prompt.

We would display a message asking the user what the desired "re-play" stated is.
Two options to be proposed to the end-user:

  • Does the user wants to replay all the messages sent?
  • Or does the user prefer to start from scratch?
@slemeur slemeur added this to the 1.1 milestone Mar 21, 2024
@axel7083
Copy link
Contributor

I would argue that re-playing all the conversation does not really make sense, I would propose that only the first message of the user would be replay, as the responses following it depends on the conversation, which do not have the same history after changing the system prompt.

@feloy
Copy link
Contributor

feloy commented Apr 30, 2024

I would argue that re-playing all the conversation does not really make sense, I would propose that only the first message of the user would be replay, as the responses following it depends on the conversation, which do not have the same history after changing the system prompt.

@slemeur wdyt?

In the new playground, it would be nice to have the user proposed the prompt from the previous session, until the user changes the prompt.

For example:

playground 1

  • prompt 1
  • prompt 2
  • prompt 3

user changes system prompt =>

playground 2

  • prompt 1 (prompt is pre-written in the textarea, the user can change it or press send directly, here the user presses send)
  • prompt 2 bis (prompt "prompt 2" is pre-written in the textaera, but this time, the user changes the prompt)
  • ... (the prompt is not pre-written, as the user changed the previous one)

@axel7083
Copy link
Contributor

I would argue that re-playing all the conversation does not really make sense, I would propose that only the first message of the user would be replay, as the responses following it depends on the conversation, which do not have the same history after changing the system prompt.

@slemeur wdyt?

In the new playground, it would be nice to have the user proposed the prompt from the previous session, until the user changes the prompt.

I like this idea!

@axel7083 axel7083 modified the milestones: 1.1, 1.2 May 2, 2024
@slemeur
Copy link
Contributor Author

slemeur commented May 13, 2024

In this flow, we need to let the user deciding how to re-play (or not) the conversation, but the user needs to be aware of what's going to happen, otherwise the experience will be confusing.

I can imagine the proposed experience to be tedious and long, if the number of prompt is high.

When the user edits the system prompt, we should provide the ability to either:

  • Restart a new playground with a different system prompt: in this case the conversation will restart from scratch
  • Replay the conversation: in this case, we ask the user the number of messages to be replayed starting from the first one that has been sent. In another issue, we would add the ability to delete a previously sent prompt, which would grant the ability to come back to an earlier point in the conversation.

@axel7083
Copy link
Contributor

In this flow, we need to let the user deciding how to re-play (or not) the conversation, but the user needs to be aware of what's going to happen, otherwise the experience will be confusing.

I can imagine the proposed experience to be tedious and long, if the number of prompt is high.

When the user edits the system prompt, we should provide the ability to either:

  • Restart a new playground with a different system prompt: in this case the conversation will restart from scratch

I would agree with this one

  • Replay the conversation: in this case, we ask the user the number of messages to be replayed starting from the first one that has been sent. In another issue, we would add the ability to delete a previously sent prompt, which would grant the ability to come back to an earlier point in the conversation.

This is a very complicated mechanic which would be hard to implement in terms of UI design. I would suggest waiting for user's feedback? To see if we really need such feature, as we have a lot of area of improvement already including the playground base UI

@feloy
Copy link
Contributor

feloy commented May 13, 2024

In this flow, we need to let the user deciding how to re-play (or not) the conversation, but the user needs to be aware of what's going to happen, otherwise the experience will be confusing.
I can imagine the proposed experience to be tedious and long, if the number of prompt is high.
When the user edits the system prompt, we should provide the ability to either:

  • Restart a new playground with a different system prompt: in this case the conversation will restart from scratch

I would agree with this one

I'm not sure to understand. What would be the difference with the existing possibility to start a new playground?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📅 Planned
Development

No branches or pull requests

3 participants