-
Notifications
You must be signed in to change notification settings - Fork 73
Description
Are you requesting a new GitHub Repository within opensearch-project GitHub Organization?
yes
GitHub Repository Proposal
GitHub Repository Additional Information
1. What is the new GitHub repository name?
strands-agents-opensearch-session-manager
2. Project description and community value?
A session repository implementation that integrates Strands Agents with OpenSearch's Agentic Memory feature (GA in version 3.3). This adapter enables persistent storage and retrieval of agent sessions, conversations, and memory data using OpenSearch as the backend. Community Value:
- Seamless Integration: Provides out-of-the-box compatibility between Strands Agents and OpenSearch, reducing development effort for users
- Persistent Memory: Enables agents to maintain context across sessions, improving conversational AI experiences
- Scalable Storage: Leverages OpenSearch's distributed architecture for reliable, scalable session management
3. What user problem are you trying to solve with this new repository?
Currently, users who want to integrate OpenSearch's Agentic Memory feature with Strands Agents must build custom adapters from scratch. This repository solves that problem by providing:
- A ready-to-use session manager implementation
- Simple configuration and setup
- Consistent API aligned with Strands Agent's session interface
This allows developers to focus on building their agents rather than implementing storage infrastructure.
4. Why do we create a new repo at this time?
OpenSearch introduced the Agentic Memory feature as GA in version 3.3. Following this release, we developed and validated a functional demo integrating the OpenSearch Session Manager with Agentic Memory. Creating this repository provides the community with an opportunity to leverage Agentic Memory alongside Strands Agents as both projects continue to evolve and mature.
5. Is there any existing projects that is similar to your proposal?
No, to my knowledge. There is no existing OpenSearch-based session manager implementation for Strands Agents.
6. Should this project be in OpenSearch Core/OpenSearch Dashboards Core? If no, why not? Or, shall we combine this project to an existing repo source code in opensearch-project GitHub Org?
No, this should be standalone repository since this is an integration adapter, not core OpenSearch functionality. This project will also have it's own release cycle, allowing faster iteration.
7. Is this project an OpenSearch/OpenSearch Dashboards plugin to be included as part of the OpenSearch release?
No, this repo will run independently. It will follow its own release cycle and published via PyPI
GitHub Repository Owners
1. Who will be supporting this repo going forward?
ML Commons team will support this repository.
2. What is your plan (including staffing) to be responsive to the community (at a minimum, this should include reviewing PRs, responding to issues, answering forum questions?)
The maintainers will actively maintain the repository by reviewing PRs, triaging and addressing issues, and responding to community questions.
3. Initial Maintainers List (max 3 users, provide GitHub aliases):
- nathaliellenaa
- ylwu-amzn
- dhrubo-os
- b4sjoo
GitHub Repository Source Code / License / Libraries
1. Please provide the URL to the source code.
This is the demo code, we will modify it further https://github.com/nathaliellenaa/strands-agents-opensearch-session-manager
2. What is the license for the source code?
The source code is Apache-2.0 licensed
3. Does the source code include any third-party code that is not compliant with the Apache License 2.0?
No
What is the publication target(s)?
You can choose multiple targets from the list.
PyPI
Notes (DO NOT CHANGE)
Next Steps:
-
If this is about creating a new GitHub Repository
- Build Interest Group (BIG) and its members will review your proposal and provide feedback
- Review of Proposal, asking questions, adding comments
- If there is any concern regarding the naming / IP, additional IP review will be requested
- Involve Subject Matter Experts from other repositories on the proposed topics
- Ensure new repositories align with the foundation’s charter
- Review the provided source code if any
- Send final feedback and recommendations to the Technical Steering Committee
- Technical Steering Committee (TSC) will have a vote based on BIG feedback, and reply back the vote as a comment in this issue by a TSC member
- At least three positive (+1) TSC members' votes are necessary, and no vetoes (-1) after a one week period, then Admin Team will open a repo creation ticket with Linux Foundation
- Linux Foundation verify the votes and create repo
- Admin Team setup automations on repo settings, secrets, scanning, add initial maintainers, and more
- Repository delivered to the original requester
- Build Interest Group (BIG) and its members will review your proposal and provide feedback
-
If you already have a GitHub repo and just want to add new publication target(s)
- Admin Team will review your request and follow up
Track the progress of your request here: Engineering Effectiveness Board (view).
Member of @opensearch-project/admin will take a look at the request soon.
Thanks!
Metadata
Metadata
Assignees
Labels
Type
Projects
Status