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. Invite @glen to a public channel and its history becomes 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
The app requests three OAuth scopes, all limited to public channels:
channels:readList the workspace's public channelschannels:historyRead messages in public channels Glen has been invited tochannels:joinJoin a public channel when you ask it toDirect messages, group DMs, private channels, and Slack Connect or externally shared channels are outside those scopes, so Glen cannot read them even by accident. Ingestion is public-channel-only by construction, enforced at the API level rather than by configuration.
Installing Glen in your workspace
- 01
Sign in at app.tryglen.com. 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 exactly the three scopes above; 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
Invite Glen to the channels that matter
Type /invite @glen in a public channel. From then on that channel's history feeds your org's memory, and anyone in it can ask questions.
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 shows which channels Glen has joined and disconnects the workspace in one click. Disconnecting stops ingestion immediately.
Privacy
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 founders@tryglen.com, which the founders read.