Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
One change · claude-docs

Troubleshoot Claude Tag in channels and DMs changed

claude-tag/users/troubleshooting

Nearest release: v2.1.268, published 2 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+23added
Lines−19removed
From line 156 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits14to this page, all time

The whole hunk

from line 156, old and new numbered
/
lines
from line 156
156156 
157157* Remove the guests from the channel. In Slack, open **Channel details** → **Members** and filter by "guests"; guests show a **guest** badge on their Slack profile.
158158* Move the conversation to a channel with no guests.
159* Ask a claude.ai organization owner to allow Claude to respond in channels that include guests, and send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels). If you don't know who your organization's owners are, ask whoever set Claude up in your workspace.
159* Ask a claude.ai organization owner to change the guest setting for this channel, and send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels). They can let Claude reply with only the channel's own setup, or with full access. If you don't know who your organization's owners are, ask whoever set Claude up in your workspace.
160160 
161161The guest access setting restores replies, not workspace search. Claude can't search the workspace from a channel that includes guests, even when it's allowed to respond there. Removing the guests or moving the conversation to a channel with no guests restores search as well.
162162 
from line 228
228228 
229229## Claude stopped mid-task
230230 
231The messages in this section mean a session started and then stopped partway through. In most cases the work isn't lost, and the same thread picks up where it stopped. Each entry says whether anything needs redoing.
231The messages in this section mean a session started and then stopped partway through. For most of them the work is still there, and the same thread picks up where it stopped. For a disconnect, work that existed only on the machine running the session can be lost. Each entry says whether anything needs redoing.
232232 
233233### I hit repeated API server errors
234234 
from line 306
306306 
307307**What you see**
308308 
309Claude posts in the thread:
309In the thread, Claude posts a message that begins "I got disconnected partway through and may not have finished" or "I lost my connection". The rest of the message either says that Claude is recovering on its own and how long to wait before mentioning it, or asks you to mention it so it can start again.
310310 
311> I got disconnected partway through and may not have finished. Reconnecting and resuming automatically usually within a few minutes, though a slow recovery can take much longer. Mention me if I don't follow up.
311A disconnect message appears in a thread where you're working with Claude, including a direct-message thread; Claude doesn't post one in a channel it's only watching or from a routine.
312312 
313When Claude reconnects, it edits that message to "I reconnected and I'm carrying on where I left off. No need to mention me." When automatic recovery isn't armed, the message is "I got disconnected partway through and may not have finished. Mention me to pick up where I left off." instead.
313If the machine running the session comes back, Claude removes the disconnect message from the thread, and there's nothing for you to do. If Claude restarts on a fresh machine instead, it edits the disconnect message to:
314314 
315You can see it in a thread where you're working with Claude, including a direct-message thread; Claude doesn't post it in a channel it's only watching or from a routine.
315> I've restarted on a fresh machine. Uncommitted changes from before the restart may not have carried over, so I'll re-check my work before continuing. No need to mention me.
316316 
317317**What it means**
318318 
319The sandbox running this thread's session stopped partway through a turn, so the step Claude was on may not have finished. The thread's conversation is intact.
319The machine running this thread's session, the sandbox Claude works in, stopped partway through a turn, so the step Claude was on may not have finished. The thread's conversation is intact, and so is work Claude pushed to a branch, opened as a pull request, or posted into the thread. Files and drafts that existed only on the machine that stopped may not carry over to a fresh one. The entry [Claude lost work it created earlier](#claude-lost-work-it-created-earlier) describes the same kind of loss.
320320 
321321**How to resolve**
322322 
323Wait for the reconnect message, or mention Claude in the same thread when the message asks you to. Claude resumes there and continues from the conversation; ask it to check on the step it was working on and redo anything that didn't finish. If the same notice comes back, the underlying problem hasn't cleared yet. Wait a few minutes and mention Claude again.
323If the message says how long to wait, wait that long. If Claude hasn't posted in the thread by then, or if the message asks you to mention Claude, mention `@Claude` in the same thread. Claude runs the interrupted step again, so check the files and drafts from before the disconnect and ask Claude to redo anything that's missing.
324324 
325If the message says there's no need to mention Claude, wait for Claude to post in the thread. Claude re-checks its earlier work, then continues.
326 
327If a disconnect message comes back after you mention Claude, the problem hasn't cleared yet. Wait a few minutes, then mention Claude in the thread again.
328 
325329### Something went wrong and I couldn't finish this turn
326330 
327331**What you see**
from line 478
474478 
475479**What it means**
476480 
477Where you message Claude determines which connectors apply. A channel uses only the connections an admin attached to it, and personal connectors never apply there. A DM runs on your own claude.ai account and uses that account's connectors.
481Where you message Claude determines which connectors apply. A channel session uses the connections an admin attached to it. In organizations where [personal connectors in channels](/docs/claude-tag/concepts/personal-connectors) is available, Claude can also use your personal connectors there for your own tasks, after you allow it. A DM runs on your own claude.ai account and uses that account's connectors.
478482 
479483You set up and authenticate connectors on claude.ai under **Customize > Connectors**; Slack has no connector settings of its own. The [settings map](/docs/claude-tag/concepts/settings-map) covers every settings surface.
480484 
481485**How to resolve**
482486 
483For a channel, ask your admin to [add a connection](/docs/claude-tag/admins/add-connections) for the service.
487For a channel, ask your admin to [add a connection](/docs/claude-tag/admins/add-connections) for the service. If [personal connectors in channels](/docs/claude-tag/concepts/personal-connectors) is available to your organization, Claude can also use your personal connectors for your own tasks, after you allow it.
484488 
485489For a DM, work through these in order:
486490