fix: (1) refactor in Agent.step()
to fix out-of-order timestamps, (2) bug fixes with usage of preset/human
vs filename values
#1145
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.
step()
to fix out-of-order timestamps due to duplicate messagepersona
andhuman
- in many instances we were using them aspersona/human_name
, even though the values were expected to be the full valuePreset
model to contain apersona_name
andhuman_name
persona/human_name
fields toPreset
#1134list_agents
GET
routeMany of the line diffs are to fix a tangentially related bug wherehuman_name
andpersona_name
aren't being used correctly. For a future PR, we should strip this field and replace it withhuman_id
andpersona_id
that point to the DB.- [ ] TODO: striphuman/persona_name
, and refer to ID in table instead