search

frdel / agent-zero

Agent Zero AI framework
Other
4.65k stars 1.02k forks source link

Inconsistent Time Retrieval: Need for Manual Memory ID Input #44

Open oziau opened 2 months ago

oziau commented 2 months ago

Feedback on agent-zero project: Memory retrieval and time task inconsistencies

Thank you for the excellent agent-zero project. I've been using it daily and learning a great deal. However, I've encountered an issue that I'd like to bring to your attention:

Issue Description

  1. When requesting the current time for Sydney, Australia (AEST), the agent consistently returns an incorrect time. I've been using this prompt as a test case.

  2. After subsequent requests for time in various locations, the agent fails to retrieve the correct time.

  3. To resolve this, I need to manually provide a memory ID, after which the agent correctly retrieves and provides the time.

Observation

It appears that the agent is not automatically referring to its memory for previously completed tasks. This necessitates manual intervention to ensure accurate responses.

Question

Could you please explain why the agent doesn't automatically refer to its memory? Is this an intended behavior, or is there a potential improvement that could be made to enhance the agent's memory retrieval capabilities?

Thank you for your time and continued work on this project. Any insights or potential solutions would be greatly appreciated.

blind0wl commented 1 week ago

The docker container is running timezone UTC+0 by default. I went in and changed the timezone of the agent-zero docker container manually. I'm not sure if it will be persistent as I've only just came across this, but my steps were as follows:

docker exec -u 0 -it agent-zero-exe bash
rm -rf /etc/localtime
ln -s /usr/share/zoneinfo/Australia/Sydney /etc/localtime

Then ran date to check it.

Then went back and asked agent-zero to check the time. In my instance its running a python script to feed the time back to it.