Team Workflows Q3 2026 Megaissue
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Feature request
Goals
🚀 Goal 1: Become a 2030 Workflows Product (Champion: @mayteio)
Motivation: Agents are far better at building context and making modifications than users.
What we'll ship:
- Fully AI native & agentic workflow product
- Chat interface for rapid iteration
- Move to read-only UI for workflows / email templates / messaging
- Removal of hefty existing UI if new experience & user testing is superior
- Revisions
- Reshape APIs to be agentic-friendly for rapid turnaround
🚀 Goal 2: Fit into self-driving products (Champion: @dmarchuk)
Motivation: A single person can drive 1000 workflows.
What we'll ship:
- Get our data right so 'self-driving' can first suggest changes
- Integrate with 'self-driving' to propose the change (using revisions and APIs)
- Test revisions of actions against each other for improvements (still human in the loop)
- Self-driving applying the outcomes of the A/B tests
🚀 Goal 3: Reliability & Trust (Champion: @meikelmosby)
Motivation: Customers trust us fully with their workflows.
What we'll ship:
- Harden our systems to never drop data
- Finalise the re-run system so we can replay failed invocations
- Full visibility into every messaging channel
🚀 Goal 4: Nail Messaging (Champions: @dmarchuk & @meikelmosby)
Motivation: Feature parity on table-stakes features with our competitors.
What we'll ship:
- Behavioural cohorts (no backfilling)
- Push notifications
- A/B testing
- Email events
- Messaging metrics
- Email with multiple links / more detailed metrics
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.
Research direction
The issue is a roadmap megaissue and names no files, tests, or entry points. Start by selecting one narrowly scoped goal and finding or creating a dedicated issue with a specific implementation location and acceptance criteria; the overall work is done only when each listed workflow objective has been separately defined and delivered.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100