claude/for
Search
Subscribe
Claude CodeUpdated

Claude Tag Slack search: the "Channels Claude can search" setting

Arthur Teboul
Arthur TeboulEditor, claude/for
UPDATED SEP 30 · 5 MIN

Claude Tag can keyword-search public Slack channels; admins can limit search to channels Claude has joined via “Channels Claude can search” (CHANGELOG 2.1.283). Search vs membership, access checks, and how it differs from MCP --channels and Desktop.

In Claude Tag (Slack), Claude can keyword-search public channels the way a Slack member searches — finding messages without full channel membership. Full history needs /invite @Claude into that channel. Admins can enable “Channels Claude can search” (CHANGELOG 2.1.283) to limit search to public channels Claude has been added to (org / workspace / channel). Ask @Claude what can you access from this channel?. This is not Claude Code’s research-preview MCP Channels (claude --channels), and not Claude Desktop.

TL;DR: Search ≠ full history. Keyword find on public channels is broader than membership; invite Claude to participate. Admin setting “Channels Claude can search” (2.1.283+) can tighten search to channels Claude joined. MCP --channels push plugins and Desktop (claude --desktop) are different products. Checked 2026-09-30.

Search vs membership — what Claude can find

From How Claude Tag works and Get started:

ContextWhat Claude can do
Thread / channel where Claude is presentRead that conversation’s history (session context)
Other public channels Claude is not inKeyword search only (same search a Slack user has) — not a full channel dump
Public channel Claude has been added toWork there; full history where added
Private channels / DMsOnly from inside them
Channel that includes guestsWorkspace search is unavailable from those channels

Finding ≠ acting. To participate in a channel, invite with /invite @Claude. Claude Tag is Team/Enterprise Slack path; Pro/Max still use the earlier Claude in Slack path per Code Slack docs. The docs don't spell out the exact plan floor as of 2026-09-30, so check with your Tag admin before assuming Tag features apply.

Admin setting — “Channels Claude can search” (2.1.283)

CHANGELOG 2.1.283 (anthropics/claude-code):

[Claude Tag] Added a "Channels Claude can search" admin setting that limits Claude's Slack search to public channels it has been added to, set per organization, workspace or channel

Effect: when enabled, Slack keyword search is limited to public channels Claude has been added to. Scope: organization, workspace, or channel. Official docs match: “an admin can limit search to channels Claude is in.”

As of 2026-09-30, Anthropic's docs don't show the exact click-path for this setting, so look for it in your Claude Tag admin settings. CHANGELOG HEAD on check day is 2.1.285 (unrelated additive CLI, Desktop and plugin-configure items). This page covers the 2.1.283 Tag search setting only.

How to check and use search today

  1. Invite for full history: in the channel message box, /invite @Claude (Slack rejects /invite from inside a thread).

  2. Check reach: @Claude what can you access from this channel?

  3. Search: ask Claude to find a known keyword or message across public channels it can search.

  4. Channel replies may show a Configure link (per the getting-started docs).

The Claude moves worth stealing, by email

Workflows tested on real jobs, sent only when they are worth it. Free.

Not these “Channels”

ThingWhat it isThis page?
Claude Tag “Channels Claude can search”Admin limit on Slack workspace keyword searchYes, this guide
Claude Code MCP ChannelsResearch-preview plugins that push Telegram/Discord/iMessage events into a local session via claude --channels (docs)No
Claude Desktop / claude --desktopDesktop product / CLI flagNo, see the Desktop guide
/doctor prompt-auditAudit CLAUDE.md/skills for stale promptsdoctor guide
/skill-doctorSkills context-cost pruneskill-doctor guide
Claude Mods / You should knowPlugins that modify deeper behavior (2.1.287+)Mods guide
Permissions / auto modePermission modespermissions guide
MemoryCLAUDE.md / memorymemory guide

Legacy Claude Code in Slack routing modes are retiring in favor of Claude Tag for Team/Enterprise. This page is Tag search, not the legacy setup guide.

Pitfalls

  • Assuming keyword search = full channel history dump
  • Expecting private-channel search from another channel
  • Confusing Tag with the MCP --channels install steps
  • Expecting claude --desktop to have anything to do with Slack channels
  • Hunting for an admin click-path the official docs don't describe yet

FAQ

Can Claude read a public channel it isn’t in?

Keyword search yes (unless an admin limited search, or the ask comes from a guest-bearing channel where workspace search is unavailable). Full history no until /invite @Claude.

What does “Channels Claude can search” change?

It limits Slack search to public channels Claude has been added to (CHANGELOG 2.1.283; org / workspace / channel scope).

Is this the same as claude --channels?

No. MCP Channels push events into a local Claude Code session. This guide covers Claude Tag Slack search.

Does this work on Pro/Max Claude Tag?

Claude Tag is the Team/Enterprise Slack path; Pro/Max stay on the earlier Claude in Slack path per Slack/Tag docs. Confirm with your admin.

How is this different from /doctor or permissions?

Different tools: prompt-audit, skill-doctor, permissions, memory.

Sources (checked 2026-09-30)

  • CHANGELOG 2.1.283 — “Channels Claude can search” bullet
  • How Claude Tag works — search vs membership, guests, admin limit
  • Get started — /invite @Claude, access check prompt
  • MCP Channels, a different product

The Claude moves worth stealing, by email

Workflows tested on real jobs, sent only when they are worth it. Free.