fix: properly handle CLI flags passed to memgpt run
#833
Conversation
This file contains 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
…ew agent (previously they were ignored)
norton120
pushed a commit
to norton120/MemGPT
that referenced
this pull request
Feb 15, 2024
mattzh72
pushed a commit
that referenced
this pull request
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please describe the purpose of this pull request.
Properly handle CLI flags passed to
memgpt runwhen creating a new agent (previously they were ignored)E.g.:
Would not actually set the wrapper to
chatml-noforceif you created a new agent.How to test
memgpt run --model-wrapper XXX --debug, whereXXXis not the default. Inspect the output of--debugto spot check that the correct prompt formatter is being used.