feat: Introducing MACAE V3 version with MCP server #521
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
Strongly typed messages - sent tool call info
Macae v3 dev marktayl
feat: Enhance team upload UI and fixed TypeScript errors and React key warnings
Introduces the WebsocketMessageType enum for consistent message typing across WebSocket communications. Refactors response handlers, connection management, and orchestration modules to utilize message_type for improved clarity and extensibility. Also removes an unused __init__.py file from common services.
Replaced the UUID-based timestamp with the event loop's time from asyncio for the final result message. This provides a more accurate and relevant timestamp for message completion.
Standardizes WebSocket message types using the WebsocketMessageType enum across multiple modules. Refactors message sending to include explicit message type and data structure, and updates API endpoint for plan retrieval. Fixes and improves consistency in how messages are sent and handled throughout the backend.
feat:Macae v3 fr dev 92
Deleted the HumanFeedback, HumanClarification, and WebsocketMessage classes from messages.py as they are no longer used. This helps clean up the codebase and reduces maintenance overhead.
Introduces parseAgentMessage and parseAgentMessageStreaming methods to PlanDataService for handling agent message objects and their streaming fragments. Also refines plan approval request parsing logic for improved format support and step extraction.
Macae v3 fr dev 92
Moved WebSocket-related types (StreamMessage, StreamingPlanUpdate, etc.) from the service to the models directory for better separation of concerns. Introduced a WebsocketMessageType enum for consistent message type handling. Updated imports and usages across components, hooks, and services to use the new model definitions. Improved message handling logic in WebSocketService for clarity and maintainability.
Replaced hardcoded 'parsed_plan_approval_request' string with WebsocketMessageType.PLAN_APPROVAL_REQUEST enum across components, models, and services for improved type safety and maintainability.
Replaced string literals with WebsocketMessageType enum for agent messages and plan approval events in PlanPage and PlanDataService. This improves type safety and consistency when handling websocket events.
Replaces string literals with DataType enum for data_type fields and queries in models and CosmosDB client for consistency and type safety. Adds PlanService to encapsulate plan approval logic and updates router to use this service, improving separation of concerns and error handling.
Introduces the TeamSelected component for displaying the current team. Updates PlanPanelLeft, HomePage, and PlanPage to support an isHomePage prop and refines team selection and upload handling. Also updates PlanPanelLefProps interface to include isHomePage.
Replaces usage of current_team.id with current_team.team_id when fetching plans, ensuring correct team identifier is used for plan retrieval.
Refactored Plan model fields in frontend to match backend, replacing 'title' and 'description' with 'initial_goal' and updating status fields. Adjusted backend to ensure plan completion only when total steps are greater than zero. Updated API and TaskService to use new fields and status logic for consistency.
Replaced usage of 'description' with 'initial_goal' in PlanChat component and updated plan status check from 'status' to 'overall_status' in TaskService. These changes align with updated plan data structure.
Commented out in-progress step display in TaskList and simplified skeleton rendering logic. Modified TaskService to categorize completed tasks only by overall_status, removing PlanDataService.isPlanComplete check.
Update agentIconUtils.tsx
fix: Added the user_id explicitly to get the completed task
Replaced the agent_flow.png and architecture.png images in the documentation to reflect updated diagrams. This improves clarity and accuracy in the project's README visualizations.
Update agent flow and architecture diagrams
fix: plan activities that mention agents, Logging fixes, clean-up
chore: downmerge main to v3 feature branch
fix: updated the pipeline and bicep changes
feat: Feature Sept 2025 - MACAE V3
Roopan-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Prajwal-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
as code owners
Roopan-Microsoft
changed the title
fix: enabled the public access for search service
Prajwal-Microsoft
approved these changes
Sep 23, 2025
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
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.
Purpose
This pull request introduces two new GitHub workflow files for validating and cleaning up deployments for version 2 of both the main application and WAF, and updates the existing deployment workflows to version 3. The new v2 workflows add quota checks, resource group management, notifications, deployment, and cleanup logic, while the v3 workflows update branch names and image tagging conventions to support the latest deployment strategy.
New v2 Deployment Workflows
.github/workflows/deploy-v2.ymlfor validating main application deployments, including quota checks, dynamic resource group creation, notifications, deployment, e2e testing, and automated cleanup/purging of resources..github/workflows/deploy-waf-v2.ymlfor validating WAF deployments, mirroring the main deployment workflow with quota checks, resource management, deployment, notification, and resource cleanup/purging.Updates to Existing Deployment Workflows (v3)
.github/workflows/deploy.ymland.github/workflows/deploy-waf.ymlto "Validate Deployment v3" and "Validate WAF Deployment v3" to reflect the new version. [1] [2].github/workflows/deploy.ymlto usedev-v3instead ofdev, supporting the new deployment branch strategy.latest_v3anddev_v3for the respective branches, ensuring correct versioning of deployed images.Does this introduce a breaking change?