feat: add AtMem memory provider - #43
Open
aetna000 wants to merge 1 commit into
Open
Conversation
|
@aetna000 is attempting to deploy a commit to the Vectorize Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds AtMem as a local provider for Agent Memory Benchmark.
The adapter:
raw_response; andAtMem is pinned to
2.2.7b1so the benchmark lock resolves the exact published package and its stableatmem-atbot==0.1.0companion.Reproduce
Validation
atmem==2.2.7b1: 2 passed.uv lock --checkandgit diff --checkpassed.The repository's complete environment cannot be installed on this macOS x86_64 host because the existing
lancedb==0.29.2dependency has no compatible wheel. The AtMem adapter itself was tested in an isolated Python 3.12 environment using the published wheel.AI assistance
Codex generated most of the adapter and tests. The public AtMem APIs were checked against the tagged release, and the tests and benchmark smoke above were run against the published wheel.