feat: added persona/human_name
fields to Preset
#1134
Merged
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.
Added persona/human_name fields to presets to distinguish between the filename and the actual values used to init memory.
This fixes a bug in the
GET /api/agents
route where thehuman
andpersona
fields returned in the response were expected to be the names of the human/persona, not the actual value.Things to consider @sarahwooders :
preset.name
will now be null/None unexpectedly?Preset(
constructors are created, but I might have missed something.Now the response looks as expected (top-level
human/persona
are the names, and the real values are inside the nested memory block):