Luffy is an AI employee inside Slack that connects to your tools and builds a living memory of your company. With that context, it can answer questions, follow ongoing work, and execute tasks across your apps, so your team can move from conversation to action without leaving Slack or constantly switching between tools
1. Lives and works directly inside Slack
2. Connects to all your workplace tools
3. Remembers your entire workspace and company context
4. Executes tasks across multiple apps
5. Proactively handles reminders, follow-ups, and project tracking
- AI employee inside Slack
- Handling repetitive work across tools
- Company knowledge and workspace search
- Reporting, analysis, and business intelligence
- Proactively tracking projects, sending reminders, and following up on open work
free $1000 worth of credits
Visit deal
AI video with native sound, paid per clip. Nothing stored.
A calmer Mac menu bar, one click away.
Enterprise Software. Intelligent Automation. Global Impact.
Comments
11Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy. nice idea of integrating with slack though
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy. nice idea of integrating with slack though
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy. nice idea of integrating with slack though
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy. nice idea of integrating with slack though
Building @base0.tech & @supatoken.lol
doesit actually work like the onepiece luffy. nice idea of integrating with slack though
The Slack-first approach makes sense for teams that already run most work in channels. One thing I would want to see clearly is how permission boundaries and audit trails work when Luffy executes tasks across connected apps, since that will matter a lot for adoption in ops-heavy teams.
Builder.
helps begin to solve the fragmentation problem of modern workflows!