microsoft / microsoft/simplechat
Design generic monitor trigger model for workflows
@paullizer is already working on this.
Since Jun 26, 2026.
- Dominant language
- Python
- Stars
- 152
- Forks
- 116
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 122
Description
## Summary
Redesign workflow triggers so users choose a generic Monitor trigger, then configure a monitor type such as SMB/File Sync, workspace changes, agent output, SQL/KQL query, or custom connector.
## Scope
- Review the relevant SimpleChat implementation surfaces and decide the recommended approach.
- Produce enough design detail to split implementation into follow-up issues if needed.
- Capture permission, configuration, scale, and validation concerns before implementation.
## Acceptance Criteria
- [ ] The design or research outcome answers the open implementation questions.
- [ ] Follow-up implementation issues are identified if the work is larger than one delivery slice.
- [ ] Risks, dependencies, and validation requirements are documented.
## Notes
- Source backlog entry: Generic Monitor Trigger Model
- Source file: priv-simplechat-2/grouped_feature_fix_backlog.md
- Backlog status: Research
- Current anchors: `docs/explanation/features/PERSONAL_WORKFLOWS.md`, `docs/explanation/features/GROUP_WORKFLOWS.md`, `application/single_app/background_tasks.py`
- Proposed roadmap priority: P2
- Proposed roadmap size: L
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.