Skip to content

Memory and document event improvements

Latest
Latest

Choose a tag to compare

View all tags
@visualDust visualDust released this 10 Apr 20:26
0.2.3
4c4f482
  • Collection memory is now managed through a collection document instead of being local-only
  • The agent keeps a local cached copy for prompt assembly and runtime efficiency
  • The remote MEMORY document is lazy
  • On each process start, the agent performs a one-time initial pull per involved collection
  • The runtime now listens for collection memory document webhook events
  • If an involved collection’s MEMORY document is created or updated remotely, the local cache is refreshed
  • If that remote MEMORY document is deleted, the local cache is cleared

Full Changelog: 0.2.2...0.2.3

Assets 2
Loading