Agent orchestration #7
Closed
Conversation
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
- Introduced new tables for workspaces, workspace members, and invitations in the database. - Updated chat structure to associate chats with workspaces and modified related queries. - Refactored user ID checks in chat and vote routes to use the new createdBy field. - Implemented functions to create and retrieve workspaces and manage workspace members.
- Added workspace membership checks for chat creation and deletion to ensure users are authorized. - Updated chat handling to associate messages with the correct workspace. - Removed unused workspace creation logic and streamlined user checks. - Adjusted container tagging for memory tools to use channel IDs for better isolation.
… in documents API - Added support for chatId in the POST request to fetch documents, allowing for channel-scoped memory. - Implemented checks to verify workspace membership for the provided chatId, returning appropriate error responses for unauthorized access. - Updated container tagging logic to prioritize chatId while maintaining backward compatibility with user ID.
…space membership checks - Implemented validation for workspaceId in the GET request to ensure it is provided. - Added checks to verify if the user is a member of the specified workspace before retrieving chats. - Updated chat retrieval logic to fetch chats based on workspaceId instead of userId.
…uthorization checks - Added a new GET endpoint to fetch messages associated with a specific chatId. - Implemented user authentication and authorization checks to ensure only valid users can access messages. - Included error handling for missing chatId, unauthorized access, and non-existent chats. - Enhanced message formatting to include sender information and attachments.
…space membership checks - Changed the endpoint from GET to POST to accommodate chatId in the request body. - Implemented validation for chatId to ensure the user is a member of the associated workspace. - Enhanced error handling for unauthorized access and non-existent chats. - Updated container tagging logic to prioritize chatId while maintaining backward compatibility with user ID.
…ecks - Implemented GET endpoint to retrieve workspaces for authenticated users. - Added POST endpoint for creating new workspaces, restricted to regular users. - Included validation for workspace creation requests using Zod. - Enhanced error handling for unauthorized access and invalid requests.
…mponents - Added workspace management features, including fetching and selecting workspaces. - Updated chat components to handle workspace-specific chat retrieval and message sending. - Enhanced memory graph components to support channel selection based on workspaces. - Removed legacy profile refresh logic and streamlined conversation handling. - Implemented workspace ID handling across various components for improved data management.
…mory chat and welcome message - Removed the supermemory chat and its associated messages from the initial conversation setup. - Updated profile question and response messages for clarity and relevance. - Cleaned up unused function for generating supermemory IDs.
…tion - Added 'workspace' to the Surface type and updated error messages for unauthorized workspace access. - Modified MessageQueue to include workspaceId in message tasks, ensuring proper association with conversations. - Updated enqueue methods to accept workspaceId, improving message management within specific workspaces.
…ace initialization - Implemented the creation of a private #setup channel upon workspace creation. - Seeded the channel with an onboarding message to assist users in getting started with the workspace. - Updated the message schema to ensure proper handling of the assistant's messages without a user ID.
…ain creation order for chats
…nversation switching behavior
…rkspace specificity
…d update chat and workspace titles
… checks and PATCH endpoint for renaming workspace
…ific functionality - Added dialogs for creating and renaming chats with validation. - Implemented workspace-specific storage for conversations and active chat IDs. - Improved conversation handling during workspace switches and URL-based chat selection. - Integrated error handling for workspace access and chat creation processes.
…er session update
…e functionalities - Introduced functions to create, retrieve, and delete chat connections in the database. - Added a new ChatConnection schema to support chat connection data storage.
- Added a new client for managing chat connections using the Supermemory API. - Included functions for creating, listing, deleting, and syncing connections. - Re-exported relevant SDK types for convenience and defined types for connection options and results.
- Created a new ChatConnection table to manage chat connections with relevant fields. - Added foreign key constraints for chatId and workspaceId referencing the Chat and Workspace tables, respectively. - Updated migration journal and snapshot to reflect the new schema changes.
…stead of id - Changed the parameter name from 'id' to 'connectionId' for clarity. - Updated the database query to reference 'supermemoryConnectionId' instead of 'id' for deletion.
- Added 'connection' as a new Surface type for error handling. - Updated visibility settings to include 'connection' with a response visibility. - Implemented a specific error message for 'not_found:connection' to improve user feedback.
- Added GET endpoint to retrieve chat connections with user access verification. - Introduced DELETE endpoint to remove specific chat connections, ensuring proper authorization and error handling. - Created a new callback route for handling OAuth redirects after establishing chat connections.
…ality - Updated callback route to handle connection creation with improved cookie management for pending connections. - Modified connect route to set a short-lived cookie for OAuth flow. - Introduced a new sync route for synchronizing connections with Supermemory, including authorization checks and error handling. - Refactored connection retrieval logic to improve data merging from Supermemory and the database. - Added a new database query function to delete chat connections by ID.
…ders - Implemented a dropdown menu for connecting various data sources (Google Drive, Notion, OneDrive, GitHub, Web Crawler) in both ChatHeader and ConversationHeader components. - Introduced connection management logic, including error handling and loading states during connection attempts. - Enhanced user feedback with toast notifications for connection status and errors. - Refactored connection handling to improve user experience and maintainability.
|
@BaoNguyen09 is attempting to deploy a commit to the supermemory Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.