Skip to main content
Once your workspace is connected, Neo can be used directly inside Slack for fast, collaborative security work.

​
Where You Can Use Neo

Neo works in two main modes:
  • Direct messages for focused one-on-one interaction with Neo
  • Channels and threads for team-visible investigations and follow-up
In channels, threading matters. Neo keeps work scoped to a thread so the conversation, task status, and final summary stay in one place.

​
DMs vs Channels

​
DMs

DMs are the simplest way to work with Neo:
  • no mention is required
  • the conversation is naturally scoped
  • ideal for focused recon, research, and exploratory work

​
Channels

In channels, Neo is best used when the task belongs in a team conversation:
  • in public and private channels Neo only responds when explicitly mentioned with @Neo — plain channel messages are ignored even if the bot is in the channel
  • in group DMs (multi-person DMs) Neo also requires an @Neo mention to act
  • keep follow-up in the same thread
  • share findings where the rest of the team can see them
If Neo is disabled for a channel, users are guided toward admin settings or a DM instead.

​
Starting A Task

Slack works well for instructions such as:
  • “Run a full recon on example.com and look for exposed admin endpoints.”
  • “Review this code path for auth bypass or IDOR risk.”
  • “Research this CVE and tell me whether it is relevant to our stack.”
  • “Summarize the likely impact of this finding and what to check next.”
Neo can also work from attached files when the request needs more context.

​
Attachments And Files

When you attach files to your Slack request, Neo can use them as part of the task context. Good examples include:
  • logs
  • text summaries
  • code snippets
  • reports
  • exported findings or evidence files
For larger or more detailed outputs, Neo can return a concise Slack summary while attaching result files back into the thread.

​
What Results Look Like

Neo is designed to keep Slack readable:
  • it posts concise summaries in-thread
  • it highlights the key outcome instead of dumping raw output
  • it attaches files when the detailed output belongs outside the message body
  • it links the work back to Neo for deeper follow-up
Neo posting a Slack channel summary of a weekly security audit with attached JSON and Markdown reports

​
While Neo works

Neo adds an eyes reaction to your message within a few seconds of picking it up. Messages Neo does not act on, such as commands, get no reaction. While the task runs, Slack shows a grey status line under your message with a short tip, such as “Tip: Reply in this thread to steer me”. The tip changes each time you ask Neo something. For longer tasks, Neo posts one live checklist in the thread and edits it as steps move from pending to in progress to done. If the task is stopped or fails, unfinished steps are marked as not completed. Each final reply ends with a small model footer naming the model that handled it.

​
Commands

Mention Neo with a command to control it without starting a new task: A ! in the middle of a message is not a command, so “what does !help mean?” runs as a normal request.

​
Channel memory

Ask Neo to remember a standing rule for a channel, such as “@Neo remember for this channel: always include CVSS scores”, and it applies the rule to every future task there. Ask “@Neo what do you remember about this channel?” to see the current rules. Remembered rules are saved as the channel’s custom instructions, so workspace admins can review or edit them in Neo Settings.

​
Canvases and lists

Neo can create and manage Slack canvases and Slack Lists when you ask, for example “Create a canvas tab in this channel titled Recon notes with a summary of the findings”, “Add a Next steps section to that canvas”, or “Create a Slack List called Findings with columns Title, Severity, Status and add these items”. Canvases and Lists that Neo creates are shared with the channel you asked from, so everyone there can open them. Slack Lists require a paid Slack plan.

​
Task Visibility Is Team-Specific

Work started from Slack is not treated as a private task owned only by the person who sent the message.
  • each Slack workspace is connected to a specific Neo team
  • tasks created from Slack are stored in that Neo team context
  • visibility inside Neo follows the connected team’s access model
  • DMs keep the Slack conversation focused, but the resulting Neo task is still team-scoped

​
Continue In Neo

Slack is the fast front door, not the only surface. If the task becomes more complex, Neo continues to be available in the full Neo UI for:
  • full execution context
  • complete artifacts
  • longer follow-up tasks
  • reviewable task history

​
Stop or mute with reactions

If Neo is still working on a request, you can abort the running task directly from the Slack thread by reacting with any of these (or send @Neo !stop):
Reaction-based abort is useful when:
  • the task is no longer needed
  • the target or scope changed
  • you realize the prompt needs to be corrected
  • you want to stop long-running work before it finishes
What to expect:
  • only a currently running Slack task is affected
  • Neo confirms the abort request in the thread
  • unrelated reactions do not stop work
To stop Neo from replying in a thread at all, react with a thumbs-down on any message in it. Neo stops any running task, mutes the thread, and says so in the thread. Mention @Neo in that thread to bring it back.
If your workspace installed Neo before reaction-based abort shipped, reinstall or reconnect the app after the permissions update so the latest event subscription and scopes are active.

​
Example Prompts

Try prompts like these:
  • “Run a full recon on acme.com and summarize exposed services and likely risk areas.”
  • “Review this API design for authentication and authorization gaps.”
  • “Research CVE-2026-XXXX and tell me whether it matters for our environment.”
  • “Look through this attached report and summarize the issues worth validating first.”
  • “Continue the investigation from above and tell me what you would test next.”

​
Next