🚀 Feature Description
Our team has now created several custom workflows. I'm finding it a source of friction to now go fill out the custom workflow form whenever I want to use a specific workflow
It would be great if we could add other workflow "sources" which allows us to select from a drop down of workflows like the default selection:
💡 Proposed Solution
I'd like to suggest a setting in our ambient workspace that allows us to add different workflow sources. they then show up on the drop down list.
It would also be helpful to perhaps create a tab section so you can switch between viewing default workflows vs custom ones that come from a different source. We store all our ambient workflow definitions in a central git repo at the moment.
🎯 Use Cases
Teams that invest heavily in custom workflows
User Stories:
- As a user, I want to be able to quickly start a session with a custom workflow
🔧 Technical Considerations
Unsure about these at the moment, to me this sounds like it should only be a frontend change..
📊 Success Metrics
User can easily select pre-existing ambient workflows without filling out git repo, branch, directory every time
🔄 Alternatives Considered
N/A
✅ Acceptance Criteria
🏷️ Labels
- Priority: [low/medium/high]
- Effort: [S/M/L/XL]
- Component: [frontend/backend/operator/tools/docs]
- Type: [new-feature/enhancement/improvement]
🚀 Feature Description
Our team has now created several custom workflows. I'm finding it a source of friction to now go fill out the custom workflow form whenever I want to use a specific workflow
It would be great if we could add other workflow "sources" which allows us to select from a drop down of workflows like the default selection:
💡 Proposed Solution
I'd like to suggest a setting in our ambient workspace that allows us to add different workflow sources. they then show up on the drop down list.
It would also be helpful to perhaps create a tab section so you can switch between viewing default workflows vs custom ones that come from a different source. We store all our ambient workflow definitions in a central git repo at the moment.
🎯 Use Cases
Teams that invest heavily in custom workflows
User Stories:
🔧 Technical Considerations
Unsure about these at the moment, to me this sounds like it should only be a frontend change..
📊 Success Metrics
User can easily select pre-existing ambient workflows without filling out git repo, branch, directory every time
🔄 Alternatives Considered
N/A
✅ Acceptance Criteria
🏷️ Labels