One read of Claude Documentationclaude-docs-20261016T183706Z
4 pages moved out of 277 read.
Pages moved
4
significant first
Pages read
277
in this capture
Captured
18:37 UTC
Corpus hash
a8adc37ed883
corpus-hash
What this read moved
1-4 of 4claude-tag/users/when-claude-responds Changed · +3 / -2 lines
from line 65
6565
6666Claude reads a message that another Slack app or bot posts as channel context, and replies to it only when the message includes `@Claude`. Claude treats alerts an integration posts, messages a Slack workflow posts, and messages from any other bot the same way.
6767
68A bot's `@Claude` at the channel's top level gets a reply in a thread under that message, unless either of these is true:
68A bot's `@Claude` at the channel's top level gets a reply in a thread under that message, unless any of these is true:
6969
7070* The channel's [**Respond automatically**](#turn-automatic-replies-on-or-off) setting is off.
7171* Claude has [stopped reading the channel](#when-claude-stops-reading-a-channel) because of message volume.
72* The channel is a [Slack Connect channel](/docs/claude-tag/admins/restrict-access#when-claude-does-not-answer-in-a-slack-connect-channel), shared with another company. Claude reads what apps, bots, and workflows post there as context but doesn't reply to them.
7273
73A person's mention reaches Claude in both cases.
74A person's mention reaches Claude in each of these cases.
7475
7576Because Claude reads those messages, when a person asks about an alert a bot posted, Claude can answer from it. To have Claude act on what an integration posts, mention it in the channel or in the message's thread. For example, reply to a bot-posted alert with `@Claude triage this`. To have Claude check the channel on a schedule and post what needs attention, set up a [routine](/docs/claude-tag/users/proactivity).
7677
third-party/claude-desktop/extensions Changed · +13 / -0 lines
### Hooks on Windows devices without Git for Windows
from line 392
392392
393393Claude Code [managed settings](/docs/third-party/claude-desktop/code#interaction-with-claude-code%E2%80%99s-own-managed-settings) deployed on the device govern these hooks as they do in the Claude Code CLI: `disableAllHooks` turns them off, and `allowManagedHooksOnly` keeps only the hooks those managed settings define.
394394
395### Hooks on Windows devices without Git for Windows
396
397On a Windows device without Git for Windows, Claude Code runs a [hook](https://code.claude.com/docs/en/hooks) in PowerShell when the hook sets neither `shell` nor `args`. Hooks in Cowork sessions run the same way, on the device itself and not in Cowork's virtual machine. PowerShell rejects some commands that Bash accepts, such as a quoted program path followed by arguments.
398
399A [`PreToolUse`](https://code.claude.com/docs/en/hooks#pretooluse) hook that runs this way and has no `onFailure` field blocks the tool call when it fails or times out. The hook error that Claude receives includes `blocking because Git Bash wasn't found`.
400
401If your Windows devices have hooks, in a plugin or in Claude Code [managed settings](/docs/third-party/claude-desktop/code#interaction-with-claude-code%E2%80%99s-own-managed-settings), make one of these changes:
402
403* **Keep a hook written for Bash**: install Git for Windows in its default location (`C:\Program Files\Git`) on each device, then quit and reopen Claude Desktop
404* **Run the hook without a shell**: write the hook in [exec form](https://code.claude.com/docs/en/hooks#exec-form-and-shell-form), with the program in `command` and its arguments in `args`
405
406After either change, a hook that fails or times out lets the tool call go ahead. To stop the tool call instead, add [`"onFailure": "block"`](https://code.claude.com/docs/en/hooks#block-the-action-when-a-hook-fails) to the hook.
407
395408## User extensions
396409
397410Unless restricted by an admin, end users can add their own extensions through the in-app UI:
third-party/claude-desktop/installation Changed · +4 / -1 lines
from line 16
1616
1717On Windows, Cowork requires the `.msix` package: fleets provisioned with the legacy `.exe` installer get Claude Desktop without Cowork, and migrating them to `.msix` enables it. Cowork also requires working hardware virtualization and, on Windows, the Virtual Machine Platform optional feature. The [readiness check](#check-device-readiness) verifies both along with the requirements above.
1818
19On Windows, Cowork's virtual machine runs under an account in the built-in `NT VIRTUAL MACHINE\Virtual Machines` group, and that group needs the **Log on as a service** user right. If your organization assigns that right through Group Policy or MDM, see [Windows security policy blocks the Cowork workspace](#windows-security-policy-blocks-the-cowork-workspace) before rollout.
19Check these on Windows devices before rollout:
20
21* **Log on as a service**: Cowork's virtual machine runs under an account in the built-in `NT VIRTUAL MACHINE\Virtual Machines` group, and that group needs the **Log on as a service** user right. If your organization assigns that right through Group Policy or MDM, see [Windows security policy blocks the Cowork workspace](#windows-security-policy-blocks-the-cowork-workspace).
22* **Hooks**: a [hook](https://code.claude.com/docs/en/hooks) command written for Bash needs Git for Windows on the device. If your Windows devices have hooks in plugins or in Claude Code managed settings, see [Hooks on Windows devices without Git for Windows](/docs/third-party/claude-desktop/extensions#hooks-on-windows-devices-without-git-for-windows).
2023
2124With [Unified Claude](/docs/third-party/claude-desktop/unified-claude) on, a message sent from the home screen starts a Cowork session on a device that can run Cowork, and a Chat conversation on a device that can't.
2225
claude-tag/admins/restrict-access Changed · +1 / -0 lines
from line 269
269269* **Enterprise Grid organization-level installs.** Claude is installed for your whole Enterprise Grid organization rather than per workspace, and none of your own workspaces hosts the channel.
270270* **Threads from before the channel was shared.** Claude doesn't continue a thread it was already working in before the channel was shared. A mention there gets the notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here," and a new thread works.
271271* **Messages from the other company's Claude.** Claude doesn't reply to the other company's Claude. If the other company also uses Claude, each company's settings decide only whether its own Claude answers.
272* **Messages from other apps, bots, and workflows.** Claude doesn't reply to a message another app, bot, or Slack workflow posts in a Slack Connect channel, even one that mentions `@Claude`. Claude still reads the message as context, so a person who replies to it with `@Claude` gets an answer.
272273
273274### Channels shared across workspaces in your Enterprise Grid
274275