Basic multi client support #759
Draft
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.
Description
State['client'] now becomes a dictionary mapping from str -> client object
we then need to add a new field to State to track what the current client is
in init_state, we handle whether the user passed in a dictionary for the llm client mapping or a single client
add a get_next_client function to multi_turn_env to implement client switching logic
decided that get_prompt_messages should own this model switching logic, but not sure if that is best option
for more robust solution, would need prompt message rewrite logic according to what client we are on