One read of Claude Documentationclaude-docs-20261001T170712Z
2 pages moved out of 259 read.
Pages moved
2
significant first
Pages read
259
in this capture
Captured
17:07 UTC
Corpus hash
befe499e3a2b
corpus-hash
What this read moved
1-2 of 2government/desktop/plugins Changed · +1 / -1 lines
from line 14
1414* If your administrators let you add your own plugins, you can upload a plugin file or ask Claude to create a plugin with you.
1515* If your administrators let you add plugin marketplaces, you can add a marketplace and install plugins from it.
1616
17Claude for Government does not include a public plugin marketplace; your administrators add your organization's plugins. Your deployment's network controls determine whether a marketplace you add can be downloaded.
17Claude for Government does not include a public plugin marketplace; your administrators add your organization's plugins. Whether a marketplace you add can be downloaded depends on your agency's network and on the settings your administrators choose.
1818
1919## Find and install plugins
2020
government/security/security-and-data-handling Changed · +1 / -1 lines
from line 24
2424 </Accordion>
2525
2626 <Accordion title="How are attached folders made available to the sandbox?">
27 When a user attaches a local folder to a Cowork session, the entire folder is made available to that session's sandbox as a filesystem mount, so changes Claude makes are written directly to the folder on disk. A mapped network drive on Windows is an exception: Claude's host-side file tools can read, write, and search it, but shell commands in the sandbox cannot reach network shares, so a task that runs a script or build against those files must copy them to a local folder first (see [Desktop and filesystem access](/docs/third-party/claude-desktop/local-access#network-drives-on-windows)). Files the user attaches individually to a conversation are copied or hard-linked into a per-conversation uploads directory and mounted read-only; where the filesystem hard-links, edits to the original file while the conversation is open can be visible to it. The allowed-folders setting is a policy control enforced by the desktop application. See [Desktop and filesystem access](/docs/third-party/claude-desktop/local-access).
27 When a user attaches a local folder to a Cowork session, the entire folder is made available to that session's sandbox as a filesystem mount, so changes Claude makes are written directly to the folder on disk. A mapped network drive on Windows is an exception: Claude's host-side file tools can read, write, and search it, but shell commands in the sandbox can reach it only if the drive was mapped and reachable when the sandbox started (see [Network drives on Windows](/docs/third-party/claude-desktop/local-access#network-drives-on-windows)). Files the user attaches individually to a conversation are copied or hard-linked into a per-conversation uploads directory and mounted read-only; where the filesystem hard-links, edits to the original file while the conversation is open can be visible to it. The allowed-folders setting is a policy control enforced by the desktop application. See [Desktop and filesystem access](/docs/third-party/claude-desktop/local-access).
2828 </Accordion>
2929
3030 <Accordion title="Which file types need the sandbox in Chat?">