One read of Claude Documentationclaude-docs-20260928T230705Z
2 pages moved out of 255 read.
Pages moved
2
significant first
Pages read
255
in this capture
Captured
23:07 UTC
Corpus hash
d3309973f0f2
corpus-hash
What this read moved
1-2 of 2claude-tag/admins/connections/datadog Changed · +12 / -10 lines
from line 20
2020
2121## Add the connection to a bundle
2222
23In the bundle, click **Connect** next to Datadog. The picker has three Datadog entries, one per site. Pick the one that matches your Datadog account's site.
23In the bundle, click **Connect** next to Datadog. The picker has one Datadog entry per Datadog site. Datadog has a separate API host per site, and a key only works against its own, so pick the entry that matches your Datadog account's site.
2424
25| Picker entry | Site |
25| Picker entry | Site and API host |
2626| :- | :- |
27| **Datadog** | US1 (`api.datadoghq.com`), the default site |
28| **Datadog (US5)** | US5 (`api.us5.datadoghq.com`) |
29| **Datadog (EU)** | EU (`api.datadoghq.eu`) |
27| **Datadog** | US1, `api.datadoghq.com`, Datadog's default site |
28| **Datadog (US3)** | US3, `api.us3.datadoghq.com` |
29| **Datadog (US5)** | US5, `api.us5.datadoghq.com` |
30| **Datadog (EU)** | EU, `api.datadoghq.eu` |
31| **Datadog (AP1)** | AP1, `api.ap1.datadoghq.com` |
32| **Datadog (AP2)** | AP2, `api.ap2.datadoghq.com` |
33| **Datadog (US1-FED)** | US1-FED, `api.ddog-gov.com` |
3034
31The form asks for the same fields in all three.
35The form asks for the same fields in every entry.
3236
3337| Field | Value |
3438| :- | :- |
3539| Claude's API key | The API key from Datadog |
3640| Claude's application key | The Application key from Datadog. Optional in the form; add it so Claude can read metrics, monitors, and dashboards |
37| Allowed websites | Prefilled by the preset; override for other sites (see below) |
41| Allowed websites | Prefilled with the entry's API host |
3842
39Datadog has a separate API host per site, and a key only works against its own. If your account is on a site without a picker entry, pick any Datadog entry and override the **Allowed websites** field with your site's API host: `api.us3.datadoghq.com`, `api.ap1.datadoghq.com`, or `api.ddog-gov.com`. To change the host later, open the **⋮** menu on this connection in the bundle's Credentials tab and choose **Edit**.
40
41If you override the **Allowed websites** field, replace the prefilled host with your site's API host rather than adding yours alongside it, so that **Test connection** checks your host instead of the prefilled one. You can save the connection even if the test fails, and the credential is sent only to the hosts in **Allowed websites**.
43The connection is created with path prefixes that cover Datadog's read and query routes: metric, log, trace, and RUM queries, monitors, downtimes, dashboards, SLOs, notebooks, events, hosts, service definitions, and incident search. It doesn't cover Datadog's key, user, integration, or log-configuration management routes, so Claude can't call those through it. To narrow the connection further, for example to `GET` only, or to allow another route, select **Edit** on the connection's row; see [Restrict by path or method](/docs/claude-tag/admins/add-connections#restrict-by-path-or-method).
4244
4345The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See [how Agent Proxy works](/docs/claude-tag/concepts/agent-identity#agent-proxy).
4446
cowork/guide/plugins Changed · +18 / -23 lines
## Related ## Next steps
from line 2
22
33> Add packaged skills, connectors, and agents to Cowork from the plugin marketplace or a file.
44
5A plugin is a package that extends what Claude can do in Cowork. Installing one can add skills, MCP connectors, subagents, commands, or hooks in a single step. Plugins come from the marketplace, from your organization, or from a file you upload.
5A plugin is a package that extends what Claude can do in Cowork. Installing one can add skills, MCP connectors, subagents, slash commands, or hooks in a single step. Plugins come from the marketplace, from your organization, or from a file you upload.
66
7A plugin you install is saved to your account, so its skills and connectors are also available in chat and in Claude Code. [Plugins](/docs/plugins/overview) covers what each surface loads; this page covers the Cowork side.
7Plugins are available in Cowork and Code. They aren't used in Chat.
88
9To get started, [install a plugin](#install-a-plugin) from **Customize**, or [add a Git repository as a marketplace](#use-a-git-repository-as-a-marketplace) to share plugins without publishing them.
10
119## What a plugin can contain
1210
13A plugin can contain any combination of the following components.
11A plugin's manifest declares any combination of the following.
1412
1513| Component | What it adds |
1614| - | - |
from line 21
2321
2422## Install a plugin
2523
26You browse, install, and upload plugins from the **Plugins** page. Open **Customize** in the sidebar, then select **Plugins**.
24Open **Customize** in the sidebar, then **Plugins**.
2725
2826<Steps>
2927 <Step title="Browse the marketplace">
30 Select **Discover** to see available plugins. The default marketplace is
31 Anthropic's official catalog; you can add other marketplaces by URL.
28 Select **Browse plugins** to see available plugins. The default marketplace
29 is Anthropic's official catalog; you can add other marketplaces by URL.
3230 </Step>
3331
3432 <Step title="Install">
35 Select a plugin and click **Install**. Installing doesn't add or sign you in
36 to any connector. If the plugin includes connectors, open its **Connectors**
37 tab afterward to add or connect each one.
33 Select a plugin and click **Install**. If the plugin includes a connector
34 that needs authentication, you're prompted to sign in.
3835 </Step>
3936
4037 <Step title="Review components">
4138 Open the installed plugin to see its skills, connectors, agents, and hooks.
42 Select **Disable plugin** to turn the whole plugin off, and connect or
43 disconnect each connector on its own from the **Connectors** tab.
39 Enable or disable individual components as needed.
4440 </Step>
4541</Steps>
4642
from line 44
4844
4945## Use a Git repository as a marketplace
5046
51A Git repository that contains plugin packages can serve as a marketplace, which lets you share plugins without publishing to the public catalog. For a marketplace you add yourself, repositories on GitHub, including GitHub Enterprise, are supported, and public repositories on GitLab and Bitbucket also work. To distribute plugins to everyone in a Team or Enterprise organization, an Owner syncs the repository from organization settings instead, as [Manage plugins for your organization](/docs/plugins/admin#add-your-own-plugins) describes.
47A Git repository that contains plugin packages can serve as a marketplace. This is the typical way teams distribute their own plugins without publishing to the public catalog. Repositories on GitHub (including GitHub Enterprise) are supported; public repositories on GitLab and Bitbucket also work.
5248
5349<Steps>
5450 <Step title="Add the repository">
from line 59
6359 </Step>
6460</Steps>
6561
66Select **Check for updates** on a marketplace to pull the latest plugins from its repository, or turn on **Sync automatically**.
62Click **Update** on a marketplace to pull the latest plugins from its repository.
6763
68For marketplaces your organization manages, see [Manage plugins for your organization](/docs/plugins/admin), or [MCP, plugins, skills, and hooks](/docs/cowork/3p/extensions) if your organization deploys Claude Desktop with its own model provider.
64For administrator-managed marketplaces, see [MCP, plugins, skills, and hooks](/docs/cowork/3p/extensions) in the deployment guide.
6965
7066## Limits
7167
from line 81
8581
8682On Team and Enterprise plans, administrators can require certain plugins for everyone in the organization. Required plugins install automatically and show **This plugin is required by your organization**; you can't remove them.
8783
88For how administrators provision plugins, see [Manage plugins for your organization](/docs/plugins/admin).
84For how administrators provision plugins, see [MCP, plugins, skills, and hooks](/docs/cowork/3p/extensions) in the deployment guide.
8985
9086## Update and remove plugins
9187
9288Cowork checks for plugin updates from the marketplace they came from. If you've edited a plugin's files locally, Cowork detects the change and warns you before an update would overwrite it.
9389
94To remove a plugin you installed, open it under **Customize > Plugins** and select **Remove**. You can't remove a plugin marked **This plugin is required by your organization**.
90To remove a plugin you installed, open it under **Customize → Plugins** and click **Uninstall**. Organization-managed plugins can only be removed by an administrator.
9591
96## Next steps
92## Related
9793
98* [Plugins](/docs/plugins/overview): how plugins work across Claude products
99* [Manage plugins for your organization](/docs/plugins/admin): administrator provisioning on Team and Enterprise plans
100* [Submit a plugin](/docs/plugins/submit): publish your own to the marketplace
101* [MCP, plugins, skills, and hooks](/docs/third-party/claude-desktop/extensions): for organizations that deploy Claude Desktop with their own model provider
94* [Plugins overview](/docs/plugins/overview) for how plugins work across Claude products
95* [Submit a plugin](/docs/plugins/submit) to publish your own to the marketplace
96* [MCP, plugins, skills, and hooks](/docs/cowork/3p/extensions) for administrator provisioning
10297