GLEN FOR SLACK
Ask your org's memory in the channel where the question came up.
Glen, shared memory for AI agents, keeps what your team's agents and people learn as they work. Decisions still get asked about twice, though, because the person who knows is offline or gone. The Slack app closes that gap: mention @glen and it answers in the thread, from what the org already knows.
Maya Chen 9:14 AM
@glen why is the checkout retry cap 3? Stripe's docs suggest 5 and I can't find the decision anywhere.
Glen APP 9:14 AM
The cap dropped from 5 to 3 on May 12, after retries amplified the Stripe rate-limit incident (INC-214). Nadia's agent recorded the decision: hold at 3 until idempotency keys ship. Both observations are linked in the dashboard.
answered from org memory · 2 observations
How a mention becomes an answer
- 01
You mention @glen
Slack delivers the mention to Glen over the Events API. Every request is verified against the app's signing secret before anything else happens.
- 02
Glen recalls
The question runs through the same recall pipeline as the dashboard's ask assistant, an LLM pass over the observations your org's agents and people have accumulated.
- 03
The answer lands in the thread
Glen replies under the original message, so the question, the answer, and the discussion that follows stay attached to each other.
Channels work in the other direction too. The channels Glen reads become part of org memory, so a decision made in Slack is recallable by every agent your org runs, not only by whoever scrolled past it.
What Glen reads, exactly
Public channels
If the person connecting Slack lets Glen use their access, Glen reads the workspace's public channels without joining them. Otherwise it reads only the public channels @glen has been added to.
Private channels, only when invited
Glen reads a private channel only after someone in it invites @glen. It never adds itself to one.
Not direct messages
Glen doesn't read DMs or group DMs. Anything sent to it directly is ignored.
Not shared or archived channels
Channels shared with another organization (Slack Connect) and archived channels are skipped.
Names and emails
Glen reads members' names and email addresses so each message is credited to the person who wrote it and linked to their Glen account. It never emails anyone it finds in Slack.
Wipe memories & disconnect on the Slack integration page permanently deletes everything Glen took from Slack and revokes its access.
Installing Glen in your workspace
- 01
Sign in at app.tryglen.com. Glen accounts are by invitation for now: if your team isn't on Glen yet, use Get access at the top of this page. The Slack connection belongs to your Glen organization, so you install it from the dashboard rather than from a bare button on this page.
- 02
Open Settings → Integrations and choose Slack.
- 03
Click Add to Slack. Slack shows its consent screen listing the permissions Glen asks for; some workspaces route this through admin approval first.
- 04
Approve, and Slack sends you back to Glen. The integrations page confirms the workspace is connected and shows the two first steps: invite @glen to a channel, then mention it.
After you install
Add @glen where people will ask it things
Type /invite @glen in a channel so people there can mention it. Inviting it to a private channel is also how that channel's history joins your org's memory.
Ask something the org already answered
Mention @glen with a real question, a past decision, an incident, a customer detail. The first useful answer is the fastest way to show the team what it's for.
Manage it from the dashboard
The same integrations page disconnects the workspace in one click, and Wipe memories & disconnect deletes everything Glen took from Slack.
Privacy and support
What the Slack integration stores, how long Glen keeps it, and how to have it deleted are covered in the Glen privacy policy. For anything the policy doesn't answer, write to support@tryglen.com. Stuck on something? The support page has what to include.