Kollab

This is huge! Congratulations on the launch

Didn't expect this one to land for me, but it did.The core bet is that the agent should live in Slack or Telegram instead of some separate dashboard you have to open. That's just correct. Most teams aren't lacking AI tools — they're lacking time to go find them when they actually need them.The Skills system is what shifts it from "team chatbot" to something real. One person builds the workflow, everyone reuses it. Luo from HeyForm said it better than I can: no more explaining the same process over and over. One thing I'd love to know: what's running under the hood, model-wise? And is there a path to bringing your own API key? For teams that already have Claude or GPT-4 access through work, that could be a dealbreaker — or a non-issue, depending on how it's built. Also curious about MCP tool limits. ChatGPT caps at 30 tools per connector — what's the ceiling here? With complex workflows pulling from GitHub, Sentry, Slack, and a few others at once, that number matters more than it looks. Upvoted!

I've tried a bunch of AI productivity tools, and most of them feel like single-player experiences. Kollab is the first one that actually makes sense for a team.

I'm not a developer, and that's exactly why Kollab works for me. No terminal, no config files. I just connect my tools, set up what I need, and the agent handles it. Finally an AI tool that doesn't assume everyone can code.

The bots triggering from Slack and syncing back to the workspace is a nice loop, but how about when someone edits the output inside Kollab, does that change reflect back in the Slack thread?

How do you handle agent coordination across workflows? Building an AI scheduling assistant for TV and curious about your approach to chaining agent tasks.

We've been using Kollab internally for a few weeks now. The biggest win for us is Skills — once someone builds a workflow, the whole team can reuse it instantly. No more explaining the same process over and over. Really changes how we share knowledge across the team.

Interesting positioning. Feels less like “another agent tool” and more like an orchestration layer across where work already happens. If teams can actually rely on it for day-to-day ops, this could become pretty sticky.

This feels very practical. Most teams don’t lack tools — they lack something that ties everything together. An agent that sits across channels and actually executes workflows (not just answers) could remove a lot of operational overhead.

Hey 👋 I'm Lynn, one of the makers behind Kollab.Kollab is the AI workspace that actually gets how teams work. 🎯I've been looking for a platform that doesn't just bolt AI onto project management, but truly unifies agents, knowledge, and team collaboration in one place. Kollab nails it.What stands out:One CLI to rule them all — spaces, projects, tasks, skills, bots, timers, MCP servers, memory. Everything is accessible through a single, cleankollab command. No more jumping between ten different tools.Knowledge-base powered — ask questions across your projects and get real answers grounded in your docs, not generic LLM hallucinations.Agent-first by design — timers, bots, and skills aren't afterthoughts. They're first-class citizens you can configure, automate, and deploy.Model flexibility — choose between Lite, Pro, and Max tiers depending on the task, so you're not overpaying for simple queries.For teams building with AI, Kollab feels like the operating system we should have had all along. Clean architecture, real automation, and collaborative by default.Upvoted and excited to see where this goes! 🚀---

Hi Product Hunt! 👋 I'm Gavin, the CEO and founder of Kollab.While building my previous SaaS product (Buildin), I realized a fundamental issue: even with deep AI integration, most tools operate on a "SaaS + AI" logic where AI is merely a helpful sidekick. However, with the rapid rise of Claude Code, MCP, and similar breakthroughs, we are officially entering the Agent era.Yet, the barrier to entry for using Agents at work is still way too high. Terminals, npm installs, MCP configurations, system prompts, memory management... these technical hurdles keep 90% of everyday users out. Even for the tech-savvy who do know how to set them up, their Agent environments remain siloed on local machines, making it incredibly hard to share workflows or best practices across a team.That’s exactly why we built Kollab. We designed Kollab to be the central hub for team-agent collaboration. We focused on three core pillars to make this happen:Zero-Barrier Configuration: We made the complexity of MCPs and coding environments completely invisible. Through our Connectors, you can integrate tools like Notion, GitHub, Figma, Linear, and Slack with just a few clicks, allowing your Agents to seamlessly access and act on your actual business data.The Compounding Power of Team Knowledge: This is what makes Kollab truly special. When any team member creates a new Skill or sets up a workflow, it’s immediately added to your team's shared Skill Marketplace. One person's "aha" moment instantly scales into an organizational capability. No more reinventing the wheel.Work Where Collaboration Already Happens: You shouldn't have to change your habits to use AI. With Kollab, you can deploy your Agents as Bots directly into Slack or Telegram. Just tag them in your chat, and they’ll take instructions and execute long-running automated tasks right alongside your human teammates.Internally, our product, engineering, and ops teams are already sharing over 20 active skills for our daily workflows. We firmly believe that Agents shouldn't just be about boosting individual productivity—they should serve as the central nervous system for team collaboration.We’d love for you to try Kollab and would be incredibly grateful for your honest feedback!👉 https://kollab.im/product

Hey 👋 I'm jiayi, one of the makers behind Kollab.Kollab is an AI-native workspace. Unlike doc tools with AI added on top, Kollab puts Agents front and center. You give them tasks, they execute, and everything stays in a shared workspace your team can actually use.Here's a real example. Our team runs a blog. It used to be all manual: track trends, find topics, write drafts, make images, review. Same grind every week.Now in Kollab:A scheduled task searches target keywords every morning and drops new topic ideas into the workspaceAnother task picks up new topics automatically, writes drafts and generates imagesA review task runs a saved Skill to check tone, structure, and SEOWhen it's done, the Bot sends a message in our channel so the team knows it's ready for final reviewThree scheduled tasks running in the background. Skills defined once, reused every time. We just do the last step: review and publish. What used to take a team days now takes one person a few minutes.No code. No stitching five tools together. Set up a Skill, set a schedule, let Agents do the work.Teamwork, done with Kollab.

Hey PH 👋 YAN here, one of the makers behind Kollab. We built it so our team could stop bouncing between Slack, GitHub, Notion and half a dozen separate agent tools. One agent, sitting across every channel the team already lives in, with any MCP server wired behind it.Here's how we use it ourselves. Kollab's hooked into our Slack and Telegram bots, with Notion MCP and GitHub MCP behind them. Inside our work group, anyone (devs or not) can ping the bot to look at code, review a feature, or file an issue. In the community group, users @Kollab to report bugs or ask how something works, and every message routes through Notion MCP straight onto our backend board. Feedback used to get lost in DMs; now it doesn't.The piece we underestimated most is scheduled tasks. We thought we were shipping a digest job, but a scheduled task on Kollab is really a timed agent. The same cron can call any MCP tool, pull from the knowledge base, run as a specific agent role, and post back to any channel. Ours right now: one drafts a weekly changelog from GitHub issues, one cross-checks our status page against Sentry, one pings the on-call before standup. Same thing under the hood, totally different jobs on top.When we need more than a quick answer, there's AgentCore. Long-running agent with its own filesystem and a browser built in. We've been using it to stand up small demo sites and internal tools instead of writing throwaway scripts. And since skills are just regular GitHub repos, anything the team keeps repeating turns into a skill the whole org can install by name. We're still early on this part, and it's probably where we'll end up finding the weirdest uses.Question for PH: if you had one agent sitting across your team's channels with full MCP reach, what's the first scheduled task or skill you'd write? No idea what people will come up with. So far the answers have been all over the map, and two of them are already in our next release.