Glue review

Glue is team chat organized around named, persistent threads rather than channels and a continuous message stream. A thread can hold the conversation and decisions for a piece of work, then be closed when that work is done. The idea is to make active discussions easier to find later, instead of relying on people to remember where something was said.

Teams can mention @Glue or @Cursor in a thread to get AI help. The agents can summarize a conversation, find context or information, draft replies, and generate ideas. Glue also lists Slack history import, so teams can bring existing conversations over rather than start with an empty workspace.

That makes Glue a focused chat product, not just a chatbot layered over an existing channel setup. Its fit depends on whether your team is willing to organize work into persistent threads and use agent mentions as part of that workflow.

Glue’s clearest strength is its organizing model. Named threads give teams a place to keep a specific task or decision, while persistent history means the context is not designed to disappear into a fast-moving stream. Closing finished threads gives work a visible endpoint. Those are useful choices for teams that struggle to retrieve decisions from chat.

The agent features are built into that same thread workflow. Teams can mention @Glue or @Cursor to summarize, find context, draft replies, look up information, or generate ideas without leaving the discussion, according to the product description. Slack import also gives teams a way to carry over existing conversations.

The entry price is relatively clear: the pricing page lists up to five users free, then $6 per user per month for Startup. That plan includes up to five groups, unlimited threads and message history, unlimited apps and webhooks, and unlimited external users. For a small team that needs persistent chat and does not need more than five groups, the published Startup limits are easy to assess before switching.

The main trade-off is the structure itself. Glue is built around named threads instead of channels and an ongoing chat stream. Teams that rely on channel-based conversation may need to change how they organize work; the product description does not say whether Glue supports a channel-style alternative.

Startup also caps teams at five groups, even though it includes unlimited threads. That distinction matters if your team separates work into many groups. The pricing page lists Business as adding unlimited groups, multiple admins, premium AI models, and data imports up to 100mb, but it does not publish a Business price. Enterprise pricing is also not published; its listed additions include unlimited data imports, SAML and SCIM capabilities, priority support, and white-glove onboarding.

The page lists a 30-day free trial and says annual billing is not published. We also do not have published AI usage limits or details on how Slack import handles data beyond the Business cap. Check those points, and the higher-tier price, before treating the $6 Startup figure as the cost of a broader rollout.

Glue lists Startup at $6 per user per month after the first five users, who are free. Startup includes up to five groups, unlimited threads and message history, apps and webhooks, and external users. The pricing details also list a 30-day free trial, but don’t explain how it relates to the free users.

The step up to Business adds unlimited groups, multiple admins, premium AI models and data imports up to 100MB. Enterprise adds unlimited data imports, SAML and SCIM, priority support and white-glove onboarding. The catch: neither tier has a published price, so we can’t calculate the cost jump from Startup or compare the higher plans. Extra users are listed at $6 each per month after the five free users. Annual billing prices aren’t published either. If your team needs more than five groups, premium models or enterprise controls, ask Glue for a quote before budgeting.

Glue lists Slack history import as a feature, which gives teams a route to bring existing conversations over. The published pricing details set Business imports at up to 100MB and Enterprise imports as unlimited; they don’t specify what the Slack import preserves or whether it has other limits. Confirm the import scope before treating it as a complete archive migration.

The bigger change is organizational: Glue centers work on named, persistent threads rather than channel-based chat. Teams moving from Slack should decide how they’ll structure threads and whether that suits their work. Mentions for @Glue and @Cursor bring agents into discussions, but the published material doesn’t describe a data-export option or an exit process. That makes portability worth checking before you move important work in. We weren’t given Reddit posts or comments about Glue, so we can’t substantiate what tends to make users leave; ask about export and retention directly.