Prerequisites
Feature Description
I would like Canvas to implement a generic WebSocket service that can be used across different services, starting with the flow engine controller. Currently, the flow engine uses REST endpoints (like execute_crewai_flow_chain), but we need a more dynamic, real-time communication channel that can be reused by other services in the future.
Use Case
This feature would be useful when:
- Needing real-time updates on flow execution status
- Implementing interactive agent responses
- Building collaborative features where multiple users need to see updates simultaneously
- Creating dynamic dashboards that show real-time progress
- Implementing long-running operations that need to provide progress updates
- Future services that require bi-directional communication
Self-service
Prerequisites
Feature Description
I would like Canvas to implement a generic WebSocket service that can be used across different services, starting with the flow engine controller. Currently, the flow engine uses REST endpoints (like execute_crewai_flow_chain), but we need a more dynamic, real-time communication channel that can be reused by other services in the future.
Use Case
This feature would be useful when:
Self-service