A New AI Helper You Can Use Together With Other People

Eugenia Kuyda launched Wabi for everyone on October 19, 2026, a personal AI helper that works like a messenger app. TechCrunch
Wabi organizes help into threads. Think of each thread as a shared notebook inside a chat, set up for one job or long-term plan. Threads can be shared, so several people and the assistant can talk and work together in the same place.
That idea goes back to where Kuyda started. She showed a chat bot called IO on stage at TechCrunch Disrupt in 2014. IO was meant as a lifestyle helper to book restaurants and vacations and handle other tasks. It was the first product from her startup Luka. Luka later became Replika, the AI companion company.
Kuyda has since left her job as CEO of Replika and started Wabi. Wabi raised a $20 million pre-seed round reported at its first launch.
Wabi did not start as a messenger. It worked as an app builder where typed requests made simple apps, before changing into a personal AI agent that can make screens when needed. TechCrunch That change moved screen-making out of a separate building step and into the chat itself.
On its homepage, Wabi calls itself "The AI assistant you use together". Wabi It runs on computers and phones, so people can start on one device and continue on another. It also offers widgets that can be added to iOS or Android home screens.
The broader context here is a shift from helpers made for one person and one chat to helpers that stick around and work with groups. Most helpers still keep each person and each chat separate. Wabi threads last over time and let other people in, so information has to stay correct across people, devices, and time. Who can see what, what the AI remembers in each thread, and how long threads are kept become basic parts of the system.
In my view, the hard part is shared control. A private thread is mostly about memory and planning. A shared thread has to keep track across people. The assistant must remember who asked for what, who can see what, and which instructions still count later. Done well, that cuts copy-and-paste work in group plans, family logistics, and small-team jobs. Done poorly, it leaves people unsure who said what and who is in charge.
Looking at what this means for builders, making screens when needed fits that model. A normal app screen assumes one fixed job and one user. A shared thread needs simple lists, bookings, tables, and buttons that show up, change, and go away as the work changes. Widgets and use across devices point the same way. The helper lives where people already spend time.
Worth flagging is how familiar this feels. Helper bots in 2014 promised to handle bookings and errands by chat, but they used rigid scripts and people working behind the scenes. Today's models can understand requests, use software tools, and remember context longer. The pitch has come full circle. What will decide Wabi is less smooth chat than dependable follow-through in shared threads that last.


