Why does AI still feel like working alone?
Hi everyone 👋
I'm AnitaBest, founder of Flowacts.
Over the past few years, I've been fascinated by one question:
AI models like ChatGPT and Claude are incredibly smart...
So why do we still lose ourselves in long conversations and endless chat history when working on real projects?
And when a team is building together, why does collaboration still mean jumping between AI chats, docs, tasks, and messaging apps instead of working in one shared space?
Those questions eventually led us to build Flowacts.
I'm here to learn from other makers, share what we're building, and connect with people who are exploring the future of AI collaboration.
If this sounds like a challenge you've experienced too, I'd love for you to give Flowacts a try and let me know what you think.
Looking forward to meeting everyone.
Replies
Welcome, and the question in your title is sharper than the usual version of it.
The part I would push on is what a shared space actually stores. I work daily in an agent that keeps a folder of plain text files it rereads at the start of every session, and what fixed the lost thread problem was not more history. It was that the few things worth keeping got written down somewhere separate from the conversation. Chat history grew and helped less. A short file that got edited helped more.
So the question I would want Flowacts to answer is whether a teammate joining on day forty reads the conversation or reads the state.