Skip to main content
Connect Glassray to Slack and your team can report misbehavior, ask questions, and get deviations posted for review - without leaving the channel.

​
Connect your workspace

Open integration settings

In the dashboard, go to Settings → Integrations and find the Slack card.

Connect Slack

Click Connect Slack and authorize the workspace in the popup.

Pick a channel

Choose the channel Glassray should post deviations to. You can send a test message to confirm it’s wired up, then Save Channel.

Invite the bot

Invite the Glassray bot to that channel so it can read threads it’s mentioned in and reply.

​
Choose when you’re notified

Under Settings → Integrations → Slack, the When to notify control sets how early - and for which severities - deviations get posted to your channel:
  • Lifecycle stage - Confirmed only (default: the quieter setting - wait until Glassray confirms a deviation recurs before posting) or Suspected onwards (post as soon as a deviation is first suspected, so you can Confirm it from the card).
  • Minimum severity - post at any severity (default), major & critical, or critical only.
A 🔎 Suspected card tells you Glassray is looking for more examples to confirm it’s a recurring issue, and carries a Confirm button - if it’s a known issue you’re already aware of, confirm it right there. Either way - your confirmation or Glassray’s own investigation finding it recurs - the card updates in place: the pill flips to 🟡 Confirmed and the button becomes Generate fix. Click it and Glassray writes the fix and replies in the thread, including the branch name to use (glassray-dev-142-…) so the pull request links itself to the deviation.

​
Using the bot

Mention @Glassray in the channel and describe a misbehavior - or paste a problem, optionally with a trace link. The bot reads the thread and responds in a single reply.

Finds the evidence

If you reference a trace, the bot verifies it; if you only describe the behavior, it searches your corpus for matching traces and verifies the best match.

Logs a deviation

When you report a real misbehavior, the bot logs it as a 🔎 Suspected deviation from the conversation, attaching the trace it found - a single report isn’t yet confirmed to recur.

Scans to confirm it

After logging it, the bot kicks a deep-search scan for more examples to confirm it’s a recurring issue, and posts the results back to the thread. The card carries a Confirm button if you already know it’s real.

Answers read-only questions

Ask “what do you already know about X?” or “is the scan done?” and it just reads and answers - it creates nothing.
In a deviation’s thread, tell the bot which pull request fixes it:
The bot attaches the PR to that deviation - it shows in the deviation’s Pull requests panel with its live state, and Glassray leaves one comment on the PR linking back. You can also paste a PR URL or owner/repo#123, or name the deviation by its short ID (DEV-142) outside its thread. Linking a PR never changes the deviation’s status. PRs whose branch, title or description carry glassray-dev-142 link on their own - see GitHub.

​
Automatic vs. a click

The bot acts within its toolset on its own when you ask it to log a problem or clearly report one - it logs the deviation as 🔎 Suspected and starts a scan to confirm it recurs, then posts a deviation card to your channel. From that card you can Confirm it (if you already know it’s a real problem - the card then offers Generate fix) or Dismiss it. For read-only questions it never creates anything.
Members of your own workspace get the full toolset; external collaborators connected through Slack get a safe read-and-report subset and can’t trigger broad, metered scans.

​
Security

The Slack agent’s reasoning loop has no direct Slack access - reading the thread and posting the reply are handled by Glassray’s runner, not by the model. The thread is treated as untrusted input: instructions inside it never override the agent’s rules or expand its toolset.