This is very close to what we’ve been struggling with too.
But in practice, a lot of things never even become “tasks” — they stay in threads.
We tried reactions as status (✅ = done, etc.)
It works a bit, but breaks quickly with many active discussions.
The main issue for us is earlier:
how to track which threads actually need action vs just being informational.
We started thinking about threads more like an inbox (needs reply / waiting / resolved), and even built a small tool around this idea:
https://www.threaddesk.work/
Feels like there’s a gap before tasks — at the thread level.
Alex Lukon
This is very close to what we’ve been struggling with too.
But in practice, a lot of things never even become “tasks” — they stay in threads.
We tried reactions as status (✅ = done, etc.)
It works a bit, but breaks quickly with many active discussions.
The main issue for us is earlier:
how to track which threads actually need action vs just being informational.
We started thinking about threads more like an inbox (needs reply / waiting / resolved), and even built a small tool around this idea:
https://www.threaddesk.work/
Feels like there’s a gap before tasks — at the thread level.