Skip to content

docs(slack): vulnerability checks, the sandbox, code history and shared channels - #111

Draft
zeyu2001 wants to merge 1 commit into
mainfrom
docs/slack-assistant-use-cases
Draft

zeyu2001 wants to merge 1 commit into
mainfrom
docs/slack-assistant-use-cases

Conversation

@zeyu2001

@zeyu2001 zeyu2001 commented Nov 7, 2026 •

Copy link
Copy Markdown
Member

What changed

platform/slack-assistant.mdx documents what the Slack assistant does since HacktronAI/web#1782, #1784, #1785, #1790, #1791 and #1799 (on staging, not yet in a production release):

  • Check a vulnerability against your repositories: a CVE, advisory, package or "this week's" vulnerabilities, checked against every connected repository's dependency manifests and lock files; what the answer contains; the 25-repositories-at-a-time note.
  • Work in a sandbox: attached files, scripts, scanners and proofs of concept, public repositories, web research with sources; no credentials, a host allowlist with one-click approval per thread; connected repositories never leave Hacktron (read-only shell, no network).
  • Ask security questions now says it reads a pull request's changes and a file's history (who changed a line and when), with an example.
  • Follow what it's doing: the 👀 reaction and what the progress card shows.
  • Shared channels: who Hacktron answers in a Slack Connect channel, the guest notice, and that a thread with a guest in it is left alone.
  • Limits: "doesn't build or run your code" is now "doesn't build or run your connected repositories; it runs scripts and tools in its own sandbox".
  • The task table and description gain the two new use cases.

Draft until

The web changes above are on staging only. Merge once they ship in a production release.

HacktronAI/landing has the same changes to its copy of the page and its integrations FAQ (draft PR there).

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only updates to describe Slack assistant behavior; no application code or configuration changes.

Overview
Updates platform/slack-assistant.mdx so Slack assistant docs match new staging capabilities: vulnerability checks across repos, sandbox file/tool work, richer code/PR/history answers, progress UX, and Slack Connect behavior.

The page intro and task table now call out checking CVEs/advisories/packages and analyzing attachments or running tools in a sandbox. Ask security questions explains search, PR diff reads, and line history (with a new example). New sections document vulnerability checks (advisory sources, lockfile/transitive deps, answer shape, 25-repo limit) and Work in a sandbox (capabilities, no creds, host approval, connected repos stay read-only off-network).

Follow what it's doing adds the 👀 reaction and progress-card steps. Shared channels covers who gets answers in Slack Connect, guest connect prompts, and stopping replies in guest-contaminated threads. Limits clarifies sandbox scripts vs not building/running connected repos.

Reviewed by Cursor Bugbot for commit 8e07891. Bugbot is set up for automated code reviews on this repo. Configure here.

…ed channels

The Slack assistant now checks a CVE or package against every connected
repository's manifests and lock files, works in its own sandbox (attached
files, scripts and tools, public repositories, web research behind a host
allowlist), reads a pull request's changes and a file's history, reacts
with eyes, and replies to Slack Connect guests with how to connect.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
hacktronai 🟢 Ready View Preview Nov 7, 2026, 1:15 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

This branch was successfully deployed

1 active deployment
staging — 8e078916 Deployed Nov 7, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant