Glue

Glue is trying to compete in a harder category than it may appear: team collaboration software. That is a brutal market because users already have Slack, Teams, Discord, email, project boards, and internal docs. So a new entrant only matters if it changes the nature of the work, not just the interface. Glue's core pitch—agentic team chat with goal-oriented threads and shared workflows across humans, tools, and AI—at least points at a real wedge. It is not just “chat, but with AI.” It is trying to make the thread itself the execution surface.

That distinction is important. In a normal chat tool, conversations about work happen in one place and the work itself often happens somewhere else. Glue appears to be designed so a thread can contain discussion, agent actions, tool invocations, and progress toward a goal in one flow. If it works well, that could reduce context switching and make internal operations more traceable. For teams that already coordinate around recurring tasks—incident handling, launch prep, research sprints, onboarding, approvals—this kind of execution-oriented chat could be useful.

The product also appears to lean into MCP-style tool connectivity, which would make it easier to connect agents to external systems without inventing everything from scratch. That raises the ceiling on usefulness, but it also raises the complexity. Collaboration products with embedded agents can quickly become noisy, permission-heavy, or culturally awkward if they are not designed well. The risk is not just technical failure; it is team resistance. People will ignore “agentic” features if they feel like extra ceremony.

Public pricing was not clearly available in accessible sources during this run, and direct product-page fetches were blocked. That is frustrating because collaboration tools are typically bought on seat economics, and unclear pricing slows evaluation. For now, Glue looks more like a product to pilot with a real team workflow than to buy off launch enthusiasm alone.

The best fit is likely a small-to-mid-sized team with recurring process-heavy work and enough comfort with AI to treat chat as a work surface instead of just a messaging layer. It is less compelling if your team already has a heavily customized Slack + project management setup that nobody wants to change. But if your biggest pain is that work disappears across threads, tools, and status meetings, Glue's execution-in-thread idea is worth testing. Just judge it on reduction in coordination overhead, not on how futuristic the demo feels.