List view
- Due by March 20, 2026•9/9 issues closed
- Overdue by 6 day(s)•Due by March 13, 2026•7/11 issues closed
- Overdue by 13 day(s)•Due by March 6, 2026•14/32 issues closed
- Overdue by 20 day(s)•Due by February 27, 2026•19/37 issues closed
- Overdue by 27 day(s)•Due by February 20, 2026•32/53 issues closed
- Overdue by 1 month(s)•Due by February 16, 2026•26/28 issues closed
- Overdue by 1 month(s)•Due by February 6, 2026•46/57 issues closed
- Overdue by 1 month(s)•Due by February 2, 2026•31/31 issues closed
- Overdue by 2 month(s)•Due by January 5, 2026•9/9 issues closed
- Overdue by 3 month(s)•Due by December 19, 2025•7/7 issues closed
- Overdue by 3 month(s)•Due by November 28, 2025•1/1 issues closed
- Overdue by 3 month(s)•Due by November 24, 2025•29/29 issues closed
- Overdue by 5 month(s)•Due by October 20, 2025•14/14 issues closed
- Overdue by 5 month(s)•Due by October 13, 2025•14/14 issues closed
The product is evolving from a single-turn task executor to a **Persistent Process Automation Platform**. This requires three major feature upgrades in this version: **Multi-turn conversations, schedule/event-based trigger for tasks, and enhanced memory & context.** In addition, to activate the developer ecosystem, we need to support the Linux system. For user scenarios, we will first focus on the **growth and marketing** scenario, which can attract early adoption and dissemination by independent developers.
Overdue by 4 month(s)•Due by October 31, 2025•5/5 issues closed