feat: add a last_run
field to the agent state model
#1124
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.
Please describe the purpose of this pull request.
last_run
field to the agent state modelmessages[-1].created_at
correct AgentStateModel's created_at to be a datetime (like the other created_at fields) instead of an intQuestion for @sarahwooders - another way to do this is to keep alast_run
field inside theAgentState.state
that gets updated dynamically/eagerly whenAgent.step()
is called. Any preference on eager vs lazy?How to test
Run an API call to list all agents (https://memgpt.readme.io/reference/list_agents_api_agents_get) and the
last_run
fields should exist and be valid.Have you tested this PR?
GET localhost:8283/api/agents