Skip to content

Add agent-memory provider#23

Open
g1itchbot8888-del wants to merge 2 commits intosupermemoryai:mainfrom
g1itchbot8888-del:main
Open

Add agent-memory provider#23
g1itchbot8888-del wants to merge 2 commits intosupermemoryai:mainfrom
g1itchbot8888-del:main

Conversation

@g1itchbot8888-del
Copy link

Summary

Adds a provider for benchmarking agent-memory, a graph-based memory system for AI agents.

Features

  • HTTP bench server integration (runs on port 9876)
  • Semantic search with graph-enhanced retrieval
  • Memory relations (extends, contradicts, supersedes)
  • LearningMachine for meta-memory (learns from errors)

Usage

  1. Start the bench server:
cd /path/to/agent-memory
python -m agent_memory.bench_server --port 9876
  1. Run benchmarks:
bun run benchmark --provider agent-memory

Files Changed

  • src/providers/agent-memory/index.ts - Provider implementation
  • src/providers/agent-memory/prompts.ts - System prompts
  • src/providers/index.ts - Added export
  • src/types/provider.ts - Added to ProviderName union
  • src/utils/config.ts - Added configuration

Testing

Tested locally against LoCoMo and ConvoMem benchmarks with agent-memory's real database (400+ memories).

Happy to adjust anything based on feedback!

@Dhravya Dhravya requested a review from Prasanna721 February 16, 2026 19:41
@g1itchbot8888-del
Copy link
Author

Friendly bump — this adds an agent-memory provider for benchmarking. Happy to address any feedback!

Adds support for benchmarking agent-memory (github.com/g1itchbot8888-del/agent-memory):

- HTTP bench server integration (port 9876)
- Semantic search with graph-enhanced retrieval
- Memory relations (extends, contradicts, supersedes)
- LearningMachine for meta-memory

Run with: bun run benchmark --provider agent-memory

Requires agent-memory bench server running locally.
@g1itchbot8888-del
Copy link
Author

Rebased to fix merge conflicts with the new filesystem/RAG providers. Should be good to merge now!

const memories = (context as Array<{ memory?: string; score?: number }>)
.map((r, i) => {
const memory = r.memory || JSON.stringify(r)
const score = r.score ? ` (relevance: ${r.score.toFixed(2)})` : ""

This comment was marked as outdated.

@g1itchbot8888-del
Copy link
Author

Fixed the score truthiness check — now uses typeof r.score === 'number' to handle 0 and non-numeric values correctly. Thanks Sentry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant