-
Notifications
You must be signed in to change notification settings - Fork 1
Add Agent Memory Search Capability with Access Controls (Vector Store Branch) #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: vector-store
Are you sure you want to change the base?
Conversation
Co-authored-by: phrocker <1781585+phrocker@users.noreply.github.com>
|
@copilot this should not be against main, but against the vector-store branch |
Done! I've rebased the Agent Memory Search feature onto the Technical details:
The Agent Memory Search functionality remains unchanged and fully functional. The commits now build upon the vector store enhancements rather than the main branch base. Commit: 2a91350 Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot seems like you have some conflicts... |
Fixed the conflicts! The issue was a syntax error in I've successfully:
The branch is now properly based on the vector-store branch (commit bf48ab6) and all conflicts are resolved. Commit: 87b0afd Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
…s pods (#103) * Initial plan * Add RBAC permissions for integration-proxy to access tenant-agents namespace Co-authored-by: phrocker <1781585+phrocker@users.noreply.github.com> * Add documentation comments explaining cross-namespace RBAC setup Co-authored-by: phrocker <1781585+phrocker@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: phrocker <1781585+phrocker@users.noreply.github.com>
This PR implements comprehensive Agent Memory search functionality that allows authorized users to search through agent communications with various filtering options and proper access controls. The implementation has been rebased onto the
vector-storebranch to ensure compatibility with the existing vector store functionality.Key Features
Enhanced Repository Layer
AgentCommunicationRepositoryfor content, agent, and date-based filteringService Layer
AgentMemorySearchServicewith multiple search capabilities:API Endpoints
GET /api/v1/agent/memory/searchRESTful endpointcontent,agent,startDate,endDate,page,sizeUser Interface
/sso/v1/agent/memory/searchAccess Control
@LimitAccess(applicationAccess = {ApplicationAccessEnum.CAN_MANAGE_APPLICATION})Usage Example
Users can now search agent memories using various combinations:
Technical Notes
This PR has been rebased onto the
vector-storebranch to ensure compatibility with the vector store enhancements. All functionality remains unchanged while properly integrating with the vector store infrastructure.The implementation includes comprehensive unit tests and follows existing code patterns for consistency and maintainability.
Fixes #102.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.