diff --git a/content/.metadata.json b/content/.metadata.json
index 5bafc0ba7..10ada6aac 100644
--- a/content/.metadata.json
+++ b/content/.metadata.json
@@ -1,7 +1,7 @@
{
"metadata": {
"version": "2.0",
- "fetch_date": "2026-08-18T16:17:29.055877Z",
+ "fetch_date": "2026-08-19T02:10:19.967249Z",
"section": "all"
},
"items": [
@@ -9,15 +9,15 @@
"url": "https://platform.claude.com/docs/en/home",
"status": "success",
"path": "en/home.md",
- "sha256": "5afa0fe29b5cfcfec1e91bd4143c51b03a3c96e06170c7dd0e43e05ea5232864",
- "size": 11959
+ "sha256": "8246dc49fade25c067beaff3b2ec2503633db98279d57d7674a91fb464dd6589",
+ "size": 11967
},
{
"url": "https://platform.claude.com/docs/en/intro",
"status": "success",
"path": "en/intro.md",
- "sha256": "00adef941caa9156cff4e2d58bc5996fe772e6fd60ec9521e7737e69ebfcf2b6",
- "size": 5263
+ "sha256": "318b7cbe5bafaa902c6552b4f253779cb7ec0e793bdf37315f682d230a354b2e",
+ "size": 5264
},
{
"url": "https://platform.claude.com/docs/en/get-api-key",
@@ -422,8 +422,8 @@
"url": "https://platform.claude.com/docs/en/build-with-claude/files",
"status": "success",
"path": "en/build-with-claude/files.md",
- "sha256": "9b6c30d55f11737692784d5bf287021cbff08ed7102a21a2ba3950391968a970",
- "size": 32138
+ "sha256": "9cb3e722238635102bd70c5006d3c5d362a60022d1718e59d89c4bd7dde2c8b6",
+ "size": 33565
},
{
"url": "https://platform.claude.com/docs/en/build-with-claude/pdf-support",
@@ -436,8 +436,8 @@
"url": "https://platform.claude.com/docs/en/build-with-claude/vision",
"status": "success",
"path": "en/build-with-claude/vision.md",
- "sha256": "3242a01766ed71074007d71652ebd7dc426feb8fa417e0c66f56b7f87da38d26",
- "size": 46303
+ "sha256": "a7ec458bd897341ac6fc6dcd9601108665a8ea1e4825155060b2e0202c7fe523",
+ "size": 46300
},
{
"url": "https://platform.claude.com/docs/en/build-with-claude/vision-coordinates",
@@ -450,8 +450,8 @@
"url": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview",
"status": "success",
"path": "en/agents-and-tools/agent-skills/overview.md",
- "sha256": "4f7b241829ad6a1358475dfc59e33de0669f7d0b00e634acd2da66c3c6e9b321",
- "size": 21150
+ "sha256": "f3a9e69a05e4d41157561ced529eb795dc420d99103faf2a3488d364f5eacf03",
+ "size": 21652
},
{
"url": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/quickstart",
@@ -471,15 +471,15 @@
"url": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/enterprise",
"status": "success",
"path": "en/agents-and-tools/agent-skills/enterprise.md",
- "sha256": "de38cb2a0a0e4fd777a979be4604da73f93052bb29132f763beb79a0e1840190",
- "size": 14415
+ "sha256": "7a83e80ce335ab329ed9f1c674fa3747b3b0d46656c9de6835932cc168976e36",
+ "size": 16293
},
{
"url": "https://platform.claude.com/docs/en/build-with-claude/skills-guide",
"status": "success",
"path": "en/build-with-claude/skills-guide.md",
- "sha256": "71451b5bc3e2193c5673fb70c0380002900a142ddd5393fd2a1f750f3292e797",
- "size": 155789
+ "sha256": "85af315e980fe974e2f85d403db4099a5aee51a1fb0d902dd468cb4c42d5bb49",
+ "size": 157714
},
{
"url": "https://platform.claude.com/docs/en/agents-and-tools/remote-mcp-servers",
@@ -786,8 +786,8 @@
"url": "https://platform.claude.com/docs/en/manage-claude/admin-api",
"status": "success",
"path": "en/manage-claude/admin-api.md",
- "sha256": "b4216b894f51d048e8bcffcdcce4f1903fe2a81a27b5e0ddb355eb0d8507704b",
- "size": 15185
+ "sha256": "fccb182841bede8aa232ccf9024076ce87bf2e65847e699fc161c96f6d3be274",
+ "size": 15192
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/user-management",
@@ -800,7 +800,7 @@
"url": "https://platform.claude.com/docs/en/manage-claude/workspaces",
"status": "success",
"path": "en/manage-claude/workspaces.md",
- "sha256": "e1f397520ca9cc8b38d6eaffdb563dcf2bfc7d060fb61f694489ca7315ac346a",
+ "sha256": "9b61b914684f5527578e853fe2c758900a3f134a43cd039abbbe57a92a11306c",
"size": 25136
},
{
@@ -835,64 +835,64 @@
"url": "https://platform.claude.com/docs/en/manage-claude/wif-reference",
"status": "success",
"path": "en/manage-claude/wif-reference.md",
- "sha256": "82cf57edfd0814fda032accb4a96823810065b04dbc0d3764f1f3ae51366473e",
- "size": 41361
+ "sha256": "031e6df9331540529e06322e9c08e11f383dcb756ce7a4da0883ed7a5897dd64",
+ "size": 43128
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/wif-providers/aws",
"status": "success",
"path": "en/manage-claude/wif-providers/aws.md",
- "sha256": "47da9f49b1a51f6cdadd15926c4047bd1688dc9750ec3e71c58bebde81cc6aad",
- "size": 31928
+ "sha256": "9c097b02cadeff891d46fda2a9a43d637df60fc30e06bb2c17423c911dc54db1",
+ "size": 32388
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/wif-providers/gcp",
"status": "success",
"path": "en/manage-claude/wif-providers/gcp.md",
- "sha256": "71db33dd700a240642145a90d5fc1b5a30ff36528464e5f5111b975f13787f64",
- "size": 20052
+ "sha256": "5c104d2f5bb7f6bbd30606196c878ee8156bd422525f64fb87af274da72a5f36",
+ "size": 20282
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/wif-providers/azure",
"status": "success",
"path": "en/manage-claude/wif-providers/azure.md",
- "sha256": "e5e7a668224dcf78d074734509d69136e9f41e683dadfbbd78230efb6d6b9a09",
- "size": 64211
+ "sha256": "2c6cf9d6a7a7dc3e05755c700ef2c39dfd3c7079206e0b2b51e59873fad3727e",
+ "size": 64832
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/wif-providers/github-actions",
"status": "success",
"path": "en/manage-claude/wif-providers/github-actions.md",
- "sha256": "1d973a9502305754e7b76c98d77a810616f7e216f7279fa30caa993a922b23ea",
- "size": 14072
+ "sha256": "0013cf9776f628177eb67ee7c1999fbe581715ed76b3078b38b6c7fe630e62e9",
+ "size": 14448
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/wif-providers/kubernetes",
"status": "success",
"path": "en/manage-claude/wif-providers/kubernetes.md",
- "sha256": "1b09145c5dd71808f3ef4dc29592a2be5fdc76dfca67a60ec7e1bf3de7060480",
- "size": 14123
+ "sha256": "8b13fb2a457db389eab5e11bbd9879b50735bf7d8f54de0e556b554c90b1beed",
+ "size": 14353
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/wif-providers/spiffe",
"status": "success",
"path": "en/manage-claude/wif-providers/spiffe.md",
- "sha256": "dfb6c4b3d0555a4e34f8c2ad724be79f5d5a5a47ec51082dbd100fb7387eb517",
- "size": 30231
+ "sha256": "055df84499a3fed79aaac796e16518eda93a2ce3d7c48a9f92270dbd1b7cdd94",
+ "size": 30461
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/wif-providers/okta",
"status": "success",
"path": "en/manage-claude/wif-providers/okta.md",
- "sha256": "7fb8615a272c5627b5965f9ca26de879ff2fe418d036a7a6f1193ac24170bed7",
- "size": 21681
+ "sha256": "2106555740d19f1f1327662d6f9553363c51191758fbc078f919a32e1339897c",
+ "size": 21911
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/usage-cost-api",
"status": "success",
"path": "en/manage-claude/usage-cost-api.md",
- "sha256": "6d96289f57699196bfdd08ec549aae8d1c8333fbf05664260c224431b66ccd31",
- "size": 15853
+ "sha256": "a27a6eb355e359ae5cecb139fdf8cb6d2af064fc0f2edc47c02c29090dffaf62",
+ "size": 15905
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/rate-limits-api",
@@ -933,43 +933,43 @@
"url": "https://platform.claude.com/docs/en/manage-claude/api-and-data-retention",
"status": "success",
"path": "en/manage-claude/api-and-data-retention.md",
- "sha256": "c8aadd7a40cf0b37ca54f0c0ed256733f0144c2e5615f637b32a1841372db15f",
- "size": 55734
+ "sha256": "9981daf66c4b75639235c980cf4e81cba75fa6eb8634d522ef8180e6aed19916",
+ "size": 55704
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/access-transparency",
"status": "success",
"path": "en/manage-claude/access-transparency.md",
- "sha256": "6dc76a63c3312f5c0929f88392f46a2fc698b34befcb3c1f57a2685070ff8684",
+ "sha256": "00946afb5c4c2d853b0bc44f25284ffd410e81e9b0ebafd13fe6c5322eabf8ee",
"size": 20648
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/cmek",
"status": "success",
"path": "en/manage-claude/cmek.md",
- "sha256": "628f113fa8be874ef68f86acc1b44d377bad3e35cdc9eced302c6e8ae43138f5",
- "size": 14177
+ "sha256": "cbcfd2c05b5cdb02c859584f1ea9ac12c4cabe25477ec5ffb01fcbb511aee3e4",
+ "size": 14599
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/cmek-aws-kms",
"status": "success",
"path": "en/manage-claude/cmek-aws-kms.md",
- "sha256": "d108e77a5c0b474f5bc84187d967481ba32eac9174ebf80adde2c5bccd82894b",
- "size": 12661
+ "sha256": "ac2ebe33e1776000f0ea58c2adb499c200576866cf6a8720e85141552da8ced4",
+ "size": 12938
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/cmek-google-cloud-kms",
"status": "success",
"path": "en/manage-claude/cmek-google-cloud-kms.md",
- "sha256": "4a37f583dd12626f751fe441f806132e1251d7242cb8cad4867edf47033d4548",
- "size": 10376
+ "sha256": "e9286ec4fa8a20b2bf2853a0b349031185c09a5b20f58db51ac533a221e3e35b",
+ "size": 10653
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/cmek-azure-key-vault",
"status": "success",
"path": "en/manage-claude/cmek-azure-key-vault.md",
- "sha256": "d4daf34cb610b7e2c57373baa7fe50bcbfc5fb13a0331c5d2f2f2da3a9d2e871",
- "size": 12535
+ "sha256": "4e7feb68773ee3d6b0daa0d618cbed212ffbc057d73f4eebec9aaac4fc2a32b9",
+ "size": 12709
},
{
"url": "https://platform.claude.com/docs/en/manage-claude/inference-hooks",
@@ -1374,8 +1374,8 @@
"url": "https://platform.claude.com/docs/en/api/overview",
"status": "success",
"path": "en/api/overview.md",
- "sha256": "4ea0935af9f2cf7048a21031fff3be7bb5391396aa849443003f9f45f1e31c7b",
- "size": 19768
+ "sha256": "9e285167b30b1c0e5cf57150130aade624d74ee0aa8a9057360447be3ab86456",
+ "size": 19765
},
{
"url": "https://platform.claude.com/docs/en/api/beta-headers",
@@ -1451,8 +1451,8 @@
"url": "https://platform.claude.com/docs/en/release-notes/overview",
"status": "success",
"path": "en/release-notes/overview.md",
- "sha256": "4eebb61915c3db72b2735385190393b5194e43f60fa17562e14494a16dea67ea",
- "size": 87047
+ "sha256": "b37e0bd3d987a2e6c4e6be8b364086961e297b7893d64602de82ec5754885f14",
+ "size": 87622
},
{
"url": "https://platform.claude.com/docs/en/api/completions",
@@ -3978,15 +3978,15 @@
"url": "https://code.claude.com/docs/en/quickstart",
"status": "success",
"path": "en/docs/claude-code/quickstart.md",
- "sha256": "760ac8c65123e97c7a0716a2f2c4f4c26573b2c93c48c5c7ee8224fc44551f58",
- "size": 15795
+ "sha256": "f5b59b2f5b7186ab5fec800beacc45413c103c3e19b2c1292c00838b7d7c0c8d",
+ "size": 13325
},
{
"url": "https://code.claude.com/docs/en/changelog",
"status": "success",
"path": "en/docs/claude-code/changelog.md",
- "sha256": "07d3c964061e482a67b2803b26b62a6308aa84b9e61f6e60a943512a5df299f9",
- "size": 551496
+ "sha256": "055628a3225c59b1be4ea8fa99f76cedf5cea25023681f069ea17c94239eafa5",
+ "size": 554295
},
{
"url": "https://code.claude.com/docs/en/how-claude-code-works",
@@ -4258,8 +4258,8 @@
"url": "https://code.claude.com/docs/en/sub-agents",
"status": "success",
"path": "en/docs/claude-code/sub-agents.md",
- "sha256": "1926157b3db4755951c70d3d3a8cd74d5d3a564389120c7cab2491bde83bb246",
- "size": 101052
+ "sha256": "227626bc5018367896b25c3ecc241964adf11bacd050644f6576cb64e9226dd4",
+ "size": 101302
},
{
"url": "https://code.claude.com/docs/en/agent-view",
@@ -4279,8 +4279,8 @@
"url": "https://code.claude.com/docs/en/cross-session-messaging",
"status": "success",
"path": "en/docs/claude-code/cross-session-messaging.md",
- "sha256": "256b5079ec301ec1bad917f32d05baedc42498883014c8446a1ddc3f33f82d41",
- "size": 29480
+ "sha256": "4906354c778df040a93eb79efa13356f6540a4ecf9241e3e3aa919ea06ba7712",
+ "size": 29886
},
{
"url": "https://code.claude.com/docs/en/workflows",
@@ -4307,15 +4307,15 @@
"url": "https://code.claude.com/docs/en/mcp",
"status": "success",
"path": "en/docs/claude-code/mcp.md",
- "sha256": "0d95df9a1639543f7043c1f42f1ef30491ce05b7075473cef331699940fda2d5",
- "size": 84882
+ "sha256": "66ee91eed4f14dbf5fa9171ac90b47ceacb6fad70a1454e2df4f4fe451eda145",
+ "size": 88493
},
{
"url": "https://code.claude.com/docs/en/skills",
"status": "success",
"path": "en/docs/claude-code/skills.md",
- "sha256": "a6951e76716c9cf8f74f664aa635888ec6e0ee3ceecdb272b2f41f7b37a8b117",
- "size": 96929
+ "sha256": "448fde484cc410c84d871ccffe9c8676f6a5e5fd8ff8330183ef2461fed43575",
+ "size": 96949
},
{
"url": "https://code.claude.com/docs/en/discover-plugins",
@@ -4405,15 +4405,15 @@
"url": "https://code.claude.com/docs/en/debug-your-config",
"status": "success",
"path": "en/docs/claude-code/debug-your-config.md",
- "sha256": "5abeca159091d0d2c090f1105e33549cb367723f242e5568f1d2efaed8f87ef7",
- "size": 23355
+ "sha256": "698a9d85c621d33ca55741de4fd7692646700c35d2c00d69e3845c0771ed5419",
+ "size": 22961
},
{
"url": "https://code.claude.com/docs/en/errors",
"status": "success",
"path": "en/docs/claude-code/errors.md",
- "sha256": "1dcf5f650f977f17f1c677ec4f917769083d0bb671fef30a9b1152735ea22be0",
- "size": 238239
+ "sha256": "01b42e3801011b257a4bae207d3ddecac7df09b07ae48de631a534a58663eb07",
+ "size": 244892
},
{
"url": "https://code.claude.com/docs/en/admin-setup",
@@ -4685,8 +4685,8 @@
"url": "https://code.claude.com/docs/en/settings",
"status": "success",
"path": "en/docs/claude-code/settings.md",
- "sha256": "ea7dbd4d12ee9f4f38175025a82c07d1eae6e9b407fc046bf821cee6c1894965",
- "size": 335349
+ "sha256": "c93f165ff64a6fcd372b3479095a870cd7ea87eefaa8190b648af7fd1516cc9f",
+ "size": 336721
},
{
"url": "https://code.claude.com/docs/en/permissions",
@@ -4769,8 +4769,8 @@
"url": "https://code.claude.com/docs/en/model-config",
"status": "success",
"path": "en/docs/claude-code/model-config.md",
- "sha256": "1492ee54df64707ae3c8732b52a56a4dc3186673567a171c4a3e79fb28d0cfdd",
- "size": 93978
+ "sha256": "f1f8199299e10a5481ad693fcc149e3f241a4dbc0165cc7b8c08bd025af1bf19",
+ "size": 93973
},
{
"url": "https://code.claude.com/docs/en/fast-mode",
@@ -4825,8 +4825,8 @@
"url": "https://code.claude.com/docs/en/statusline",
"status": "success",
"path": "en/docs/claude-code/statusline.md",
- "sha256": "67f836556ddc69bd6505672fe5a65f227f73f4c48316fe96d424261d677ad128",
- "size": 70551
+ "sha256": "546fbc9424f28d62b3c55972b3fd1c8b61b9cb0b442b280928bebf3b1ea01114",
+ "size": 70460
},
{
"url": "https://code.claude.com/docs/en/keybindings",
@@ -4853,8 +4853,8 @@
"url": "https://code.claude.com/docs/en/env-vars",
"status": "success",
"path": "en/docs/claude-code/env-vars.md",
- "sha256": "983e39e18207ab3a2474d435a0221e1f105ee13a5ec61b0663e2e445405219a4",
- "size": 406192
+ "sha256": "7d6edb2858cc214ae4d0290cf7e4d3a5c487a441543345144ac606067ef04f79",
+ "size": 406197
},
{
"url": "https://code.claude.com/docs/en/tools-reference",
@@ -4867,8 +4867,8 @@
"url": "https://code.claude.com/docs/en/interactive-mode",
"status": "success",
"path": "en/docs/claude-code/interactive-mode.md",
- "sha256": "cbcebbd31e5ccf676ee71cda7ac57c1e0c573f91bc4f5516e5f4579798b86734",
- "size": 60952
+ "sha256": "a7a9ca4ac5efa44ed7167ba70d5983b52350607371bc684caccd74a856bca750",
+ "size": 66886
},
{
"url": "https://code.claude.com/docs/en/checkpointing",
@@ -4909,8 +4909,8 @@
"url": "https://code.claude.com/docs/en/agent-sdk/overview",
"status": "success",
"path": "en/docs/claude-code/agent-sdk/overview.md",
- "sha256": "a443e0c70e5b1c98998f6836a2a06ef17f310fb90dbd8e4c3f96b4179d4207bb",
- "size": 9069
+ "sha256": "584a1641997bce448e6675b614c418d73b97087234419ab5227693b3dc89f9ff",
+ "size": 9299
},
{
"url": "https://code.claude.com/docs/en/agent-sdk/quickstart",
@@ -4937,8 +4937,8 @@
"url": "https://code.claude.com/docs/en/agent-sdk/agent-loop",
"status": "success",
"path": "en/docs/claude-code/agent-sdk/agent-loop.md",
- "sha256": "a270ce0539dd5fbb7c31221ab45cf5f6bf1e1da07e9edc54f8c169c4b15747f3",
- "size": 48601
+ "sha256": "8c998e19a93f78b6df2bc32f1d2d6a766d9aeee49aa7f861f02fcf998d960b17",
+ "size": 48604
},
{
"url": "https://code.claude.com/docs/en/agent-sdk/claude-code-features",
@@ -5014,8 +5014,8 @@
"url": "https://code.claude.com/docs/en/agent-sdk/subagents",
"status": "success",
"path": "en/docs/claude-code/agent-sdk/subagents.md",
- "sha256": "e08018409381c1e4e25f81d5a39055381c43731b199b21c049d66c782e94a5b0",
- "size": 44725
+ "sha256": "e7ae552b855784ee1522cb120c1da039675be617edbdcbcf4a60bfc1f2f84d67",
+ "size": 45275
},
{
"url": "https://code.claude.com/docs/en/agent-sdk/modifying-system-prompts",
@@ -5024,26 +5024,19 @@
"sha256": "5f15c1496afbdeed5092b9ea3d68d877b20ea90091381d8139f1680648f1300c",
"size": 22480
},
- {
- "url": "https://code.claude.com/docs/en/agent-sdk/slash-commands",
- "status": "success",
- "path": "en/docs/claude-code/agent-sdk/slash-commands.md",
- "sha256": "e5c597afe5e5ef0370896a12d51f01e32f80f23697c1d99b8bd2e7b5a463b810",
- "size": 19248
- },
{
"url": "https://code.claude.com/docs/en/agent-sdk/skills",
"status": "success",
"path": "en/docs/claude-code/agent-sdk/skills.md",
- "sha256": "978ecbb28fbfc4dc7aed5380f99c42a108bd5bff652cf98e59ed4566c625cc3a",
- "size": 13974
+ "sha256": "400bb4b2c7af65d6bef64799f614a22fe8ff915ec06f1c31711b4be0d62aa9ee",
+ "size": 26661
},
{
"url": "https://code.claude.com/docs/en/agent-sdk/plugins",
"status": "success",
"path": "en/docs/claude-code/agent-sdk/plugins.md",
- "sha256": "26994bfcc00f70c3a5065b891902032b679d6752a3ad0d889b6214f9e1ecc20a",
- "size": 12029
+ "sha256": "c8b179ee93ae6f4ee0a7b01b688153988c893a1cbca544859adea71097d296c0",
+ "size": 12053
},
{
"url": "https://code.claude.com/docs/en/agent-sdk/permissions",
@@ -7751,8 +7744,8 @@
"url": "https://support.claude.com/en/articles/8114491-get-started-with-claude",
"status": "success",
"path": "support/8114491-get-started-with-claude.md",
- "sha256": "72d80a94d10c3cbf7711b88e62474619ca5238470a9b0750e30e3e6b419bfc44",
- "size": 5298
+ "sha256": "fb498ba8472d6c01232c7f422c4767adb805c87d66a90beef4e2987ad1c34d1e",
+ "size": 5302
},
{
"url": "https://support.claude.com/en/articles/8114494-how-up-to-date-is-claude-s-training-data",
@@ -7765,8 +7758,8 @@
"url": "https://support.claude.com/en/articles/8114513-business-associate-agreements-baa-for-commercial-customers",
"status": "success",
"path": "support/8114513-business-associate-agreements-baa-for-commercial-customers.md",
- "sha256": "d5c07e016771ef4adc59b335bc61d9c5e1a24f4aa225eebbf58373ec791ee7e7",
- "size": 23435
+ "sha256": "643be28a4da79c89d76fe4bd690bbca391d0f5f57ee065878febb33567c01449",
+ "size": 23424
},
{
"url": "https://support.claude.com/en/articles/8114518-claude-s-response-to-my-prompt-is-too-brief",
@@ -7779,8 +7772,8 @@
"url": "https://support.claude.com/en/articles/8114521-how-can-i-access-the-claude-api",
"status": "success",
"path": "support/8114521-how-can-i-access-the-claude-api.md",
- "sha256": "6f54abdea6e360f3b565cc0fa2512b479af1951711e3a6fda565e247bbbef314",
- "size": 823
+ "sha256": "9501e160692302bbadcb175db0f16f3e6688c033bacca56016be88aba3fb708a",
+ "size": 824
},
{
"url": "https://support.claude.com/en/articles/8114523-how-can-i-learn-more-about-claude-api-pricing",
@@ -7807,8 +7800,8 @@
"url": "https://support.claude.com/en/articles/8114531-i-created-a-claude-console-organization-how-do-i-start-using-the-claude-api",
"status": "success",
"path": "support/8114531-i-created-a-claude-console-organization-how-do-i-start-using-the-claude-api.md",
- "sha256": "97bb9be78321d7294579fe9ea95091080729b5551e3245586de589b224fd5646",
- "size": 736
+ "sha256": "c5249b0123e6fc11c09cbd464c2c1a2948bc253f6d042108a062c51d31331896",
+ "size": 741
},
{
"url": "https://support.claude.com/en/articles/8114533-i-ve-been-using-other-large-language-models-llms-to-power-my-product-how-should-i-alter-my-prompts-when-switching-to-claude",
@@ -7835,8 +7828,8 @@
"url": "https://support.claude.com/en/articles/8230524-delete-or-rename-a-conversation",
"status": "success",
"path": "support/8230524-delete-or-rename-a-conversation.md",
- "sha256": "3747132f7f383dedab75a85cd8925dd2efd320134f98fb3f112fa9aa29b60584",
- "size": 5879
+ "sha256": "2d8411189f83df3ec4707137ef451cf94420735d4e23f6a97e0406e41de06efe",
+ "size": 5881
},
{
"url": "https://support.claude.com/en/articles/8241126-upload-files-to-claude",
@@ -7905,8 +7898,8 @@
"url": "https://support.claude.com/en/articles/8325618-paid-plan-billing-faqs",
"status": "success",
"path": "support/8325618-paid-plan-billing-faqs.md",
- "sha256": "7a2f1c2ab63cde2663584234114cbaf1dde127b040e755502c974144f5504888",
- "size": 4553
+ "sha256": "e503224c7bddf434fed43c67d8ae75262d0c368f529b5edf6e6efaf58de4fb5a",
+ "size": 4551
},
{
"url": "https://support.claude.com/en/articles/8325621-i-would-like-to-input-sensitive-data-into-my-chats-with-claude-who-can-view-my-conversations",
@@ -7947,8 +7940,8 @@
"url": "https://support.claude.com/en/articles/8606378-how-do-i-use-the-workbench",
"status": "success",
"path": "support/8606378-how-do-i-use-the-workbench.md",
- "sha256": "583a156946e67c2d656e524ffbb5b6199623d175903a0319663dace26d56aa13",
- "size": 9649
+ "sha256": "1bc975804c6d5c0458bdc2450c3c7e09655e27113081a3e36015b1123a8d5884",
+ "size": 5575
},
{
"url": "https://support.claude.com/en/articles/8606394-how-large-is-the-context-window-on-paid-claude-plans",
@@ -7968,8 +7961,8 @@
"url": "https://support.claude.com/en/articles/8887527-customizing-your-appearance-settings",
"status": "success",
"path": "support/8887527-customizing-your-appearance-settings.md",
- "sha256": "e27dc85ff7632528296624f392046fbb67d9a0db8a3057ab92cd2137d549ab4f",
- "size": 1874
+ "sha256": "3c3617dbf9dd2a642b0f0b1bf748d1749ff56c58f3e72aba2efba36b01ee9ea1",
+ "size": 1872
},
{
"url": "https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler",
@@ -7982,8 +7975,8 @@
"url": "https://support.claude.com/en/articles/8977456-how-do-i-pay-for-my-claude-api-usage",
"status": "success",
"path": "support/8977456-how-do-i-pay-for-my-claude-api-usage.md",
- "sha256": "dbd2b8645c0a6e0205afd2f441b086facbc85422a1381e80fc4b88429cec643c",
- "size": 2451
+ "sha256": "d1f65a5cf002aa149a1a8c9fc198f3e932470442faf738ba320fe7fcdbf57f68",
+ "size": 2466
},
{
"url": "https://support.claude.com/en/articles/8987200-can-i-use-the-claude-api-for-individual-use",
@@ -8024,8 +8017,8 @@
"url": "https://support.claude.com/en/articles/9028421-how-can-i-delete-my-claude-account",
"status": "success",
"path": "support/9028421-how-can-i-delete-my-claude-account.md",
- "sha256": "0b54d55ed932415f2e08e61e19f62e9c053ee18635cedb54614c835ba5890a7b",
- "size": 2017
+ "sha256": "9fe41eeaa626bc20e60a9b00115f473085e753f579cf3eab6decc00c5b17f017",
+ "size": 2019
},
{
"url": "https://support.claude.com/en/articles/9035075-law-enforcement-requests",
@@ -8094,8 +8087,8 @@
"url": "https://support.claude.com/en/articles/9266767-what-is-the-team-plan",
"status": "success",
"path": "support/9266767-what-is-the-team-plan.md",
- "sha256": "912c2b8145da230a80174ac8eac3c852d305f1a553e039f1e9d08ae96283f3ee",
- "size": 6097
+ "sha256": "c8658f1196fb6f59014b96f5a593e46c4c019eff5ce38cf2c3478a1d64766af1",
+ "size": 6016
},
{
"url": "https://support.claude.com/en/articles/9267247-get-started-with-the-team-plan",
@@ -8192,15 +8185,15 @@
"url": "https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects",
"status": "success",
"path": "support/9519177-how-can-i-create-and-manage-projects.md",
- "sha256": "60aaa61d1e16b252d590c7dc719120ab18ba47d5f06762787e3fb09ea9a9d3e1",
- "size": 9272
+ "sha256": "9003e428c0efb4714537fa1354048412dc53ff37816f55e33ed3fd0ff50e3820",
+ "size": 9282
},
{
"url": "https://support.claude.com/en/articles/9519189-manage-project-visibility-and-sharing",
"status": "success",
"path": "support/9519189-manage-project-visibility-and-sharing.md",
- "sha256": "65307713c69adf43ac8cf88f9f01211f753042fbf4842a369dfe85eb2906791e",
- "size": 8567
+ "sha256": "86c4a5b96b73f7c37e2739ca340d245159552638a9ee3580a2d4fde053e33914",
+ "size": 8557
},
{
"url": "https://support.claude.com/en/articles/9519291-what-is-anthropic-s-policy-for-handling-governmental-requests-for-user-information",
@@ -8220,15 +8213,15 @@
"url": "https://support.claude.com/en/articles/9534590-cost-and-usage-reporting-in-the-claude-console",
"status": "success",
"path": "support/9534590-cost-and-usage-reporting-in-the-claude-console.md",
- "sha256": "0ca44563fb0543186530e1fd82c998d9a331a1683b9481dedeffa85ec1bd8f31",
- "size": 5102
+ "sha256": "949d8fd3e2afdc3de064b4419032b7d42dbc4b38b43bd0110571d42fd0411588",
+ "size": 5098
},
{
"url": "https://support.claude.com/en/articles/9547008-publish-and-share-artifacts",
"status": "success",
"path": "support/9547008-publish-and-share-artifacts.md",
- "sha256": "856f4614f4df7106935a44645e0f07d98117ce42ae8c6c26400e7c375d077f4f",
- "size": 7324
+ "sha256": "d2ba597a2f03393869385117be0456fc1f8c571cd05a4fda2ff5015c349e87bf",
+ "size": 7326
},
{
"url": "https://support.claude.com/en/articles/9612887-install-claude-for-android",
@@ -8304,7 +8297,7 @@
"url": "https://support.claude.com/en/articles/9927533-disable-public-projects-for-your-organization",
"status": "success",
"path": "support/9927533-disable-public-projects-for-your-organization.md",
- "sha256": "c5d6fca20ae3b5c90a3a398c2aa01386b1963ebcdef4a306216463c60f9ac3b6",
+ "sha256": "25e5c5a2172eeec1aca6ca9b0e161fcc914f99fad03973334246dd0a3cf17539",
"size": 2578
},
{
@@ -8395,8 +8388,8 @@
"url": "https://support.claude.com/en/articles/10186004-claude-console-roles-and-permissions",
"status": "success",
"path": "support/10186004-claude-console-roles-and-permissions.md",
- "sha256": "53eb1c5092b3383153908324dbf3f7ce153cdd3396187746e3248cf1a02eaa87",
- "size": 2214
+ "sha256": "6a6e573aa74bd5836ffce0bd787be065b9efcbb2df0814ea0559d277dbc18c63",
+ "size": 2239
},
{
"url": "https://support.claude.com/en/articles/10263469-use-claude-app-intents-shortcuts-and-widgets-on-ios",
@@ -8444,15 +8437,15 @@
"url": "https://support.claude.com/en/articles/10310342-how-do-i-log-out-of-all-active-sessions",
"status": "success",
"path": "support/10310342-how-do-i-log-out-of-all-active-sessions.md",
- "sha256": "2e4aa140f25d644cf7bef18b3f95e4ed80d7868339945404b2abf56a29f264aa",
- "size": 2494
+ "sha256": "eaeb6fd7503149224b19305da9f2a4c975623864cef4a447f68970c5c111fa72",
+ "size": 2498
},
{
"url": "https://support.claude.com/en/articles/10366376-how-can-i-delete-my-claude-console-account",
"status": "success",
"path": "support/10366376-how-can-i-delete-my-claude-console-account.md",
- "sha256": "6e8e987d6e3751ba7a24aad40779e9344038da8fa5224eaf16df1610071efbc9",
- "size": 3171
+ "sha256": "fa673a80c2861481e4f2566b9fb3466da7aebbcfc66d00078f5f55d05ae95b09",
+ "size": 3163
},
{
"url": "https://support.claude.com/en/articles/10366389-how-can-i-get-higher-rate-limits-on-the-claude-api",
@@ -8500,14 +8493,14 @@
"url": "https://support.claude.com/en/articles/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans",
"status": "success",
"path": "support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md",
- "sha256": "12c80f8e63d63b85e731d47df6c3ba682716659d9a1ce9edeb3fc81c92634034",
- "size": 1034
+ "sha256": "36777ccba6a60fd5c2098f61c5ad9327ef121e7f0e2b71147ee9eb3b5a44fc10",
+ "size": 1036
},
{
"url": "https://support.claude.com/en/articles/10504853-manage-user-feedback-settings-on-claude-console",
"status": "success",
"path": "support/10504853-manage-user-feedback-settings-on-claude-console.md",
- "sha256": "1f5dcfcac33e7f21407c7ac908f6d478fac4d95b509fa39ffb5f6b614ba56ccf",
+ "sha256": "7dcb8e7519cb1be69152fba1ceb6c07a6df13ddc3b809ff231b29cdab7951026",
"size": 997
},
{
@@ -8521,15 +8514,15 @@
"url": "https://support.claude.com/en/articles/10593882-share-and-unshare-chats",
"status": "success",
"path": "support/10593882-share-and-unshare-chats.md",
- "sha256": "d75322521b89028d5f2f5c214f94bd3e527d38042d27970713e6e2ed58f415d4",
- "size": 4014
+ "sha256": "58519e6822b34b07576126a159e7965e3ce89cb60830c1fea10dcf2e142b5b8c",
+ "size": 4012
},
{
"url": "https://support.claude.com/en/articles/10684626-enable-and-use-web-search",
"status": "success",
"path": "support/10684626-enable-and-use-web-search.md",
- "sha256": "07041b7278fa02847c6f5cd962b256933f30a44e7ddb7b75eab6d134c6e86406",
- "size": 6368
+ "sha256": "524ed45b52cb94d2e11d9b4b701c3ed713b34adcd16902c711939fc91992ff41",
+ "size": 6370
},
{
"url": "https://support.claude.com/en/articles/10684638-report-block-and-remove-content-from-claude",
@@ -8538,13 +8531,6 @@
"sha256": "7b76d501ac6a24f255ff0c4f7b77d732acacbea231d014d6b3102c58568ed03e",
"size": 6745
},
- {
- "url": "https://support.claude.com/en/articles/10722177-sharing-prompts-in-the-claude-console",
- "status": "success",
- "path": "support/10722177-sharing-prompts-in-the-claude-console.md",
- "sha256": "a5bb537ef1a4cb9f17dd0fa72a42913a72680588a15ef2d0430438746d9373a1",
- "size": 4527
- },
{
"url": "https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language",
"status": "success",
@@ -8556,8 +8542,8 @@
"url": "https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop",
"status": "success",
"path": "support/10949351-getting-started-with-local-mcp-servers-on-claude-desktop.md",
- "sha256": "1dc6878b0d9a686a32e06084da7758c3fc461d7158cbaf71e84b1d9e4ec44894",
- "size": 8269
+ "sha256": "ba11b0b1f6cd4b20bafbc011a45d868a6f14825e03cb8ecd9072208564e4e3d5",
+ "size": 8271
},
{
"url": "https://support.claude.com/en/articles/11049741-what-is-the-max-plan",
@@ -8598,8 +8584,8 @@
"url": "https://support.claude.com/en/articles/11101966-use-voice-mode",
"status": "success",
"path": "support/11101966-use-voice-mode.md",
- "sha256": "f0d1b8d812f28519d40b47523969d1ce4e79e50986c7e3f68689e862001c6df6",
- "size": 10558
+ "sha256": "7d84f64d095fa9872527f151b554dbdbc794db2812e0ff7a51e659ead825f8f8",
+ "size": 10554
},
{
"url": "https://support.claude.com/en/articles/11107691-why-is-a-coupon-or-promotion-not-available-for-my-account",
@@ -8731,7 +8717,7 @@
"url": "https://support.claude.com/en/articles/11725453-set-up-the-claude-lti-in-canvas-by-instructure",
"status": "success",
"path": "support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md",
- "sha256": "a6b2bf8b8f57a5cc3eced15671b0f150f723574ee73cb85cffe1adce5fa5f63f",
+ "sha256": "83f6e24121d706c6db99fd166a3b915442194a1857b3db2a0ac8d735314dc2e6",
"size": 2750
},
{
@@ -8745,14 +8731,14 @@
"url": "https://support.claude.com/en/articles/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context",
"status": "success",
"path": "support/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context.md",
- "sha256": "04e43087cf8e1288532aeb4869f857dadc5e7a4ce0406df1ffce610d171aa0a2",
- "size": 21526
+ "sha256": "3df0f7a5bbda42ecc5bb99bb6b60675c336d423d59e27d43a0b6cfd3ae2055fe",
+ "size": 21524
},
{
"url": "https://support.claude.com/en/articles/11818288-why-am-i-being-asked-to-verify-my-payment-method",
"status": "success",
"path": "support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md",
- "sha256": "c38828821b199856f5be1f812af157c5f1d50f893c7c4abe04d1f1c278dbaca4",
+ "sha256": "2c25802651821be3bcd3237f9163b64f3867796172d52fdbdc479550966aeacb",
"size": 816
},
{
@@ -8787,7 +8773,7 @@
"url": "https://support.claude.com/en/articles/11869629-use-claude-with-android-apps",
"status": "success",
"path": "support/11869629-use-claude-with-android-apps.md",
- "sha256": "d9d632ec0a24d1f01ddce4e4835fb0810807dca5682598c6a26f1b1956e19f84",
+ "sha256": "09c8c694e2d8a45ef83c50929065353c0b9d7a1372b451b40a3b37c961aff702",
"size": 13879
},
{
@@ -8822,14 +8808,14 @@
"url": "https://support.claude.com/en/articles/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans",
"status": "success",
"path": "support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md",
- "sha256": "171302b89f7d69e4e7187a8f509ee008f68a0d9d07f679332c1222c7208a6794",
- "size": 9640
+ "sha256": "6438074ffc93b86b8ab8f85c2b292d93bc2e65ce4239e49e9e77261ddbd257f7",
+ "size": 9636
},
{
"url": "https://support.claude.com/en/articles/12012173-get-started-with-claude-in-chrome",
"status": "success",
"path": "support/12012173-get-started-with-claude-in-chrome.md",
- "sha256": "460ef496cbb4ea1f54d55aa314ca1f4808814bfff339314087ef6f1e6ea75d58",
+ "sha256": "4805c598e89f39be126d36129f99330b7e27f14b68146ec0a0112dbd4e433cc5",
"size": 14331
},
{
@@ -8843,8 +8829,8 @@
"url": "https://support.claude.com/en/articles/12083917-change-your-team-plan-from-monthly-to-annual-billing",
"status": "success",
"path": "support/12083917-change-your-team-plan-from-monthly-to-annual-billing.md",
- "sha256": "9d80f76481dd9d73ecd2403dd6d6875352af02675e4061dfdc09198f81088727",
- "size": 1398
+ "sha256": "2094b7a54c0fa60a742a754df4676b90f5e389a3eb7c94b36b94ec256679f984",
+ "size": 1400
},
{
"url": "https://support.claude.com/en/articles/12109679-creating-a-new-account-after-deletion",
@@ -8857,8 +8843,8 @@
"url": "https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude",
"status": "success",
"path": "support/12111783-create-and-edit-files-with-claude.md",
- "sha256": "3989ce97dc1978f9ba44057a2cde64b85d48e48640c89a14719083133bb41303",
- "size": 17956
+ "sha256": "57e4bcfd74e3e0c1fc76e12e4a8c8b0e79d328bfdec02dae65e8e7a955a3393e",
+ "size": 17958
},
{
"url": "https://support.claude.com/en/articles/12119250-model-safety-bug-bounty-program",
@@ -8885,22 +8871,22 @@
"url": "https://support.claude.com/en/articles/12157520-claude-code-usage-analytics",
"status": "success",
"path": "support/12157520-claude-code-usage-analytics.md",
- "sha256": "643241832908edbb214df4f442e7fdd1ee9f03a89d1efaf23354ffee0042d5b4",
+ "sha256": "6640fd4474877f3f0d33e40c589cfe2b331f4c0dae767aaf36e482e5254648d4",
"size": 6427
},
{
"url": "https://support.claude.com/en/articles/12260368-use-incognito-chats",
"status": "success",
"path": "support/12260368-use-incognito-chats.md",
- "sha256": "f11bfa748646ceea6614b9e0290edfc6938c8ffb620e1725adbc4181c717955e",
- "size": 3598
+ "sha256": "38dcf7f6ade25965c4b3ff5ccc236b1f23a691c5b3907b32ef8f3e205f6cef8b",
+ "size": 3594
},
{
"url": "https://support.claude.com/en/articles/12293051-use-claude-in-xcode",
"status": "success",
"path": "support/12293051-use-claude-in-xcode.md",
- "sha256": "eba783156c06fa64589002aa511506dae0002dd4559fcb279ab58f6245a6c30a",
- "size": 1907
+ "sha256": "0dcbd01a393a4443b1f086e9d26de6ec0b1f53e2b8df18194b0665c6a502d8ce",
+ "size": 1909
},
{
"url": "https://support.claude.com/en/articles/12304248-manage-api-key-environment-variables-in-claude-code",
@@ -8941,15 +8927,15 @@
"url": "https://support.claude.com/en/articles/12429409-manage-usage-credits-for-paid-claude-plans",
"status": "success",
"path": "support/12429409-manage-usage-credits-for-paid-claude-plans.md",
- "sha256": "933d6935ae691d325eb384efd4722f3caae785a4f62e17ed4780b62f3584c93b",
- "size": 6410
+ "sha256": "9fe424c421ee19b45f6e6babdea6105048b17a1faabf361f6eed9bfa960a46e0",
+ "size": 6416
},
{
"url": "https://support.claude.com/en/articles/12466728-troubleshoot-claude-error-messages",
"status": "success",
"path": "support/12466728-troubleshoot-claude-error-messages.md",
- "sha256": "1b30dff1c3517b2d4d02232d7bcdaba5c48294619849a1eaa05f0888007a1030",
- "size": 4236
+ "sha256": "21eead0e966b5ec3246f97c72c2bfa3d5de5bb1f2528675b7b1724dd58e84d2f",
+ "size": 4234
},
{
"url": "https://support.claude.com/en/articles/12489464-use-enterprise-search",
@@ -8969,8 +8955,8 @@
"url": "https://support.claude.com/en/articles/12512180-use-skills-in-claude",
"status": "success",
"path": "support/12512180-use-skills-in-claude.md",
- "sha256": "826484144ae478cfc41b26cc527f09660cbc254d7ef0c6b6aef840bc41d6c644",
- "size": 14427
+ "sha256": "df586406737ae24c055e8e5f949abaf0efc19542a4ab79a63a731592cd8330ff",
+ "size": 14429
},
{
"url": "https://support.claude.com/en/articles/12512198-how-to-create-custom-skills",
@@ -8990,8 +8976,8 @@
"url": "https://support.claude.com/en/articles/12592343-enabling-and-using-the-desktop-extension-allowlist",
"status": "success",
"path": "support/12592343-enabling-and-using-the-desktop-extension-allowlist.md",
- "sha256": "3b0aacd5a8f47f7604cb2529e1d25a61613e41a55d6c9af6b1db66454a50ba66",
- "size": 5708
+ "sha256": "a9d092c8caa38686fb331d30dd62eb62eb71b1c6713df5e9e1bfab001a033e9c",
+ "size": 5720
},
{
"url": "https://support.claude.com/en/articles/12611117-deploy-claude-desktop-for-macos",
@@ -9004,7 +8990,7 @@
"url": "https://support.claude.com/en/articles/12618689-claude-code-on-the-web",
"status": "success",
"path": "support/12618689-claude-code-on-the-web.md",
- "sha256": "7f2c826e6d0dc300219f2fdf12d09470fe3f5c1f1c0c56bda819e41abe85b1e7",
+ "sha256": "e4a15a5a6a931996f293db247e836e7a681c9f00baa0c4556aa7d5ead67bbc7b",
"size": 10968
},
{
@@ -9025,8 +9011,8 @@
"url": "https://support.claude.com/en/articles/12626668-use-quick-entry-with-claude-desktop-on-mac",
"status": "success",
"path": "support/12626668-use-quick-entry-with-claude-desktop-on-mac.md",
- "sha256": "46048b78d9d44c8690dee004322b8800674f44d2b456c3792807a9174b5b7115",
- "size": 5972
+ "sha256": "1b14c4a528365b9c0374e5c44fc555f7568e2801e73d45361fcf08b85bb6654e",
+ "size": 5974
},
{
"url": "https://support.claude.com/en/articles/12684923-microsoft-365-connector-security-guide",
@@ -9060,8 +9046,8 @@
"url": "https://support.claude.com/en/articles/12883420-view-usage-analytics-for-team-and-enterprise-plans",
"status": "success",
"path": "support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md",
- "sha256": "d21581d3011cb0d21cfbdf7b466591fefbadc7103bd4cee7de8076dcd4b1921b",
- "size": 13173
+ "sha256": "b8a9d606ad21ce9f73f91ac570ce769465d8409d7f94463345e655cb9970540f",
+ "size": 13177
},
{
"url": "https://support.claude.com/en/articles/12902405-claude-in-chrome-troubleshooting",
@@ -9081,8 +9067,8 @@
"url": "https://support.claude.com/en/articles/12902446-claude-in-chrome-permissions-guide",
"status": "success",
"path": "support/12902446-claude-in-chrome-permissions-guide.md",
- "sha256": "b54883e5ab4b891ea431dfcc22ca2cfc9f979d0c22b4be0c13cd553e0f34f399",
- "size": 9571
+ "sha256": "b71a3eb35a92b670f5779aeeb8b360e50bac9a79e6f3559b39fe6adf9aa9b290",
+ "size": 9561
},
{
"url": "https://support.claude.com/en/articles/12938627-how-to-gift-a-claude-subscription",
@@ -9109,8 +9095,8 @@
"url": "https://support.claude.com/en/articles/12997503-team-plan-billing-faqs",
"status": "success",
"path": "support/12997503-team-plan-billing-faqs.md",
- "sha256": "8b77645950729cd05008b6df772d2ba6997921f55b158cc2ae92f3decfcfa230",
- "size": 4006
+ "sha256": "bc7bd6b0c69eba8066590cb9ceff64cc9d8900d94fd2bdb5dbb0686cbc58ed05",
+ "size": 4004
},
{
"url": "https://support.claude.com/en/articles/13015708-access-the-compliance-api",
@@ -9158,15 +9144,15 @@
"url": "https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso",
"status": "success",
"path": "support/13132885-set-up-single-sign-on-sso.md",
- "sha256": "14368b402c18f0a9f0e3dd87babc7e0f7d7b253fb5e1e1097c40e15809e1cd7e",
+ "sha256": "725aab2ce8ea33fc1302522fffd2db84b507cfba815f1db8d0ef97b0c20c915e",
"size": 12321
},
{
"url": "https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning",
"status": "success",
"path": "support/13133195-set-up-jit-or-scim-provisioning.md",
- "sha256": "f2bdb697c738a03e603632ac0b49633280b98ea7f72a746875dff1340be5d35c",
- "size": 16610
+ "sha256": "139be355e5d7a1e198462eca8df473749e05f0a84f4207cfe82505dc71115cb9",
+ "size": 16608
},
{
"url": "https://support.claude.com/en/articles/13133750-manage-members-on-team-and-enterprise-plans",
@@ -9193,7 +9179,7 @@
"url": "https://support.claude.com/en/articles/13163631-configuring-session-security-settings",
"status": "success",
"path": "support/13163631-configuring-session-security-settings.md",
- "sha256": "87b15e8f8b6e2e539d346b21b257c8e2a9f59c581ea8763909f46493c7191422",
+ "sha256": "c066e683adbe2d7e1e1cbc199d26d60146fe6fd657c4f66f4cc5695c5150814b",
"size": 3708
},
{
@@ -9214,7 +9200,7 @@
"url": "https://support.claude.com/en/articles/13189465-log-in-to-your-claude-account",
"status": "success",
"path": "support/13189465-log-in-to-your-claude-account.md",
- "sha256": "79567f5fa0ec4c8328ffbb8f11751b98d967f34313469541b376604307ecfacf",
+ "sha256": "66abddb0c9f070eca14b2e4bc245488ab0e5a792d7d66de447670b1ecf744f1c",
"size": 7040
},
{
@@ -9242,22 +9228,22 @@
"url": "https://support.claude.com/en/articles/13325567-account-management-faqs",
"status": "success",
"path": "support/13325567-account-management-faqs.md",
- "sha256": "cb2d32e438243f76aef6c696fc641424ed904b6b3d6254edcc7d70de61768667",
- "size": 2636
+ "sha256": "75d62236c1716740b359636ccf0e6aee1595e3cd643714ed580d288d702d3ee6",
+ "size": 2634
},
{
"url": "https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork",
"status": "success",
"path": "support/13345190-get-started-with-claude-cowork.md",
- "sha256": "513456ee443bdd4300eaf223a41eb4ed74c1857947b51a0f492d3805a339eea1",
- "size": 20785
+ "sha256": "e7aac729e56ef13da4bcfd0d79bf0e341731fb87877e3106820702730d5877dd",
+ "size": 20574
},
{
"url": "https://support.claude.com/en/articles/13346458-customizing-your-console-appearance-settings",
"status": "success",
"path": "support/13346458-customizing-your-console-appearance-settings.md",
- "sha256": "be6263ce86dcdffa7c39e51b39a65432c7f5b99ead2007a6efe59b6a39a0290b",
- "size": 607
+ "sha256": "5101d4cf575c3a1e2d9cd0ad64af01d56cf6ff956c46206991c86d1eb7a76c6a",
+ "size": 611
},
{
"url": "https://support.claude.com/en/articles/13346720-export-your-organization-s-data",
@@ -9270,15 +9256,15 @@
"url": "https://support.claude.com/en/articles/13364135-use-claude-cowork-safely",
"status": "success",
"path": "support/13364135-use-claude-cowork-safely.md",
- "sha256": "7f6efe09d71413a756ca526cffd83834d3d6cdaab8570699f9c9db56c728aa94",
- "size": 16537
+ "sha256": "840e0562f64bff51600fc942946d8b599f2037402abdb733d28e28638191f48a",
+ "size": 16485
},
{
"url": "https://support.claude.com/en/articles/13371040-log-in-to-your-console-account",
"status": "success",
"path": "support/13371040-log-in-to-your-console-account.md",
- "sha256": "03e54a29c25475b6882ea7153372c9827b81b3b55d36d5871bd9fa425421dea5",
- "size": 4610
+ "sha256": "206567d1a53b90c26f5395ae52f6b475ac970a670737304b4c81999bebdd4e46",
+ "size": 4619
},
{
"url": "https://support.claude.com/en/articles/13393991-purchase-and-manage-seats-on-enterprise-plans",
@@ -9319,8 +9305,8 @@
"url": "https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans",
"status": "success",
"path": "support/13455879-use-claude-cowork-on-team-and-enterprise-plans.md",
- "sha256": "4faf553fbc8513857af32cef5eb4e985055f19050da2fbb7bb850fefe1d6ea8e",
- "size": 10299
+ "sha256": "5fd5c8402562b5dcbf7ca01c5769099792ff7d5caca38fc0bcd7836c1b0d3cba",
+ "size": 10832
},
{
"url": "https://support.claude.com/en/articles/13566435-find-and-join-a-team-or-enterprise-organization",
@@ -9333,8 +9319,8 @@
"url": "https://support.claude.com/en/articles/13641943-visual-and-interactive-content",
"status": "success",
"path": "support/13641943-visual-and-interactive-content.md",
- "sha256": "81e1e5e6189951c8c75d51194cef12083b0711972be3ba11250921fb2dd7486d",
- "size": 6511
+ "sha256": "4445804fad5e125b44bfc30434cc057d4da1b76bee0ae5c0b62909bd00bd95d3",
+ "size": 6515
},
{
"url": "https://support.claude.com/en/articles/13663666-use-visual-and-interactive-content-on-team-and-enterprise-plans",
@@ -9361,8 +9347,8 @@
"url": "https://support.claude.com/en/articles/13756069-public-sector-faqs",
"status": "success",
"path": "support/13756069-public-sector-faqs.md",
- "sha256": "45d2db3c83132366a6ecaf3bcf363c726512e68de4487fc102c186ff0583c60f",
- "size": 8380
+ "sha256": "0d5e591eb93cf7b93558f45642bbab40e8cfec5b25fcf60aa915c7fe1a298f20",
+ "size": 8376
},
{
"url": "https://support.claude.com/en/articles/13776697-join-an-organization-via-invite-link",
@@ -9389,22 +9375,22 @@
"url": "https://support.claude.com/en/articles/13837433-manage-plugins-for-your-organization",
"status": "success",
"path": "support/13837433-manage-plugins-for-your-organization.md",
- "sha256": "a9513957202f77ea8b646b28bb7fee8ed561344bce5827a2154ea737576a86ab",
- "size": 19934
+ "sha256": "15d7cac9b091736d9ad7594910dfd59a81c4de843e73ba1a9151c13c40d0469d",
+ "size": 19932
},
{
"url": "https://support.claude.com/en/articles/13837440-use-plugins-in-claude",
"status": "success",
"path": "support/13837440-use-plugins-in-claude.md",
- "sha256": "0e71a18e91f3ae991feb6861bba3da786fa7f6633c4b914a6ab315ff6b8c5a29",
- "size": 6720
+ "sha256": "ea2420658dbb74d18aaea5a04c52ffc7650a23eb5616d065b037b5f922523924",
+ "size": 6718
},
{
"url": "https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork",
"status": "success",
"path": "support/13854387-schedule-recurring-tasks-in-claude-cowork.md",
- "sha256": "38924c704dae4bb39c93cfdf0899733e2ed75e1e1e862e42c27da494d6cf5291",
- "size": 4700
+ "sha256": "68e66a03dc83e87b070e92a1d1945f83fda9b1b6360036b8c04d6e837d502475",
+ "size": 4771
},
{
"url": "https://support.claude.com/en/articles/13917817-google-workspace-sso-scim-email-mismatch",
@@ -9487,15 +9473,15 @@
"url": "https://support.claude.com/en/articles/13930458-set-up-role-based-permissions-on-enterprise-plans",
"status": "success",
"path": "support/13930458-set-up-role-based-permissions-on-enterprise-plans.md",
- "sha256": "c6532eeda4473d503d23040c98d4c660fb4898defa3f09dda9e3f4d79e0ef512",
- "size": 42062
+ "sha256": "37e214517b86069529aad380581489b04c72322308ad8e0a3f5043f7f0d7eec8",
+ "size": 42072
},
{
"url": "https://support.claude.com/en/articles/13947068-assign-tasks-from-anywhere-in-claude-cowork",
"status": "success",
"path": "support/13947068-assign-tasks-from-anywhere-in-claude-cowork.md",
- "sha256": "84139cdb59cc7ebc2ec225c396dd1f0c68cb7ea92a2b1bbce0e49423c34ab27c",
- "size": 8280
+ "sha256": "e2f96758438773e254f5b5d18bd29cdd6753df50a56184eb0778b7a1aa3e61f5",
+ "size": 8274
},
{
"url": "https://support.claude.com/en/articles/13979539-custom-visuals-in-chat-and-cowork",
@@ -9515,14 +9501,14 @@
"url": "https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork",
"status": "success",
"path": "support/14116274-organize-your-tasks-with-projects-in-claude-cowork.md",
- "sha256": "69b94a1dfaeaba2c26f40aff263831854aead4671e8b2546fc34d9748ebc4fcb",
- "size": 5700
+ "sha256": "eabe691268c2ca3fb321893ebe4646514708bba4c1eb7f067ae7efba0ade4c24",
+ "size": 5702
},
{
"url": "https://support.claude.com/en/articles/14128542-let-claude-use-your-computer-in-cowork",
"status": "success",
"path": "support/14128542-let-claude-use-your-computer-in-cowork.md",
- "sha256": "c56f1497463f73f76089bb19891911ba2262c96068caece50445f7f8a9eda69e",
+ "sha256": "13178013e9108fb3b54d841c6f52dc3393b04c62b1988730bb2c73a9780dbb73",
"size": 8286
},
{
@@ -9578,14 +9564,14 @@
"url": "https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview",
"status": "success",
"path": "support/14479288-claude-cowork-architecture-overview.md",
- "sha256": "1e8ef6da835f9ed4df3aa17f398ec14763f063176f6a7f2017226c22b627b048",
- "size": 7977
+ "sha256": "1ea10cf36be14f76b9e910f0b29130d98dbbf0dcbe2f666a5bc5ee484842ea6a",
+ "size": 7884
},
{
"url": "https://support.claude.com/en/articles/14499648-how-scim-sync-works-for-enterprise-organizations",
"status": "success",
"path": "support/14499648-how-scim-sync-works-for-enterprise-organizations.md",
- "sha256": "6cea295e97334cce29cf2333054f6e18a1746b9f9e2a9f1561131921af56cbdf",
+ "sha256": "2fa09464000431a51eeee2a9a1cfc91e69546c0dc142a2c681e51127b6496fb7",
"size": 7440
},
{
@@ -9606,15 +9592,15 @@
"url": "https://support.claude.com/en/articles/14503613-sso-login",
"status": "success",
"path": "support/14503613-sso-login.md",
- "sha256": "d8d646aa4ce870e4dcf5797f5e628cf1fb814d67b681c5c4adf45a1550b0f4c8",
- "size": 6690
+ "sha256": "e0c7da9670e9ffd7b6ab1995c426a7f99184f780a895fe3f2c3e2073671daff8",
+ "size": 6688
},
{
"url": "https://support.claude.com/en/articles/14503643-set-up-scim-in-claude-for-government",
"status": "success",
"path": "support/14503643-set-up-scim-in-claude-for-government.md",
- "sha256": "5e72bb696249df49a5af5b10d2bb14de900d5907b52b0bfc763b11a77c3f4d6b",
- "size": 6421
+ "sha256": "6bfc58b5af080259f8fe97d6b3c53b528b7d2cc6dd43a8d470d7f6842449b136",
+ "size": 6427
},
{
"url": "https://support.claude.com/en/articles/14503675-organization-instructions-in-claude-for-government",
@@ -9641,8 +9627,8 @@
"url": "https://support.claude.com/en/articles/14503775-mcp-web-search",
"status": "success",
"path": "support/14503775-mcp-web-search.md",
- "sha256": "a55b22379bd2a8710b27945f3e583430f7f50cb87d9313bd17118d2686c6d699",
- "size": 4683
+ "sha256": "a565bdce3f61e383567294d7c352ecd1f9a1fc6f5d1adadff5798a4ab649cef0",
+ "size": 4677
},
{
"url": "https://support.claude.com/en/articles/14503794-model-availability-in-claude-for-government",
@@ -9739,21 +9725,21 @@
"url": "https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design",
"status": "success",
"path": "support/14604397-set-up-your-design-system-in-claude-design.md",
- "sha256": "125ba5a97042bd99b2dae404c86fc3cba2615221624fe1b1ec35cc2f8c4a9abf",
+ "sha256": "86da8b46f75871024532bbf22cc00e831b0add8dc71ba600f2f6ad9eeef1e02d",
"size": 4396
},
{
"url": "https://support.claude.com/en/articles/14604406-claude-design-admin-guide-for-team-and-enterprise-plans",
"status": "success",
"path": "support/14604406-claude-design-admin-guide-for-team-and-enterprise-plans.md",
- "sha256": "aff9c0828994498c356ebdd172be9c0397373b4b64f642f7610000ef1a33b0a0",
+ "sha256": "7669d91006c9d17a7b276f149264ed1f4b6cd4fb1fc444cb5c802833675d8130",
"size": 12733
},
{
"url": "https://support.claude.com/en/articles/14604416-get-started-with-claude-design",
"status": "success",
"path": "support/14604416-get-started-with-claude-design.md",
- "sha256": "765da30057d81aa7d6cb77d1c59b62203900547f6870c93918c89d0e8cde8ee6",
+ "sha256": "9633506ca72900a14d247ca756675bc34e0472b4ea7a12f1d233428770b103aa",
"size": 11136
},
{
@@ -9879,8 +9865,8 @@
"url": "https://support.claude.com/en/articles/15330088-set-a-default-model-for-your-organization",
"status": "success",
"path": "support/15330088-set-a-default-model-for-your-organization.md",
- "sha256": "1987813741d7028ecbc3935157c7074e6dd29544b84f8934452e4a33d2d49840",
- "size": 5744
+ "sha256": "9044aea28b37d7aef339a5736e8d9f343237edf2a4b4d0e65863d85328eed2ea",
+ "size": 5740
},
{
"url": "https://support.claude.com/en/articles/15330651-claude-enterprise-admin-api-reference-guide",
@@ -9949,8 +9935,8 @@
"url": "https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile",
"status": "success",
"path": "support/15520349-use-claude-cowork-on-web-desktop-and-mobile.md",
- "sha256": "70d185c626dc4405a906f779c744829e439f2d828b3b9f8e363e12e514bb83a0",
- "size": 7079
+ "sha256": "f82d1820eeaf3105a410181b369930c79c41286ce8d204b0529d7eaf8017019d",
+ "size": 7044
},
{
"url": "https://support.claude.com/en/articles/15537633-authorize-mcp-connectors-for-your-entire-organization",
@@ -9991,8 +9977,8 @@
"url": "https://support.claude.com/en/articles/15694740-manage-model-access-for-your-organization",
"status": "success",
"path": "support/15694740-manage-model-access-for-your-organization.md",
- "sha256": "e1301d7052e0014a88452897a8e9b1759d24676f31c3033d8de02957c7e53ac9",
- "size": 8499
+ "sha256": "942c4245c52249cbfa9dde14e657df2d4b930aca92c26946bf881a3bdae2eef2",
+ "size": 8497
},
{
"url": "https://support.claude.com/en/articles/15707726-using-claude-for-legal-work-privilege-confidentiality-and-how-to-think-about-configuration",
@@ -10026,7 +10012,7 @@
"url": "https://support.claude.com/en/articles/15936181-get-started-with-1password-for-claude",
"status": "success",
"path": "support/15936181-get-started-with-1password-for-claude.md",
- "sha256": "73e54735192e8ba587d4ba442ea446d9ce91c1bc33e7e0e7cc3e71c28bf6040d",
+ "sha256": "25a8a6a423b7772c602df193b76692e6df9d7d2775c4468afec4566c988c4005",
"size": 5056
},
{
@@ -12203,15 +12189,15 @@
"url": "https://raw.githubusercontent.com/anthropics/claude-plugins-official/main/.claude-plugin/marketplace.json",
"status": "success",
"path": "github/claude-plugins-official/.claude-plugin/marketplace.json",
- "sha256": "82b1738a804e415d8ae8fb9780e042d2a303ef3f11eabc30fdda5d37fad48206",
+ "sha256": "3e7b0ac05caf764db0284fc881b00d3d8b9a69257b2e157e84f7b405b476b929",
"size": 168794
},
{
"url": "https://raw.githubusercontent.com/anthropics/claude-plugins-official/main/.github/bump-tracking.json",
"status": "success",
"path": "github/claude-plugins-official/.github/bump-tracking.json",
- "sha256": "9783a7a4ddacdfcf3157c8134bc2e825e1b6e1f9ac5fe83dbda5f9e3ed13cd83",
- "size": 264
+ "sha256": "7bac174580f6881e9f75426cbebf6e05e7b7b251cda403016361114168f2ecf9",
+ "size": 277
},
{
"url": "https://raw.githubusercontent.com/anthropics/claude-plugins-official/main/.github/policy/prompt.md",
@@ -12735,8 +12721,8 @@
"url": "https://raw.githubusercontent.com/anthropics/claude-plugins-official/main/plugins/claude-security/.claude-plugin/plugin.json",
"status": "success",
"path": "github/claude-plugins-official/plugins/claude-security/.claude-plugin/plugin.json",
- "sha256": "93e66d694b88f4b99b1b9b2f17a72a320d2717a1331c4acab587cb3921ceefa2",
- "size": 754
+ "sha256": "76818ac7dee341a44b4e84f106272f3f7509a309e5ab45fbf00a330790e8fe08",
+ "size": 750
},
{
"url": "https://raw.githubusercontent.com/anthropics/claude-plugins-official/main/plugins/claude-security/NOTICE.md",
@@ -15918,6 +15904,10 @@
}
],
"failures": [
+ {
+ "url": "https://support.claude.com/en/articles/10722177-sharing-prompts-in-the-claude-console",
+ "error": "404, message='Not Found', url='https://support.claude.com/en/articles/10722177-sharing-prompts-in-the-claude-console.md'"
+ },
{
"url": "https://support.claude.com/en/articles/12650343-use-claude-for-excel",
"error": "upstream returned HTML, not markdown (soft 404)"
@@ -15948,10 +15938,10 @@
}
],
"summary": {
- "total": 2280,
- "downloaded": 2273,
+ "total": 2279,
+ "downloaded": 2271,
"skipped": 0,
- "failed": 7,
- "success_rate": 99.7
+ "failed": 8,
+ "success_rate": 99.6
}
}
\ No newline at end of file
diff --git a/content/CHANGELOG.md b/content/CHANGELOG.md
index d4b7b0dea..17b809154 100644
--- a/content/CHANGELOG.md
+++ b/content/CHANGELOG.md
@@ -1,5 +1,27 @@
# Changelog
+## 2.1.235
+
+- Added an optional `spellcheck` setting that underlines misspelled words in the prompt input as you type, using your installed `aspell`, `hunspell`, or `ispell`
+- Fixed whole-prompt-cache invalidation when a language server disconnected or reconnected mid-session
+- Fixed nested markdown list items misaligning at depth 3+ and added a hanging indent to wrapped list items in the terminal UI
+- Fixed prompt input highlights (slash commands, keywords, mentions) appearing shifted by one or more characters in some multi-line prompts
+- Fixed Shift+Tab inside the permission prompt's comment field approving the edit and granting session-wide edit permission instead of closing the field
+- Fixed the Agent tool advertising a general-purpose default in sessions where that agent is unavailable: an omitted `subagent_type` there now gets a clear error listing the available agents
+- Fixed notebook cell delete/replace approval dialogs silently omitting the existing cell content when the notebook or cell could not be read; the dialog now says why
+- Fixed slash commands run while Claude is responding showing HTML entities instead of the actual characters
+- Fixed the prompt footer not showing the "Update installed" restart notice after a background auto-update
+- Fixed the expanded task list (`ctrl+t`) always starting collapsed when resuming or relaunching into a session that still has open tasks
+- Improved memory and CPU usage while cloud sessions such as `/ultrareview` or `/autofix-pr` run in the background — their event streams are no longer re-scanned and re-rendered on every update
+- Improved permission dialogs: display text and "don't ask again" options now always match what a grant would cover, and "don't ask again" is withheld when contents cannot be fully displayed
+- Improved the embedded `grep` in native macOS/Linux builds: pathological patterns now fail fast instead of exhausting memory, and `-m N` with `-A/-C` prints correct context
+- Improved the context-limit error to say when auto-compact is off and point to `/config` to re-enable it
+- Vim mode: NORMAL mode and cursor position are now preserved when toggling the detailed transcript (ctrl+o) or closing a panel
+- Dialogs: arrow keys and Enter pressed in quick succession now select the option you navigated to instead of the previously highlighted one
+- `SendMessage` now refuses messages too large for cross-session delivery up front instead of silently dropping them
+- Remote Control: `claude rc` now applies the same enterprise-gateway availability check as interactive startup
+- [VSCode] Fixed focus jumping between open Claude tabs on its own when a window with several Claude panels is restored or reloaded
+
## 2.1.234
- Added the optional `CLAUDE_CODE_PROJECT_DIR_NAME` environment variable: hosts that give each session its own config directory can choose a short name for the per-project transcript directory
diff --git a/content/claude-code-manifest.json b/content/claude-code-manifest.json
index 5899bd50c..8e21cc3a2 100644
--- a/content/claude-code-manifest.json
+++ b/content/claude-code-manifest.json
@@ -6,25 +6,25 @@
"url": "https://github.com/anthropics/claude-code/issues"
},
"dist": {
- "shasum": "eea30699ec57eb975d3b11e29d6f180c25555665",
- "tarball": "https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-2.1.234.tgz",
+ "shasum": "c82eb033efe6148a49edad03948249ad9299ed57",
+ "tarball": "https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-2.1.235.tgz",
"fileCount": 7,
- "integrity": "sha512-Q53mRcFLqPAWfkvqn7vOzTtMHprzwKdKGRW4OS/Kgr/Tsa+2pyVwVetLb7DRZxhBkYsYld2l8Eo4SX76YoNOOA==",
+ "integrity": "sha512-poJ4l/nro9NEZEoLU1txUGMMw92m5P3o6Nh86GfaQuPryvOdKIz/ChlPaq3FDetiaXmoNit3ZkEgnQ1PN7z/dQ==",
"signatures": [
{
- "sig": "MEUCIQCrlnulSoybeDhXS8CVVt1t0u8IxjE2WdAiDfmB2swlvgIgAb6MjLOiVhXxVjRnE3ycNSLyjYTuKulqjjlU3N0gaPQ=",
+ "sig": "MEUCICWFRrQ6e/5sYX/aTAiw/df8RDBoLmutS1j4mWM7u+BRAiEA1nYVfv8+kNrhnQlbCGplF06D2E57sNrNjhUekg2REsU=",
"keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"
},
{
- "sig": "MEQCIHI68Cs7gsGXBbgoeb6nZPohmvs8hwxGaj7MUC7xfHjaAiBe13QeVO2IiNrrS3azVU5LOaUFZ+4i6WNZnAb33Qdmgg==",
+ "sig": "MEUCIQDB9fa6n4sJFMF+1MODgqK7cxlMnyh0fzPTA0OOxPhpJwIgTB0ldNxmWVRN56SCcFXmNskRD9hwaAOqbTmxJhovV5g=",
"keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"
}
],
- "unpackedSize": 171853
+ "unpackedSize": 172650
},
"name": "@anthropic-ai/claude-code",
"type": "module",
- "_from": "file:staged-npm/anthropic-ai-claude-code-2.1.234.tgz",
+ "_from": "file:staged-npm/anthropic-ai-claude-code-2.1.235.tgz",
"author": {
"name": "Anthropic",
"email": "support@anthropic.com"
@@ -42,8 +42,8 @@
"email": "wolffiex@anthropic.com"
},
"homepage": "https://github.com/anthropics/claude-code",
- "_resolved": "/home/runner/work/claude-cli-internal/claude-cli-internal/staged-npm/anthropic-ai-claude-code-2.1.234.tgz",
- "_integrity": "sha512-Q53mRcFLqPAWfkvqn7vOzTtMHprzwKdKGRW4OS/Kgr/Tsa+2pyVwVetLb7DRZxhBkYsYld2l8Eo4SX76YoNOOA==",
+ "_resolved": "/home/runner/work/claude-cli-internal/claude-cli-internal/staged-npm/anthropic-ai-claude-code-2.1.235.tgz",
+ "_integrity": "sha512-poJ4l/nro9NEZEoLU1txUGMMw92m5P3o6Nh86GfaQuPryvOdKIz/ChlPaq3FDetiaXmoNit3ZkEgnQ1PN7z/dQ==",
"_npmVersion": "11.17.0",
"description": "Use Claude, Anthropic's AI assistant, right from your terminal. Claude can understand your codebase, edit files, run terminal commands, and handle entire workflows for you.",
"directories": {},
@@ -106,19 +106,19 @@
"_hasShrinkwrap": false,
"readmeFilename": "README.md",
"optionalDependencies": {
- "@anthropic-ai/claude-code-linux-x64": "2.1.234",
- "@anthropic-ai/claude-code-win32-x64": "2.1.234",
- "@anthropic-ai/claude-code-darwin-x64": "2.1.234",
- "@anthropic-ai/claude-code-linux-arm64": "2.1.234",
- "@anthropic-ai/claude-code-win32-arm64": "2.1.234",
- "@anthropic-ai/claude-code-darwin-arm64": "2.1.234",
- "@anthropic-ai/claude-code-linux-x64-musl": "2.1.234",
- "@anthropic-ai/claude-code-linux-arm64-musl": "2.1.234"
+ "@anthropic-ai/claude-code-linux-x64": "2.1.235",
+ "@anthropic-ai/claude-code-win32-x64": "2.1.235",
+ "@anthropic-ai/claude-code-darwin-x64": "2.1.235",
+ "@anthropic-ai/claude-code-linux-arm64": "2.1.235",
+ "@anthropic-ai/claude-code-win32-arm64": "2.1.235",
+ "@anthropic-ai/claude-code-darwin-arm64": "2.1.235",
+ "@anthropic-ai/claude-code-linux-x64-musl": "2.1.235",
+ "@anthropic-ai/claude-code-linux-arm64-musl": "2.1.235"
},
"_npmOperationalInternal": {
- "tmp": "tmp/claude-code_2.1.234_1786990753077_0.3071230343831646",
+ "tmp": "tmp/claude-code_2.1.235_1787077450102_0.9499445655869563",
"host": "s3://npm-registry-packages-npm-production"
},
- "_id": "@anthropic-ai/claude-code@2.1.234",
- "version": "2.1.234"
+ "_id": "@anthropic-ai/claude-code@2.1.235",
+ "version": "2.1.235"
}
\ No newline at end of file
diff --git a/content/en/agents-and-tools/agent-skills/enterprise.md b/content/en/agents-and-tools/agent-skills/enterprise.md
index 78e6b565c..f1c7a9347 100644
--- a/content/en/agents-and-tools/agent-skills/enterprise.md
+++ b/content/en/agents-and-tools/agent-skills/enterprise.md
@@ -44,6 +44,12 @@ Before deploying any Skill from a third party or internal contributor, complete
Never deploy Skills from untrusted sources without a full audit. A malicious Skill can direct Claude to execute arbitrary code, access sensitive files, or transmit data externally. Treat Skill installation with the same rigor as installing software on production systems.
+### Skill content scanning
+
+Claude Enterprise organizations can turn on automated security scanning for custom Skills in claude.ai and Claude Cowork. The feature is in beta. After you turn on **Skill and plugin security scanning** at [claude.ai > Organization settings > Skills](https://claude.ai/admin-settings/skills), Skills that members then upload or edit in claude.ai or Cowork are scanned for signs of malicious behavior, such as hidden code execution, sending your data to an outside service, or instructions that tamper with Claude's safeguards. A Skill that fails the scan, or whose scan hasn't finished, is blocked from use. A Skill that passes with a warning stays usable behind a caution notice. If scanning is available to your organization, turn it on. It complements, but doesn't replace, the [review checklist](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/enterprise#review-checklist).
+
+Scanning doesn't cover the Claude API. Skills you upload through the Skills API (`/v1/skills`), including from the Claude Console, aren't scanned, so for API deployments, rely on the review checklist and [version pinning](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/enterprise#versioning-strategy). Scanning also doesn't apply to Skills that were already in your organization when you turned it on, or to organizations with certain data handling configurations, such as customer-managed encryption keys (CMEK), zero data retention (ZDR), or HIPAA readiness. For setup steps, exclusions, and result types, see [Get started with skill and plugin scanning](https://support.claude.com/en/articles/15927065-get-started-with-skill-and-plugin-scanning) in the Claude Help Center.
+
## Evaluating Skills before deployment
Skills can degrade agent performance if they trigger incorrectly, conflict with other Skills, or provide poor instructions. Require evaluation before any production deployment.
@@ -158,7 +164,7 @@ The Skills API provides workspace-scoped distribution. Skills uploaded through t
### Versioning strategy
-* **Production:** Pin Skills to specific versions. Run the full evaluation suite before promoting a new version. Treat every update as a new deployment requiring full security review.
+* **Production:** Pin Skills to specific versions. If you omit `version`, requests use the latest version, so a new version uploaded by anyone in the workspace immediately changes what production agents run. Run the full evaluation suite before promoting a new version. Treat every update as a new deployment requiring full security review.
* **Development and testing:** Use latest versions to validate changes before production promotion.
* **Rollback plan:** Maintain the previous version as a fallback. If a new version fails evaluations in production, revert to the last known-good version immediately.
* **Integrity verification:** Compute checksums of reviewed Skills and verify them at deployment time. Use signed commits in your Skill repository to ensure provenance.
diff --git a/content/en/agents-and-tools/agent-skills/overview.md b/content/en/agents-and-tools/agent-skills/overview.md
index 6c87e047f..ff5600502 100644
--- a/content/en/agents-and-tools/agent-skills/overview.md
+++ b/content/en/agents-and-tools/agent-skills/overview.md
@@ -240,7 +240,7 @@ Use Skills only from trusted sources: those you created yourself or obtained fro
* **Data exposure:** Skills with access to sensitive data could be designed to leak information to external systems
* **Treat like installing software:** Be especially careful when integrating Skills into production systems with access to sensitive data or critical operations
-For organization-scale governance, vetting, and deployment guidance, see [Skills for enterprise](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/enterprise).
+For organization-scale governance, vetting, and deployment guidance, see [Skills for enterprise](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/enterprise). Claude Enterprise organizations can also turn on [Skill content scanning](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/enterprise#skill-content-scanning) for custom Skills uploaded in claude.ai and Claude Cowork. Scanning doesn't cover Skills uploaded through the Skills API or the Claude Console.
## Available Skills
@@ -271,6 +271,8 @@ Agent Skills is not covered by ZDR arrangements. Skill definitions and execution
For ZDR eligibility across all features, see [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention).
+For audit logging of Skills API operations, see [Audit logging](https://platform.claude.com/docs/en/build-with-claude/skills-guide#audit-logging) in Using Agent Skills with the API.
+
## Limitations and constraints
Claude Platform on AWS and Microsoft Foundry follow the same limitations as the Claude API in the following subsections.
diff --git a/content/en/api/overview.md b/content/en/api/overview.md
index 76955f65a..20589f12f 100644
--- a/content/en/api/overview.md
+++ b/content/en/api/overview.md
@@ -57,7 +57,7 @@ When accessing Claude through a [cloud platform](https://platform.claude.com/doc
### Getting API keys
-The API is made available through the web [Console](https://platform.claude.com/). You can use the [Workbench](https://platform.claude.com/playground) to try out the API in the browser and then generate API keys in [Account Settings](https://platform.claude.com/settings/keys). You choose each key's [expiration](https://platform.claude.com/docs/en/manage-claude/authentication#key-expiration) when you create it. Use [workspaces](https://platform.claude.com/settings/workspaces) to segment your API keys and [control spend](https://platform.claude.com/docs/en/api/rate-limits) by use case.
+The API is made available through the web [Console](https://platform.claude.com/). You can use [Playground](https://platform.claude.com/playground) to try out the API in the browser and then generate API keys in [Account Settings](https://platform.claude.com/settings/keys). You choose each key's [expiration](https://platform.claude.com/docs/en/manage-claude/authentication#key-expiration) when you create it. Use [workspaces](https://platform.claude.com/settings/workspaces) to segment your API keys and [control spend](https://platform.claude.com/docs/en/api/rate-limits) by use case.
## Client SDKs
diff --git a/content/en/build-with-claude/files.md b/content/en/build-with-claude/files.md
index ccb40a45e..d9f8615e1 100644
--- a/content/en/build-with-claude/files.md
+++ b/content/en/build-with-claude/files.md
@@ -32,6 +32,8 @@ The Files API provides a create-once, use-many-times approach for working with f
**Uploaded files are accessible to your entire workspace, not scoped to an end user, conversation, or session.** Any API key in the same workspace can access any file uploaded there, and all of your keys share your organization's Default Workspace unless you have assigned them to separate [workspaces](https://platform.claude.com/docs/en/manage-claude/workspaces#api-keys-and-resource-scoping). Never accept `file_id` values from end users or other untrusted sources: a user-supplied file ID would let one user of your application read content that another user uploaded. Treat file IDs as server-side references, and keep the mapping between your users and their files in your application.
+
+ If you are building a multi-tenant application on the Files API, create a separate [workspace](https://platform.claude.com/docs/en/manage-claude/workspaces) for each tenant. The workspace is the isolation boundary for files, so a workspace per tenant gives each tenant's data hard isolation from every other tenant. Each organization can have up to 100 workspaces; contact your account team if you need more.
## How to use the Files API
@@ -978,7 +980,7 @@ Download files that were created by [skills](https://platform.claude.com/docs/en
### Storage limits
* **Maximum file size:** 500 MB per file
-* **Total storage:** 500 GB per organization
+* **Total storage:** 1 TB per organization
### File lifecycle
@@ -989,6 +991,10 @@ Download files that were created by [skills](https://platform.claude.com/docs/en
* Files are inaccessible through the API shortly after deletion, but they may persist in active Messages API calls and associated tool uses
* Files that users delete will be deleted in accordance with Anthropic's [data retention policy](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data). For ZDR eligibility across all features, see [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention)
+### Audit logging
+
+If your organization has the [Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api) enabled, its [Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed) records Files API operations made with a Claude API key or from the Claude Console: each upload (`POST /v1/files`), content download (`GET /v1/files/{file_id}/content`), and deletion (`DELETE /v1/files/{file_id}`) appears as a `platform_file_uploaded`, `platform_file_content_downloaded`, or `platform_file_deleted` activity. Listing files and retrieving file metadata are not recorded. Operations that occur while the Compliance API is off are not recorded and cannot be recovered later, so [set up the Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api-access) before you rely on this audit trail. On [Claude Platform on AWS](https://platform.claude.com/docs/en/build-with-claude/claude-platform-on-aws#monitoring-and-logging), audit file operations with AWS CloudTrail data events instead.
+
## Error handling
Common errors when using the Files API include:
@@ -999,7 +1005,7 @@ Common errors when using the Files API include:
* **Exceeds context window size (400):** The file is larger than the context window size (for example, using a 500 MB plain text file in a `/v1/messages` request)
* **Invalid filename (400):** The file name doesn't meet the length requirements (1-255 characters) or contains forbidden characters (`<`, `>`, `:`, `"`, `|`, `?`, `*`, `\`, `/`, or Unicode characters 0-31)
* **File too large (413):** File exceeds the 500 MB limit
-* **Storage limit exceeded (400):** Your organization has reached the 500 GB storage limit
+* **Storage limit exceeded (400):** Your organization has reached the 1 TB storage limit
```json Output
{
@@ -1026,10 +1032,7 @@ File content used in Messages requests is priced as input tokens.
### Rate limits
-During the beta period:
-
-* File-related API calls are limited to approximately 100 requests per minute
-* [Contact us](mailto:sales@anthropic.com) if you need higher limits for your use case
+File-related API calls are limited to approximately 500 requests per minute. To request a higher limit, [contact sales](mailto:sales@anthropic.com).
## Next steps
diff --git a/content/en/build-with-claude/skills-guide.md b/content/en/build-with-claude/skills-guide.md
index 9f77c4c57..6a6238f23 100644
--- a/content/en/build-with-claude/skills-guide.md
+++ b/content/en/build-with-claude/skills-guide.md
@@ -2244,6 +2244,12 @@ Combine multiple Skills in a single request to handle complex workflows:
## Managing custom Skills
+
+ **Custom Skills are accessible to your entire workspace, not scoped to an end user, conversation, or session.** Any API key in the same workspace can read, invoke, and delete every custom Skill uploaded there, and all of your keys share your organization's Default Workspace unless you have assigned them to separate [workspaces](https://platform.claude.com/docs/en/manage-claude/workspaces#api-keys-and-resource-scoping).
+
+ If you are building a multi-tenant platform on the Skills API, create a separate [workspace](https://platform.claude.com/docs/en/manage-claude/workspaces) for each tenant. The workspace is the isolation boundary for custom Skills, so a workspace per tenant gives each tenant's Skills hard isolation from every other tenant. Each organization can have up to 100 workspaces by default (see [How workspaces work](https://platform.claude.com/docs/en/manage-claude/workspaces#how-workspaces-work)); if you need more for tenant isolation, contact your account team.
+
+
### Creating a Skill
A Skill bundle is a directory containing a `SKILL.md` file at the top level with `name` and `description` YAML frontmatter, plus any supporting scripts or resources. See [Get started with Agent Skills in the API](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/quickstart) to author one, and the **Requirements** list following the examples for the full constraints.
@@ -3937,7 +3943,7 @@ Combine Skills when tasks involve multiple document types or domains:
The SDK tabs in this section show the `container` value to include in a Messages request. The cURL and CLI tabs show the full request.
-**For production:** pin a specific version, so Skill updates never change your deployed behavior. The version ID comes from the create-version response in [Versioning](https://platform.claude.com/docs/en/build-with-claude/skills-guide#versioning) or from the [List Skill Versions API](https://platform.claude.com/docs/en/api/beta/skills/versions/list). The ID is always a string: quote epoch-timestamp IDs in JSON or YAML.
+**For production:** pin a specific version, so Skill updates never change your deployed behavior. If you omit `version` or set it to `"latest"`, requests use the newest version of the Skill, so a version uploaded by anyone in the [workspace](https://platform.claude.com/docs/en/build-with-claude/skills-guide#workspace-scoped-access) immediately changes what your production agents run. The version ID comes from the create-version response in [Versioning](https://platform.claude.com/docs/en/build-with-claude/skills-guide#versioning) or from the [List Skill Versions API](https://platform.claude.com/docs/en/api/beta/skills/versions/list). The ID is always a string: quote epoch-timestamp IDs in JSON or YAML.
```bash cURL
@@ -4949,6 +4955,10 @@ Agent Skills are not covered by ZDR arrangements. Skill definitions and executio
For ZDR eligibility across all features, see [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention).
+## Audit logging
+
+If your organization has the [Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api) enabled, its [Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed) records the creation and deletion of Skills and Skill versions made with a Claude API key or from the Claude Console. Operations that occur while the Compliance API is off are not recorded and cannot be recovered later, so [set up the Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api-access) before you rely on this audit trail.
+
## Next steps
diff --git a/content/en/build-with-claude/vision.md b/content/en/build-with-claude/vision.md
index c8ead9422..efee46ac5 100644
--- a/content/en/build-with-claude/vision.md
+++ b/content/en/build-with-claude/vision.md
@@ -13,7 +13,7 @@ This guide describes how to send images to Claude, the limits and costs that app
Use Claude's vision capabilities through:
* [claude.ai](https://claude.ai/). Upload an image like you would a file, or drag and drop an image directly into the chat window.
-* The [Workbench](https://platform.claude.com/playground) in the Claude Console. Add images directly to any User message block.
+* [Playground](https://platform.claude.com/playground) in the Claude Console. Add images directly to any User message block.
* API request. See the following examples.
On the API, provide images to Claude as `image` content blocks using one of three source types:
diff --git a/content/en/docs/claude-code/agent-sdk/agent-loop.md b/content/en/docs/claude-code/agent-sdk/agent-loop.md
index 6a12fdaeb..05dd2567b 100644
--- a/content/en/docs/claude-code/agent-sdk/agent-loop.md
+++ b/content/en/docs/claude-code/agent-sdk/agent-loop.md
@@ -257,9 +257,9 @@ Compaction replaces older messages with a summary, so specific instructions from
You can customize compaction behavior in several ways:
-* **Summarization instructions in CLAUDE.md:** The compactor reads your CLAUDE.md like any other context, so you can include a section telling it what to preserve when summarizing. The section header is free-form (not a magic string); the compactor matches on intent.
+* **Summarization instructions in CLAUDE.md:** The compactor reads your CLAUDE.md like any other context, so you can include a section telling it what to preserve when summarizing. The compactor matches on intent, so the section header is free-form.
* **`PreCompact` hook:** Run custom logic before compaction occurs, for example to archive the full transcript. The hook receives a `trigger` field (`manual` or `auto`). See [hooks](/docs/en/agent-sdk/hooks).
-* **Manual compaction:** Send `/compact` as a prompt string to trigger compaction on demand. Commands sent this way are ordinary SDK inputs. See [commands in the SDK](/docs/en/agent-sdk/slash-commands).
+* **Manual compaction:** Send `/compact` as a prompt string to trigger compaction on demand. Commands sent this way are ordinary SDK inputs. See [dispatch commands by name](/docs/en/agent-sdk/skills#dispatch-commands-by-name).
Add a section to your project's CLAUDE.md telling the compactor what to preserve. The header name isn't special; use any clear label.
@@ -322,7 +322,7 @@ The `usage` field covers only the main agent loop. Use `modelUsage`, or `model_u
When a query ends on an error result:
- * A single-shot `query()` call yields the final result message, then raises an error that includes the failure text, such as `Reached maximum number of turns`. The raise is intentional — wrap the loop in a try block if your code needs to continue past it. The underlying Claude Code process also exits with a nonzero code.
+ * A single-shot `query()` call yields the final result message, then raises an error that includes the failure text, such as `Reached maximum number of turns`. The raise is intentional. Wrap the loop in a try block if your code needs to continue past it. The underlying Claude Code process also exits with a nonzero code.
* A streaming input session stays alive, and you can keep sending messages, except after a session crash, which emits a final `error_during_execution` result and exits the process.
diff --git a/content/en/docs/claude-code/agent-sdk/overview.md b/content/en/docs/claude-code/agent-sdk/overview.md
index eca3e6cb1..65b26aed8 100644
--- a/content/en/docs/claude-code/agent-sdk/overview.md
+++ b/content/en/docs/claude-code/agent-sdk/overview.md
@@ -25,16 +25,16 @@ The SDK is available as a library for Python and TypeScript only. To drive the s
Everything that makes Claude Code powerful is available in the SDK.
-| Capability | What it does | Learn more |
-| ---------------------------- | -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Built-in tools | Read, write, edit files, run commands, and search the web | [Tools reference](/docs/en/tools-reference) |
-| Hooks | Run custom code at key points in the agent lifecycle | [Hooks](/docs/en/agent-sdk/hooks) |
-| Subagents | Spawn specialized agents for focused subtasks | [Subagents](/docs/en/agent-sdk/subagents) |
-| MCP | Connect external tools and data sources via the Model Context Protocol | [MCP](/docs/en/agent-sdk/mcp) |
-| Permissions | Control which tools run automatically, which need approval | [Permissions](/docs/en/agent-sdk/permissions) |
-| Sessions | Maintain context across exchanges, resume or fork later | [Sessions](/docs/en/agent-sdk/sessions) |
-| Skills, commands, and memory | Load automatically from your project's `.claude/` and from `~/.claude/`, same as Claude Code | [Skills](/docs/en/agent-sdk/skills), [Commands](/docs/en/agent-sdk/slash-commands), [Memory](/docs/en/agent-sdk/modifying-system-prompts), [Configuration loading](/docs/en/agent-sdk/claude-code-features) |
-| Plugins | Package skills, agents, hooks, and MCP servers, and load them by local path | [Plugins](/docs/en/agent-sdk/plugins) |
+| Capability | What it does | Learn more |
+| ---------------------------- | -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Built-in tools | Read, write, edit files, run commands, and search the web | [Tools reference](/docs/en/tools-reference) |
+| Hooks | Run custom code at key points in the agent lifecycle | [Hooks](/docs/en/agent-sdk/hooks) |
+| Subagents | Spawn specialized agents for focused subtasks | [Subagents](/docs/en/agent-sdk/subagents) |
+| MCP | Connect external tools and data sources via the Model Context Protocol | [MCP](/docs/en/agent-sdk/mcp) |
+| Permissions | Control which tools run automatically, which need approval | [Permissions](/docs/en/agent-sdk/permissions) |
+| Sessions | Maintain context across exchanges, resume or fork later | [Sessions](/docs/en/agent-sdk/sessions) |
+| Skills, commands, and memory | Load automatically from your project's `.claude/` and from `~/.claude/`, same as Claude Code | [Skills](/docs/en/agent-sdk/skills), [Commands](/docs/en/agent-sdk/skills#commands-in-agent-sdk-sessions), [Memory](/docs/en/agent-sdk/modifying-system-prompts), [Configuration loading](/docs/en/agent-sdk/claude-code-features) |
+| Plugins | Package skills, agents, hooks, and MCP servers, and load them by local path | [Plugins](/docs/en/agent-sdk/plugins) |
## Get started
diff --git a/content/en/docs/claude-code/agent-sdk/plugins.md b/content/en/docs/claude-code/agent-sdk/plugins.md
index 82d8be908..38df3de16 100644
--- a/content/en/docs/claude-code/agent-sdk/plugins.md
+++ b/content/en/docs/claude-code/agent-sdk/plugins.md
@@ -332,6 +332,6 @@ If plugin skills don't work:
* [Plugins](/docs/en/plugins) - Complete plugin development guide
* [Plugins reference](/docs/en/plugins-reference) - Technical specifications
-* [Commands](/docs/en/agent-sdk/slash-commands) - Using commands in the SDK
+* [Commands](/docs/en/agent-sdk/skills#dispatch-commands-by-name) - Dispatching commands in the SDK
* [Subagents](/docs/en/agent-sdk/subagents) - Working with specialized agents
* [Skills](/docs/en/agent-sdk/skills) - Using Agent Skills
diff --git a/content/en/docs/claude-code/agent-sdk/skills.md b/content/en/docs/claude-code/agent-sdk/skills.md
index b9e27d7cd..b1c4dfcbe 100644
--- a/content/en/docs/claude-code/agent-sdk/skills.md
+++ b/content/en/docs/claude-code/agent-sdk/skills.md
@@ -2,39 +2,54 @@
> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
-# Agent Skills in the SDK
+# Extend agents with skills
-> Extend Claude with specialized capabilities using Agent Skills in the Claude Agent SDK
+> Control which skills Claude can invoke in Claude Agent SDK sessions, dispatch commands by name, and author skills your sessions discover
-## Overview
+Agent Skills extend Claude with specialized capabilities that Claude invokes when relevant. Skills are packaged as `SKILL.md` files containing instructions, descriptions, and optional supporting resources. This page also covers [commands in Agent SDK sessions](#commands-in-agent-sdk-sessions).
-Agent Skills extend Claude with specialized capabilities that Claude autonomously invokes when relevant. Skills are packaged as `SKILL.md` files containing instructions, descriptions, and optional supporting resources.
+For comprehensive information about skills, including benefits, architecture, and authoring guidelines, see the [Agent Skills overview](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview).
-For comprehensive information about Skills, including benefits, architecture, and authoring guidelines, see the [Agent Skills overview](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview).
+## How skills work with the Agent SDK
-## How Skills Work with the SDK
+When using the Claude Agent SDK, skills are:
-When using the Claude Agent SDK, Skills are:
+* **Defined as filesystem artifacts**: you create each skill as a `SKILL.md` file in its own directory, such as `.claude/skills//SKILL.md`
+* **Loaded from filesystem**: the SDK loads skills from the filesystem locations governed by `settingSources` (TypeScript) or `setting_sources` (Python)
+* **Automatically discovered**: once filesystem settings load, the SDK discovers skill metadata at startup from user and project directories, and loads the full content when Claude invokes the skill
+* **Model-invoked**: Claude autonomously chooses when to use them based on context
+* **User-invoked**: you dispatch a skill directly by sending `/` in a prompt. See [Commands in Agent SDK sessions](#commands-in-agent-sdk-sessions)
+* **Scoped via the `skills` option**: discovered skills are enabled by default. Pass a list of skill names, `"all"`, or `[]` to control which skills Claude can invoke
-1. **Defined as filesystem artifacts**: you create each Skill as a `SKILL.md` file in its own directory, such as `.claude/skills//SKILL.md`
-2. **Loaded from filesystem**: the SDK loads Skills from the filesystem locations governed by `settingSources` (TypeScript) or `setting_sources` (Python)
-3. **Automatically discovered**: once filesystem settings load, the SDK discovers Skill metadata at startup from user and project directories, and loads the full content when Claude invokes the Skill
-4. **Model-invoked**: Claude autonomously chooses when to use them based on context
-5. **Filtered via the `skills` option**: discovered skills are enabled by default. Pass a list of skill names, `"all"`, or `[]` to control which are available in the session
-
-Unlike subagents (which can be defined programmatically), Skills must be created as filesystem artifacts. The SDK does not provide a programmatic API for registering Skills.
+Unlike subagents, which you can define in the [`agents` option](/docs/en/agent-sdk/subagents#programmatic-definition-recommended), you create skills as files on disk. The SDK doesn't provide a programmatic API for registering them.
Skills are discovered through the filesystem setting sources. With default `query()` options, the SDK loads user and project sources, so skills in `~/.claude/skills/`, `/.claude/skills/`, and `.claude/skills/` in any parent directory of `` up to the repository root are available. If you set `settingSources` explicitly, include `'user'` or `'project'` to keep skill discovery, or use the [`plugins` option](/docs/en/agent-sdk/plugins) to load skills from a specific path.
-## Using Skills with the SDK
+## Use skills with the Agent SDK
+
+Set the `skills` option on `query()` to control which skills Claude can invoke in the session. When omitted, discovered skills are enabled and the Skill tool is available, matching CLI behavior. Pass `"all"` to let Claude invoke every discovered skill, a list of skill names to allow only those, or `[]` to let Claude invoke none.
+
+For example, to let Claude invoke only two named skills:
+
+
+ ```python Python theme={null}
+ options = ClaudeAgentOptions(skills=["pdf", "docx"])
+ ```
+
+ ```typescript TypeScript theme={null}
+ const options = { skills: ["pdf", "docx"] };
+ ```
+
+
+### Set up skills in a session
-Set the `skills` option on `query()` to control which Skills are available to the session. When omitted, discovered Skills are enabled and the Skill tool is available, matching CLI behavior. Pass `"all"` to enable every discovered Skill, a list of Skill names to enable only those, or `[]` to disable all. When you set `skills`, the SDK adds the Skill tool to `allowedTools` automatically. If you also pass an explicit `tools` list, include `"Skill"` in that list so Claude can invoke skills.
+When you set `skills`, the SDK adds the Skill tool to `allowedTools` automatically. If you also pass an explicit `tools` list, include `"Skill"` in that list so Claude can invoke skills.
-Once configured, Claude automatically discovers Skills from the filesystem and invokes them when relevant to the user's request.
+Once configured, Claude automatically discovers skills from the filesystem and invokes them when relevant to the user's request.
-The following example sets `cwd` to the process's current working directory, so run it from inside a project that has a `.claude/skills/` directory in the current directory or any parent up to the repository root:
+The following example enables every discovered skill in a session and pre-approves the tools that skills commonly need. The example sets `cwd` to the process's current working directory, so run it from inside a project that has a `.claude/skills/` directory in the current directory or any parent up to the repository root:
```python Python theme={null}
@@ -47,8 +62,8 @@ The following example sets `cwd` to the process's current working directory, so
async def main():
options = ClaudeAgentOptions(
cwd=os.getcwd(), # .claude/skills/ here or in a parent directory
- setting_sources=["user", "project"], # Load Skills from filesystem
- skills="all", # Enable every discovered Skill
+ setting_sources=["user", "project"], # Load skills from filesystem
+ skills="all", # Let Claude invoke every discovered skill
allowed_tools=["Read", "Write", "Bash"],
)
@@ -68,8 +83,8 @@ The following example sets `cwd` to the process's current working directory, so
prompt: "Help me process this PDF document",
options: {
cwd: process.cwd(), // .claude/skills/ here or in a parent directory
- settingSources: ["user", "project"], // Load Skills from filesystem
- skills: "all", // Enable every discovered Skill
+ settingSources: ["user", "project"], // Load skills from filesystem
+ skills: "all", // Let Claude invoke every discovered skill
allowedTools: ["Read", "Write", "Bash"]
}
})) {
@@ -78,141 +93,279 @@ The following example sets `cwd` to the process's current working directory, so
```
-Near the start of the stream, the SDK yields a system message with subtype `init`. Check its `skills` array to confirm your Skills loaded before Claude starts working. The array lists user-invocable Skills only. A Skill with [`user-invocable: false`](/docs/en/skills#control-who-invokes-a-skill) in its frontmatter loads and remains available to Claude but doesn't appear in the array.
+### Confirm skills loaded
-To enable only specific Skills, pass their names. Names match the `name` field in `SKILL.md` or the Skill's directory name. Use `plugin:skill` for plugin-provided Skills.
+Near the start of the stream, the SDK yields a system message with subtype `init`. Check its `skills` array to confirm your skills loaded before Claude starts working. The array includes the user-invocable skills that you have defined, along with [bundled skills included with Claude Code](/docs/en/skills#bundled-skills).
-
- Import statements from the first example are assumed in the following code snippets.
-
+The array lists user-invocable skills only. A skill with [`user-invocable: false`](/docs/en/skills#control-who-invokes-a-skill) in its frontmatter loads and remains available to Claude, but doesn't appear in the array. The array reflects what the session discovered and lists the same skills whether or not they're in your `skills` list.
-
- ```python Python theme={null}
- options = ClaudeAgentOptions(skills=["pdf", "docx"])
- ```
+### Allow only specific skills
+To let Claude invoke only specific skills, pass their names in the `skills` list. Names match the `name` field in `SKILL.md` or the skill's directory name. Use `plugin:skill` for plugin-provided skills.
+
+The list takes exact skill names only. If an entry can't work as an exact name, `query()` rejects the list before the session starts. See [Invalid skill name error](#invalid-skill-name-error) for the name rules and the error each SDK raises.
+
+The model doesn't see unlisted skills and the Skill tool rejects them, while their files remain on disk and stay reachable through Read and Bash. Restricting the list doesn't restrict [dispatch by name](#dispatch-commands-by-name).
+
+To let Claude invoke every discovered skill, pass `skills: "all"` rather than a wildcard.
+
+## Commands in Agent SDK sessions
+
+This section is the SDK's command documentation. A command is anything you run by sending `/` in a prompt. Entries on the command surface differ in what backs them:
+
+* **Built-in commands**: execute logic coded into the Claude Code process the SDK runs, for example `/compact`
+* **Bundled skills**: prompt artifacts included with Claude Code, for example `/code-review`
+* **Your skills**: prompt artifacts that you author, each a directory holding a `SKILL.md` file. A user-invocable skill's name joins the surface automatically, so dispatching your own `/security-check` and running a built-in work the same way
+* **Custom command files**: an older artifact form with the same behavior, flat Markdown files in `.claude/commands/` whose filenames become command names. Skills are their recommended successor
+
+By default, both you and Claude can invoke any skill. You can restrict either path through the skill's [frontmatter](/docs/en/skills#control-who-invokes-a-skill). For a definition of the two terms, see the glossary's [Command](/docs/en/glossary#command) and [Skill](/docs/en/glossary#skill) entries. See [Commands in Claude Code](/docs/en/commands) for every built-in and [Extend Claude with skills](/docs/en/skills) for the complete guide to both artifact forms.
+
+### Discover available commands
+
+You can dispatch commands that work without an interactive terminal through the SDK. The `system/init` message lists the ones available in your session in its `slash_commands` field. Commands that need an interactive terminal, such as `/theme` and `/terminal-setup`, don't appear in the list. Access the field when your session starts:
+
+
```typescript TypeScript theme={null}
- const options = { skills: ["pdf", "docx"] };
- ```
-
+ import { query } from "@anthropic-ai/claude-agent-sdk";
-The list takes exact Skill names only. In the TypeScript SDK, `query()` throws before starting the Claude Code process when a name can't work as an exact Skill name. In the Python SDK, `query()` raises `ValueError` in the same cases, for example:
+ for await (const message of query({
+ prompt: "Hello Claude",
+ options: { maxTurns: 1 }
+ })) {
+ if (message.type === "system" && message.subtype === "init") {
+ console.log("Available commands:", message.slash_commands);
+ }
+ }
+ ```
-* An empty name
-* A name containing parentheses, commas, or control characters
-* A name padded with whitespace
-* A wildcard form such as a bare `*` or a `:*` suffix
+ ```python Python theme={null}
+ import asyncio
+ from claude_agent_sdk import query, ClaudeAgentOptions, SystemMessage
-To enable every discovered Skill, pass `skills: "all"` rather than a wildcard.
-The `skills` option is a context filter, not a sandbox. Unlisted Skills are hidden from the model and rejected by the Skill tool, but their files remain on disk and are reachable through Read and Bash.
+ async def main():
+ async for message in query(prompt="Hello Claude", options=ClaudeAgentOptions(max_turns=1)):
+ if isinstance(message, SystemMessage) and message.subtype == "init":
+ print("Available commands:", message.data["slash_commands"])
-## Creating Skills
-Create each Skill as a directory containing a `SKILL.md` file with YAML frontmatter and Markdown content. The `description` field determines when Claude invokes your Skill.
+ asyncio.run(main())
+ ```
+
-**Example directory structure**:
+The printed list mixes built-in commands, bundled skills, your user-invocable skills, and `.claude/commands/` files:
```text theme={null}
-.claude/skills/processing-pdfs/
-└── SKILL.md
+Available commands: ["clear", "compact", "context", "usage", "code-review", "verify", "security-check", ...]
```
-For complete guidance on creating Skills, including SKILL.md structure, multi-file Skills, and examples, see:
+Your user-invocable skills appear in both this list and the `skills` array from [Confirm skills loaded](#confirm-skills-loaded). The `slash_commands` list adds the rest of the commands available in your session. A skill with [`user-invocable: false`](/docs/en/skills#control-who-invokes-a-skill) in its frontmatter doesn't appear in either. Sessions that configure [MCP servers](/docs/en/agent-sdk/mcp) can also expose [MCP prompts as commands](/docs/en/mcp#use-mcp-prompts-as-commands).
-* [Agent Skills in Claude Code](/docs/en/skills): complete guide with examples
-* [Agent Skills Best Practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices): authoring guidelines and naming conventions
+### Dispatch commands by name
-## Tool Restrictions
+Send a command by including it in your prompt string, the same way you send regular text. Dispatch doesn't depend on the `skills` option. Sending `/` runs a user-invocable skill even when your `skills` list omits it. Commands that act on conversation history, such as `/compact`, need prior messages to work with.
- The `allowed-tools` frontmatter field in SKILL.md is only supported when using Claude Code CLI directly. **It does not apply when using Skills through the SDK**.
-
- When using the SDK, control tool access through the main `allowedTools` option in your query configuration.
+ A command can hit the `maxTurns` / `max_turns` limit like any other prompt, ending the query with an error result instead of `success`. For the error-result contract, see [Handle the result](/docs/en/agent-sdk/agent-loop#handle-the-result). If your command might hit the limit, wrap the loop in a `try`/`catch` in TypeScript or `try`/`except` in Python, as shown in [Single Message Input](/docs/en/agent-sdk/streaming-vs-single-mode#single-message-input), or set `maxTurns` high enough for the work to complete.
-To control tool access for Skills in SDK applications, use `allowedTools` to pre-approve specific tools. Without a `canUseTool` callback, anything not in the list is denied:
+### Compact history with `/compact`
+
+The `/compact` command reduces the size of your conversation history by summarizing older messages while preserving important context. Compaction needs an existing conversation with enough prior messages to summarize. This example has a conversation first, then compacts it and reads the `compact_boundary` system message that reports the result:
+ ```typescript TypeScript theme={null}
+ import { query } from "@anthropic-ai/claude-agent-sdk";
+
+ // Compaction needs existing history, so have a conversation first
+ try {
+ for await (const message of query({
+ prompt: "Explain what this project does",
+ options: { maxTurns: 2 }
+ })) {
+ if (message.type === "result" && message.subtype === "success") {
+ console.log(message.result);
+ }
+ }
+ } catch (error) {
+ // A single-shot query() throws after yielding an error result,
+ // so the follow-up query below still runs.
+ console.error(`Session ended with an error: ${error}`);
+ }
+
+ // Compact the same conversation
+ for await (const message of query({
+ prompt: "/compact",
+ options: { continue: true, maxTurns: 1 }
+ })) {
+ if (message.type === "system" && message.subtype === "compact_boundary") {
+ console.log("Compaction completed");
+ console.log("Pre-compaction tokens:", message.compact_metadata.pre_tokens);
+ console.log("Trigger:", message.compact_metadata.trigger);
+ // Example output:
+ // Compaction completed
+ // Pre-compaction tokens: 1842
+ // Trigger: manual
+ }
+ }
+ ```
+
```python Python theme={null}
- options = ClaudeAgentOptions(
- setting_sources=["user", "project"], # Load Skills from filesystem
- skills="all",
- allowed_tools=["Read", "Grep", "Glob"],
- permission_mode="dontAsk", # Deny anything not pre-approved instead of prompting
- )
+ import asyncio
+ from claude_agent_sdk import query, ClaudeAgentOptions, ResultMessage, SystemMessage
async def main():
- async for message in query(prompt="Analyze the codebase structure", options=options):
- print(message)
+ # Compaction needs existing history, so have a conversation first
+ try:
+ async for message in query(
+ prompt="Explain what this project does",
+ options=ClaudeAgentOptions(max_turns=2),
+ ):
+ if isinstance(message, ResultMessage) and message.subtype == "success":
+ print(message.result)
+ except Exception as error:
+ # A single-shot query() raises after yielding an error result,
+ # so the follow-up query below still runs.
+ print(f"Session ended with an error: {error}")
+
+ # Compact the same conversation
+ async for message in query(
+ prompt="/compact",
+ options=ClaudeAgentOptions(continue_conversation=True, max_turns=1),
+ ):
+ if isinstance(message, SystemMessage) and message.subtype == "compact_boundary":
+ print("Compaction completed")
+ print("Pre-compaction tokens:", message.data["compact_metadata"]["pre_tokens"])
+ print("Trigger:", message.data["compact_metadata"]["trigger"])
+ # Example output:
+ # Compaction completed
+ # Pre-compaction tokens: 1842
+ # Trigger: manual
asyncio.run(main())
```
+
+
+
+ A `compact_boundary` message only arrives when compaction ran. With nothing to summarize, `/compact` reports the reason instead of raising. The run still ends with a `success` result and no `compact_boundary` message, and the result text carries the reason, for example `Not enough messages to compact.` after a single short exchange. A fresh one-shot `query()` call starts with empty context, so use this pattern in a session with prior turns, for example in [streaming input mode](/docs/en/agent-sdk/streaming-vs-single-mode) or when resuming a session.
+
+
+### Reset context with `/clear`
+The `/clear` command resets the conversation to an empty context, so subsequent prompts start with no prior conversation history. The previous conversation remains on disk. You can return to that conversation by passing its session ID to the [`resume` option](/docs/en/agent-sdk/sessions#resume-by-id).
+
+`/clear` is useful in [streaming input mode](/docs/en/agent-sdk/streaming-vs-single-mode), where you send multiple prompts over a single connection. For one-shot `query()` calls, each call already starts with empty context, so sending `/clear` has no practical effect. Start a new `query()` instead.
+
+## Create skills
+
+Create each skill as a directory containing a `SKILL.md` file with YAML frontmatter and Markdown content. The `description` field determines when Claude invokes your skill.
+
+**Example directory structure**:
+
+```text theme={null}
+.claude/skills/security-check/
+└── SKILL.md
+```
+
+### Choose a discovery level
+
+Save skills at either of the two most common [discovery levels](/docs/en/skills#where-skills-live):
+
+* **Project skills**: `.claude/skills/`, available only in the current project
+* **Personal skills**: `~/.claude/skills/`, available across all your projects
+
+If you have existing custom command files in `.claude/commands/`, they keep working. A command file at `.claude/commands/deploy.md` creates `/deploy` and works the same way as a skill at `.claude/skills/deploy/SKILL.md` would. If a command file and a skill share a name, see [Where skills live](/docs/en/skills#where-skills-live) for which one runs. The SDK loads `.claude/commands/` and `~/.claude/commands/` files from the same two scopes as skills. See [Extend Claude with skills](/docs/en/skills) for the complete guide to both artifact forms.
+
+### Create and dispatch your first skill
+
+To see the full flow, create `.claude/skills/security-check/SKILL.md`:
+
+```markdown theme={null}
+---
+name: security-check
+description: Run a security vulnerability scan
+---
+
+Analyze the codebase for security vulnerabilities including:
+- SQL injection risks
+- XSS vulnerabilities
+- Exposed credentials
+- Insecure configurations
+```
+
+Once the file exists, the skill is available through the SDK. Claude invokes it when a request matches its description, and you can dispatch it directly:
+
+
```typescript TypeScript theme={null}
+ import { query } from "@anthropic-ai/claude-agent-sdk";
+
for await (const message of query({
- prompt: "Analyze the codebase structure",
- options: {
- settingSources: ["user", "project"], // Load Skills from filesystem
- skills: "all",
- allowedTools: ["Read", "Grep", "Glob"],
- permissionMode: "dontAsk" // Deny anything not pre-approved instead of prompting
- }
+ prompt: "/security-check",
+ options: { maxTurns: 10 }
})) {
- console.log(message);
+ if (message.type === "result" && message.subtype === "success") {
+ console.log(message.result);
+ }
}
```
-
-
-## Discovering Available Skills
-To see which Skills are available in your SDK application, ask Claude. The example below sets only the `skills` option and omits `settingSources`/`setting_sources`. When you leave `settingSources`/`setting_sources` unset, the SDK still loads Skills from the user and project sources, so the `skills` option set to `"all"` on its own makes them available to list.
-
-
```python Python theme={null}
- options = ClaudeAgentOptions(skills="all")
+ import asyncio
+ from claude_agent_sdk import query, ClaudeAgentOptions, ResultMessage
async def main():
- async for message in query(prompt="What Skills are available?", options=options):
- print(message)
+ async for message in query(
+ prompt="/security-check", options=ClaudeAgentOptions(max_turns=10)
+ ):
+ if isinstance(message, ResultMessage) and message.subtype == "success":
+ print(message.result)
asyncio.run(main())
```
-
- ```typescript TypeScript theme={null}
- for await (const message of query({
- prompt: "What Skills are available?",
- options: {
- skills: "all"
- }
- })) {
- console.log(message);
- }
- ```
-Claude will list the available Skills based on your current working directory and installed plugins.
+A successful run ends with a `success` result whose text carries the scan findings. Against a small Express app with seeded issues, the result text begins:
+
+```text theme={null}
+**Security scan of `app.js` — 4 findings (most severe first):**
+
+1. **SQL Injection** (line 8) — `req.query.name` is concatenated directly into the SQL string. Trivially exploitable (`' OR '1'='1`, `'; DROP TABLE users;--`). **Fix:** use parameterized queries, e.g. `db.query("SELECT * FROM users WHERE name = ?", [req.query.name], cb)`.
+...
+```
+
+The skill's name also appears in the init message's `slash_commands` array.
+
+
+ Claude Code includes bundled `code-review` and `verify` skills. If you name a `.claude/commands/` file after one of them, for example `.claude/commands/code-review.md`, the file's command shadows the bundled skill and `slash_commands` lists the name once.
+
+
+## Pre-approve tools for skills
-## Testing Skills
+
+ For project and personal skills, the `allowed-tools` frontmatter field applies only when you use the Claude Code CLI directly. In SDK sessions, manage tool approval for these skills through the `allowedTools` option (`allowed_tools` in Python) in your query configuration. Skills [synced from claude.ai](/docs/en/skills#how-claude-code-handles-the-frontmatter-of-a-synced-skill) follow their own frontmatter rules.
+
-Test Skills by asking questions that match their descriptions:
+Skills run with the session's tools. The example below pre-approves `Read`, `Grep`, and `Glob` with `allowedTools` (`allowed_tools` in Python), so Claude can inspect files while running the [security-check skill](#create-and-dispatch-your-first-skill) without stopping for approval:
```python Python theme={null}
+ import asyncio
+
+ from claude_agent_sdk import query, ClaudeAgentOptions
+
options = ClaudeAgentOptions(
- cwd=os.getcwd(),
- setting_sources=["user", "project"], # Load Skills from filesystem
+ setting_sources=["user", "project"], # Load skills from filesystem
skills="all",
- allowed_tools=["Read", "Bash"],
+ allowed_tools=["Read", "Grep", "Glob"],
)
async def main():
- async for message in query(prompt="Extract text from invoice.pdf", options=options):
+ async for message in query(prompt="Check this project for security issues", options=options):
print(message)
@@ -220,13 +373,14 @@ Test Skills by asking questions that match their descriptions:
```
```typescript TypeScript theme={null}
+ import { query } from "@anthropic-ai/claude-agent-sdk";
+
for await (const message of query({
- prompt: "Extract text from invoice.pdf",
+ prompt: "Check this project for security issues",
options: {
- cwd: process.cwd(),
- settingSources: ["user", "project"], // Load Skills from filesystem
+ settingSources: ["user", "project"], // Load skills from filesystem
skills: "all",
- allowedTools: ["Read", "Bash"]
+ allowedTools: ["Read", "Grep", "Glob"]
}
})) {
console.log(message);
@@ -234,13 +388,15 @@ Test Skills by asking questions that match their descriptions:
```
-Claude automatically invokes the relevant Skill if the description matches your request.
+In the stream, the skill invocation appears as a Skill tool use, followed by Read calls on the project files. The run ends with a `success` result whose text carries the findings.
+
+The list pre-approves the named tools rather than restricting the others. For the full permission flow, including permission modes and the `canUseTool` callback, see [Permissions](/docs/en/agent-sdk/permissions).
## Troubleshooting
-### Skills Not Found
+### Skills not found
-**Check settingSources configuration**: Skills are discovered through the `user` and `project` setting sources. If you set `settingSources`/`setting_sources` explicitly and omit those sources, skills are not loaded:
+**Check settingSources configuration**: the SDK discovers skills through the `user` and `project` setting sources. If you set `settingSources`/`setting_sources` explicitly and omit those sources, the SDK doesn't load skills:
```python Python theme={null}
@@ -271,7 +427,7 @@ Claude automatically invokes the relevant Skill if the description matches your
For which skill directories each source loads, see the [filesystem sources table](/docs/en/agent-sdk/claude-code-features#control-filesystem-settings-with-settingsources). For more details on `settingSources`/`setting_sources`, see the [TypeScript SDK reference](/docs/en/agent-sdk/typescript#settingsource) or [Python SDK reference](/docs/en/agent-sdk/python#settingsource).
-**Check working directory**: The SDK loads Skills from `.claude/skills/` in the `cwd` option and in every parent directory up to the repository root. Ensure `cwd` points at or below the directory containing `.claude/skills/`, within the same repository:
+**Check working directory**: the SDK loads skills from `.claude/skills/` in the `cwd` option and in every parent directory up to the repository root. Ensure `cwd` points at or below the directory containing `.claude/skills/`, within the same repository:
```python Python theme={null}
@@ -293,41 +449,77 @@ For which skill directories each source loads, see the [filesystem sources table
```
-See the "Using Skills with the SDK" section above for the complete pattern.
+See [Use skills with the Agent SDK](#use-skills-with-the-agent-sdk) for the complete pattern.
**Verify filesystem location**:
```bash theme={null}
-# Check project Skills
+# Check project skills
ls .claude/skills/*/SKILL.md
-# Check personal Skills
+# Check personal skills
ls ~/.claude/skills/*/SKILL.md
```
-### Skill Not Being Used
+### Skill not being used
+
+**Check the `skills` option**: if you passed a `skills` list, confirm the skill's name is included. When Claude tries to invoke an unlisted skill, the Skill tool returns `Skill is not in this session's skills allowlist`. Add the name to your list, or dispatch the skill directly by sending `/` in a prompt, which works without listing.
+
+**Check the description**: ensure it's specific and includes relevant keywords. See [Agent Skills best practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices#writing-effective-descriptions) for guidance on writing effective descriptions.
+
+### Invalid skill name error
+
+When a name in your `skills` list can't work as an exact skill name, `query()` rejects the list before starting the Claude Code process. Names that trigger the rejection include:
+
+* An empty name
+* A name containing parentheses, commas, or control characters
+* A name padded with whitespace
+* A wildcard form such as a bare `*` or a `:*` suffix
+
+Each SDK surfaces the rejection differently:
+
+
+
+ The TypeScript SDK throws an `Error` stating the rule the entry broke. For example, `skills: ["docs:*"]` throws:
+
+ ```text theme={null}
+ Invalid skill name "docs:*": wildcard-suffix names are not allowed; list each skill by its exact name.
+ ```
+
+ An empty name reports `Skill names must be non-empty strings.`
+
+
+
+ The Python SDK raises `ValueError` stating the rule the entry broke. For example, `skills=["docs:*"]` raises:
-**Check the `skills` option**: If you passed a `skills` list, confirm the skill's name is included. Passing `[]` disables all skills.
+ ```text theme={null}
+ ValueError: Invalid skill name 'docs:*': wildcard-suffix names are not allowed; list each skill by its exact name.
+ ```
-**Check the description**: Ensure it's specific and includes relevant keywords. See [Agent Skills Best Practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices#writing-effective-descriptions) for guidance on writing effective descriptions.
+ An empty name reports `Skill names must be non-empty strings`.
+
+
-### Additional Troubleshooting
+### Additional troubleshooting
-For general Skills troubleshooting (YAML syntax, debugging, etc.), see the [Claude Code Skills troubleshooting section](/docs/en/skills#troubleshooting).
+For general skills troubleshooting, such as YAML syntax errors and debugging, see the [Claude Code skills troubleshooting section](/docs/en/skills#troubleshooting).
-## Related Documentation
+## Next steps
-### Skills Guides
+The [Claude Code skills guide](/docs/en/skills) covers authoring in depth. Its guidance applies to SDK sessions, with one exception: for project and personal skills, [Pre-approve tools for skills](#pre-approve-tools-for-skills) replaces the `allowed-tools` frontmatter field with the `allowedTools` option. Start with these sections:
-* [Agent Skills in Claude Code](/docs/en/skills): complete Skills guide with creation, examples, and troubleshooting
-* [Agent Skills Overview](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview): conceptual overview, benefits, and architecture
-* [Agent Skills Best Practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices): authoring guidelines for effective Skills
-* [Agent Skills Cookbook](https://platform.claude.com/cookbook/skills-notebooks-01-skills-introduction): example Skills and templates
+* [Frontmatter reference](/docs/en/skills#frontmatter-reference): every supported field
+* [Pass arguments to skills](/docs/en/skills#pass-arguments-to-skills): `$ARGUMENTS`, `$0`, `$1`, and skill stacking. The [full substitution table](/docs/en/skills#available-string-substitutions) adds named arguments and the `${CLAUDE_*}` variables
+* [Inject dynamic context](/docs/en/skills#inject-dynamic-context): `` !`command` `` lines that run before Claude sees the skill content
+* [Where skills live](/docs/en/skills#where-skills-live): all discovery levels, plugin namespacing, and what happens when a skill and a command file share a name
-### SDK Resources
+## Related resources
+* [Commands in Claude Code](/docs/en/commands): the full command surface, including every built-in
+* [Agent Skills overview](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview): conceptual overview, benefits, and architecture
+* [Agent Skills best practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices): authoring guidelines for effective skills
+* [Agent Skills cookbook](https://platform.claude.com/cookbook/skills-notebooks-01-skills-introduction): example skills and templates
* [Subagents in the SDK](/docs/en/agent-sdk/subagents): similar filesystem-based agents with programmatic options
-* [Commands in the SDK](/docs/en/agent-sdk/slash-commands): user-invoked commands
-* [SDK Overview](/docs/en/agent-sdk/overview): general SDK concepts
-* [TypeScript SDK Reference](/docs/en/agent-sdk/typescript): complete API documentation
-* [Python SDK Reference](/docs/en/agent-sdk/python): complete API documentation
+* [SDK overview](/docs/en/agent-sdk/overview): general SDK concepts
+* [TypeScript SDK reference](/docs/en/agent-sdk/typescript): complete API documentation
+* [Python SDK reference](/docs/en/agent-sdk/python): complete API documentation
diff --git a/content/en/docs/claude-code/agent-sdk/subagents.md b/content/en/docs/claude-code/agent-sdk/subagents.md
index 0052b7b7a..c121df19b 100644
--- a/content/en/docs/claude-code/agent-sdk/subagents.md
+++ b/content/en/docs/claude-code/agent-sdk/subagents.md
@@ -192,6 +192,8 @@ You can also define subagents as markdown files in `.claude/agents/` directories
Even without defining custom subagents, Claude can spawn the built-in `general-purpose` subagent. This is useful for delegating research or exploration tasks without creating specialized agents. Include `Agent` in `allowedTools` so these invocations auto-approve without a permission prompt.
+
+ When Claude calls the Agent tool without a `subagent_type`, it gets this built-in `general-purpose` subagent. If you set [`CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS=1`](/docs/en/env-vars), that default is gone too. Such a call then fails with `subagent_type is required: the general-purpose agent is not available in this session`. The message ends with the subagent types that are still available. Before TypeScript SDK v0.3.235 (Python SDK: bundled Claude Code before v2.1.235), the same call failed with `Agent type 'general-purpose' not found`.
## What subagents inherit
diff --git a/content/en/docs/claude-code/changelog.md b/content/en/docs/claude-code/changelog.md
index a2944e786..5c9b6da2b 100644
--- a/content/en/docs/claude-code/changelog.md
+++ b/content/en/docs/claude-code/changelog.md
@@ -10,6 +10,28 @@ This page is generated from the [CHANGELOG.md on GitHub](https://github.com/anth
Run `claude --version` to check your installed version.
+
+ * Added an optional `spellcheck` setting that underlines misspelled words in the prompt input as you type, using your installed `aspell`, `hunspell`, or `ispell`
+ * Fixed whole-prompt-cache invalidation when a language server disconnected or reconnected mid-session
+ * Fixed nested markdown list items misaligning at depth 3+ and added a hanging indent to wrapped list items in the terminal UI
+ * Fixed prompt input highlights (slash commands, keywords, mentions) appearing shifted by one or more characters in some multi-line prompts
+ * Fixed Shift+Tab inside the permission prompt's comment field approving the edit and granting session-wide edit permission instead of closing the field
+ * Fixed the Agent tool advertising a general-purpose default in sessions where that agent is unavailable: an omitted `subagent_type` there now gets a clear error listing the available agents
+ * Fixed notebook cell delete/replace approval dialogs silently omitting the existing cell content when the notebook or cell could not be read; the dialog now says why
+ * Fixed slash commands run while Claude is responding showing HTML entities instead of the actual characters
+ * Fixed the prompt footer not showing the "Update installed" restart notice after a background auto-update
+ * Fixed the expanded task list (`ctrl+t`) always starting collapsed when resuming or relaunching into a session that still has open tasks
+ * Improved memory and CPU usage while cloud sessions such as `/ultrareview` or `/autofix-pr` run in the background — their event streams are no longer re-scanned and re-rendered on every update
+ * Improved permission dialogs: display text and "don't ask again" options now always match what a grant would cover, and "don't ask again" is withheld when contents cannot be fully displayed
+ * Improved the embedded `grep` in native macOS/Linux builds: pathological patterns now fail fast instead of exhausting memory, and `-m N` with `-A/-C` prints correct context
+ * Improved the context-limit error to say when auto-compact is off and point to `/config` to re-enable it
+ * Vim mode: NORMAL mode and cursor position are now preserved when toggling the detailed transcript (ctrl+o) or closing a panel
+ * Dialogs: arrow keys and Enter pressed in quick succession now select the option you navigated to instead of the previously highlighted one
+ * `SendMessage` now refuses messages too large for cross-session delivery up front instead of silently dropping them
+ * Remote Control: `claude rc` now applies the same enterprise-gateway availability check as interactive startup
+ * \[VSCode] Fixed focus jumping between open Claude tabs on its own when a window with several Claude panels is restored or reloaded
+
+
* Added the optional `CLAUDE_CODE_PROJECT_DIR_NAME` environment variable: hosts that give each session its own config directory can choose a short name for the per-project transcript directory
* Added the `selection:clear` keybinding action, so a key can be bound to clear an in-app text selection; also works in the agents view
diff --git a/content/en/docs/claude-code/cross-session-messaging.md b/content/en/docs/claude-code/cross-session-messaging.md
index 42ae59cd5..65e69b554 100644
--- a/content/en/docs/claude-code/cross-session-messaging.md
+++ b/content/en/docs/claude-code/cross-session-messaging.md
@@ -63,7 +63,7 @@ For what the message Claude writes looks like when it arrives, including an exam
The receiving Claude reads the message between tool calls during an active turn, so a running tool is never interrupted. When the receiving session is idle, Claude Code starts a new turn with the message.
-Between two ordinary interactive sessions with default settings, Claude Code delivers the message. Delivery isn't guaranteed in every configuration, though. The receiving session checks each arriving message against its own [inbound controls](#control-inbound-messages), and the check ends in one of three outcomes:
+Between two ordinary interactive sessions with default settings, Claude Code delivers the message. Delivery isn't guaranteed in every configuration, though. Claude Code refuses a message [over the size cap](#limitations) in the sending session, before it leaves. The receiving session checks each arriving message against its own [inbound controls](#control-inbound-messages), and the check ends in one of three outcomes:
* **Delivered**: Claude Code passes the message to the receiving Claude.
* **Held**: Claude Code sets the message aside undelivered. A held message reaches Claude only when you approve it or a later mode or settings change allows it.
@@ -265,6 +265,7 @@ In a session with messaging, `/status` also shows a `Peer address` row with the
The limits here are properties of the messaging channel itself and apply wherever the feature runs. For platform and provider gaps, see [Availability](#availability) instead.
* **Plain text only**: Claude sends only plain text across sessions. Structured [agent team](/docs/en/agent-teams) protocol messages stay within a team.
+* **Same-machine message size is capped**: Claude Code refuses a message to a session on this machine once its serialized form passes about a million characters. The refusal [names the exact sizes](/docs/en/errors#message-too-large-for-cross-session-delivery). Nothing reaches the receiving session.
* **Message loops are throttled**: Claude Code rate-limits repeated messages per sender, drops identical repeats arriving within a short window, and caps accepted messages waiting for Claude to read them at 50 per session. A message loop between two sessions therefore stops on its own.
## Related resources
diff --git a/content/en/docs/claude-code/debug-your-config.md b/content/en/docs/claude-code/debug-your-config.md
index b6c5c7a61..4791451df 100644
--- a/content/en/docs/claude-code/debug-your-config.md
+++ b/content/en/docs/claude-code/debug-your-config.md
@@ -41,7 +41,7 @@ Adherence drops when an instruction is vague enough to interpret multiple ways,
Settings merge across managed, user, project, and local scopes. Managed settings apply first when present. Among the rest, the closer scope overrides the broader one in the order local, then project, then user. Some settings can also be set by command-line flags or [environment variables](/docs/en/env-vars), which act as another override layer. When a setting doesn't seem to apply, the value you set is usually being overridden by another scope or an environment variable.
-Run `/doctor` to check your configuration and installation. It reports what it finds, including invalid settings files, duplicate installations, unused extensions, and checked-in `CLAUDE.md` content Claude can derive from the codebase, then proposes fixes it applies only after you confirm. The `CLAUDE.md` trim check requires Claude Code v2.1.206 or later. Before v2.1.205, `/doctor` opened a read-only diagnostics screen and pressing `f` sent the report to Claude to fix.
+Run [`/doctor`](/docs/en/commands#all-commands) to find invalid settings files.
From the terminal, `claude doctor` prints read-only installation and settings diagnostics without starting a session.
@@ -106,7 +106,7 @@ Most configuration surprises trace back to a small set of location and syntax ru
| Subdirectory `CLAUDE.md` instructions seem ignored | Subdirectory files load on demand, not at session start | They load when Claude reads a file in that directory with the Read tool, not at launch and not when writing or creating files there. See [how CLAUDE.md files load](/docs/en/memory#how-claude-md-files-load). |
| Subagent ignores `CLAUDE.md` instructions | The built-in Explore and Plan agents skip `CLAUDE.md`. Custom subagents load it the same way the main conversation does | For Explore or Plan, restate the instruction in your delegating prompt. For a custom subagent, put critical instructions in the agent file body, which becomes the agent's system prompt. See [what loads at startup](/docs/en/sub-agents#what-loads-at-startup). |
| Cleanup logic never runs at session end | No `SessionEnd` hook configured | Add a `SessionEnd` hook in `settings.json`. See the [hook events list](/docs/en/hooks#hook-events). |
-| MCP servers in `.mcp.json` never load | File is under `.claude/` or uses Claude Desktop's config format | Project MCP config goes at the repository root as `.mcp.json`, not inside `.claude/`. See [MCP configuration](/docs/en/mcp). |
+| MCP servers in `.mcp.json` never load | File is under `.claude/`, or its servers sit under a top-level `servers` key, as in VS Code's `mcp.json`, instead of `mcpServers` | Project MCP config goes at the repository root as `.mcp.json`, not inside `.claude/`, with servers under the `mcpServers` key. See [MCP configuration](/docs/en/mcp). |
| MCP servers added under `mcpServers` in `settings.json` never appear | `settings.json` does not read an `mcpServers` key | Define project servers in `.mcp.json` at the repository root, or run `claude mcp add --scope user` for user-scoped servers. See [MCP configuration](/docs/en/mcp). |
| Project MCP server added but doesn't appear | The one-time approval prompt was dismissed | Project-scoped servers require approval. Run `/mcp` to see status and approve. |
| MCP server fails to start from some directories | `command` or `args` uses a relative file path | Use absolute paths for local scripts. Executables on your `PATH` like `npx` or `uvx` work as-is. |
diff --git a/content/en/docs/claude-code/env-vars.md b/content/en/docs/claude-code/env-vars.md
index 88bddb0b4..4af3ab585 100644
--- a/content/en/docs/claude-code/env-vars.md
+++ b/content/en/docs/claude-code/env-vars.md
@@ -188,7 +188,7 @@ Numeric variables such as timeouts, token budgets, and retry counts accept scien
| `CLAUDECODE` | Set to `1` in subprocesses Claude Code spawns (Bash and PowerShell tools, tmux sessions, [hook](/docs/en/hooks) commands, [status line](/docs/en/statusline) commands, stdio [MCP server](/docs/en/mcp) subprocesses). IDE extensions also set this in their integrated terminals. Use to detect when a script is running inside a subprocess spawned by Claude Code. To check whether the current process was spawned directly by a tool call or hook, rather than inside a stdio MCP server that Claude Code started, use `CLAUDE_CODE_CHILD_SESSION` instead |
| `CLAUDE_AFK_COUNTDOWN_MS` | How many milliseconds before auto-continue the on-screen countdown appears on an unanswered [`AskUserQuestion`](/docs/en/tools-reference) dialog. Default `20000` (20 seconds), capped at the auto-continue timeout. Has no effect unless auto-continue is on; see the [`askUserQuestionTimeout`](/docs/en/settings#available-settings) setting and `CLAUDE_AFK_TIMEOUT_MS`. Requires Claude Code v2.1.198 or later |
| `CLAUDE_AFK_TIMEOUT_MS` | How many milliseconds of idle time before an unanswered [`AskUserQuestion`](/docs/en/tools-reference) dialog auto-continues without you. Auto-continue is off by default; opt in with the [`askUserQuestionTimeout`](/docs/en/settings#available-settings) setting. This variable is an override for demos and automated tests: when set, it takes precedence over that setting and turns auto-continue on even when the setting is unset or `never`. Setting `0` doesn't turn the timeout off; it closes the dialog immediately. In v2.1.198 and v2.1.199, auto-continue was on by default with a `60000` (60 seconds) timeout. Requires Claude Code v2.1.198 or later |
-| `CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS` | Set to `1` to disable all built-in [subagent](/docs/en/sub-agents) types such as Explore and Plan. Only applies in non-interactive mode (the `-p` flag). Useful for SDK users who want a blank slate |
+| `CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS` | Set to `1` to disable all built-in [subagent](/docs/en/sub-agents) types such as Explore and Plan. Only applies in non-interactive mode (the `-p` flag). Useful for SDK users who want a blank slate. This also removes `general-purpose`, the subagent Claude Code runs when an Agent tool call omits `subagent_type`. Such a call then fails with [`subagent_type is required`](/docs/en/errors#subagent-type-is-required) |
| `CLAUDE_AGENT_SDK_MCP_NO_PREFIX` | Set to `1` to skip the `mcp____` prefix on tool names from SDK-created MCP servers. Tools use their original names. SDK usage only |
| `CLAUDE_ASYNC_AGENT_STALL_TIMEOUT_MS` | Stall timeout in milliseconds for background subagents. Default `600000` (10 minutes). The timer resets on each streaming progress event; if no progress arrives within the window, the subagent is aborted and the task is marked failed, surfacing any partial result to the parent |
| `CLAUDE_AUTOCOMPACT_PCT_OVERRIDE` | Set the percentage (1-100) of the auto-compact window at which auto-compaction triggers. Use lower values like `50` to compact earlier; the variable can't raise the threshold, so values above the default percentage are ignored. It applies only in sessions that [compact before the model's context limit](/docs/en/model-config#context-window-and-auto-compaction). Applies to both main conversations and subagents |
diff --git a/content/en/docs/claude-code/errors.md b/content/en/docs/claude-code/errors.md
index 226bbc37e..1fb3b0eb6 100644
--- a/content/en/docs/claude-code/errors.md
+++ b/content/en/docs/claude-code/errors.md
@@ -84,8 +84,12 @@ Match the message you see in your terminal to a section below.
| `Couldn't reconnect to your Remote Control session` | [Network](#couldnt-reconnect-to-your-remote-control-session) |
| `N sessions ended while this machine was offline — the environment was cleaned up on the server and can't be resumed.` | [Network](#sessions-ended-while-this-machine-was-offline) |
| `Couldn't share the transcript.` | [Network](#couldnt-share-the-transcript) |
+| `Couldn't show context usage: the remote sent a reply this version can't display` | [Network](#the-remote-sent-a-reply-this-version-cant-display) |
+| `The remote session sent a reply this version can't display` | [Network](#the-remote-sent-a-reply-this-version-cant-display) |
| `Prompt is too long` / `Input is too long for requested model` | [Request errors](#prompt-is-too-long) |
| `Prompt is too long · automatic compaction failed:` | [Request errors](#prompt-is-too-long) |
+| `Context limit reached · /compact or /clear to continue` | [Request errors](#prompt-is-too-long) |
+| `Context limit reached · /clear to continue` | [Request errors](#prompt-is-too-long) |
| `Context exceeds the ...-token limit by ... tokens` in `/context` output | [Request errors](#context-exceeds-the-token-limit) |
| `Error during compaction: Conversation too long` | [Request errors](#error-during-compaction-conversation-too-long) |
| `Request too large` | [Request errors](#request-too-large) |
@@ -136,10 +140,12 @@ Match the message you see in your terminal to a section below.
| `Plugin archive integrity check failed` | [Plugin errors](#plugin-archive-integrity-check-failed) |
| `would be spawned with zero tools — refusing` | [Tool errors](#agent-would-be-spawned-with-zero-tools) |
| `File is covered by a Read deny rule in your permission settings` | [Tool errors](#file-is-covered-by-a-read-deny-rule) |
+| `subagent_type is required: the general-purpose agent is not available in this session` | [Tool errors](#subagent-type-is-required) |
| `Error: this write left the memory index at MEMORY.md at ..., over its ... read limit` | [Tool errors](#memory-index-is-over-its-read-limit) |
| `pkill: refusing to run` | [Tool errors](#pkill-pattern-matches-the-claude-code-process) |
| `Failed to write to 's inbox — nothing was sent` | [Tool errors](#failed-to-write-to-a-teammate-inbox) |
| `Failed to write the plan approval request to the lead's inbox — plan not submitted` | [Tool errors](#failed-to-write-to-a-teammate-inbox) |
+| `Message too large for cross-session delivery` | [Tool errors](#message-too-large-for-cross-session-delivery) |
| `Can't open MCP settings while no terminal is attached to this background session` | [Background session errors](#commands-refused-in-a-background-session) |
| `Can't open MCP settings in a background session` | [Background session errors](#commands-refused-in-a-background-session) |
| `blocked because the path is spelled in a form that cannot be safely resolved` | [Background session errors](#write-or-command-blocked-because-the-path-cannot-be-safely-resolved) |
@@ -1102,6 +1108,25 @@ Claude Code shows this message in the terminal running [`claude remote-control`]
* When Claude Code lists kept worktrees under this message, pick up any uncommitted work from them
* Run `claude remote-control` to start a fresh environment
+
+ The remote sent a reply this version can't display
+
+
+`/context` shows this line in a terminal [attached to a cloud session](/docs/en/claude-code-on-the-web#send-follow-ups-from-the-cli):
+
+```text theme={null}
+Couldn't show context usage: the remote sent a reply this version can't display
+```
+
+While your terminal is attached, `/context` and `/btw` ask the cloud session for their answer. Sometimes the answer arrives in a form your terminal's Claude Code can't render. The usual cause is a version difference between the two. `/context` then shows the line above instead of the usage breakdown. `/btw` shows `The remote session sent a reply this version can't display` instead of its answer. The cloud session keeps running, and other commands still work.
+
+**What to do:**
+
+* Update Claude Code with `claude update`, reattach, and rerun the command
+* If the line still appears, run `/feedback` and name the command
+
+Before v2.1.235, this case showed a raw JavaScript error instead, such as `undefined is not an object`.
+
Couldn't share the transcript
@@ -1131,6 +1156,22 @@ The conversation plus attached files exceeds the model's context window.
Prompt is too long
```
+In an interactive session, Claude Code shows this error as:
+
+```text theme={null}
+Context limit reached · /compact or /clear to continue
+```
+
+The line names only `/clear` when [`DISABLE_COMPACT`](/docs/en/env-vars) is set. Longer forms of the error, such as the compaction-failed form below, keep the `Prompt is too long ·` wording. In `-p` output and the transcript, the text stays `Prompt is too long`.
+
+When you turned auto-compact off in your [user settings](/docs/en/settings#available-settings), the line also says so:
+
+```text theme={null}
+Context limit reached · /compact or /clear to continue · auto-compact is off · /config to turn it on
+```
+
+The **Auto-compact** toggle in `/config` writes `autoCompactEnabled` to user settings. The hint appears only when a `/config` change would take effect. For example, it doesn't appear when [`DISABLE_AUTO_COMPACT`](/docs/en/env-vars) or [`DISABLE_COMPACT`](/docs/en/env-vars) turned auto-compact off. It also doesn't appear when a higher-precedence scope, such as project or managed settings, set `autoCompactEnabled` to `false`. Nor does it appear in a terminal attached to a cloud session, where the cloud session owns auto-compact. Before v2.1.235, the line carried no auto-compact hint.
+
Amazon Bedrock reports this condition as `Input is too long for requested model.`, which Claude Code handles the same way. Before v2.1.217, Claude Code didn't recognize the Bedrock wording, so auto-compact never triggered on it and `/compact` failed with the same error.
When automatic compaction ran on this turn and failed on an underlying error, such as an unavailable model or an authentication failure, the message names that error after a separator:
@@ -1139,7 +1180,7 @@ When automatic compaction ran on this turn and failed on an underlying error, su
Prompt is too long · automatic compaction failed:
```
-Resolve the named error first; `/compact` fails on the same error until you do. Before v2.1.229, a failed automatic compaction surfaced the bare `Prompt is too long` without the cause.
+Resolve the named error first; `/compact` fails on the same error until you do. Before v2.1.229, a failed automatic compaction surfaced `Prompt is too long` without the cause.
**What to do:**
@@ -1148,13 +1189,13 @@ Resolve the named error first; `/compact` fails on the same error until you do.
* Disable MCP servers you are not using with `/mcp disable ` to remove their tool definitions from context
* Trim large `CLAUDE.md` memory files, or move instructions into [path-scoped rules](/docs/en/memory#path-specific-rules) that load only when relevant
* Subagents inherit every MCP tool definition from the parent session, which can fill their context window before the first turn. Disable MCP servers you are not using before spawning subagents.
-* Auto-compact is on by default and normally prevents this error. If you have set [`DISABLE_AUTO_COMPACT`](/docs/en/env-vars), re-enable it or run `/compact` manually before the window fills.
+* Auto-compact is on by default and normally prevents this error. If you turned it off in `/config` or with [`DISABLE_AUTO_COMPACT`](/docs/en/env-vars), turn it back on. If you keep it off, run `/compact` yourself before the window fills.
See [Explore the context window](/docs/en/context-window) for an interactive view of how context fills up.
### Context exceeds the token limit
-`/context` shows this warning at the top of its output when the conversation has grown past the model's context window. Requests fail with [`Prompt is too long`](#prompt-is-too-long) until you free space.
+`/context` shows this warning at the top of its output when the conversation has grown past the model's context window. Requests fail with [`Prompt is too long`](#prompt-is-too-long) until you free space. An interactive session shows that error as the `Context limit reached` line.
```text theme={null}
Context exceeds the 200k-token limit by 94k tokens — run /compact or /clear to continue.
@@ -1183,7 +1224,7 @@ Before v2.1.216, `/context` showed usage above 100% with no warning line explain
Error during compaction: Conversation too long. Press esc twice to go up a few messages and try again.
```
-This can happen when the window is already full at the moment auto-compact triggers, or when you run `/compact` after seeing `Prompt is too long`.
+This can happen when the window is already full at the moment auto-compact triggers, or when you run `/compact` after seeing [`Prompt is too long`](#prompt-is-too-long). In an interactive session, that error is the `Context limit reached` line.
**What to do:**
@@ -1891,6 +1932,26 @@ When Claude Code refuses the Write tool, the message ends `and cannot be written
* If Claude should be able to change the file, remove or narrow the `Read` deny rule in `/permissions` or in [settings](/docs/en/settings#permission-settings)
* If the file must stay untouched, keep the rule and add an `Edit` deny rule for the same path to block the NotebookEdit tool too
+
+ subagent\_type is required
+
+
+```text theme={null}
+subagent_type is required: the general-purpose agent is not available in this session. Available agents: ...
+```
+
+Claude called the [Agent tool](/docs/en/tools-reference#agent-tool-behavior) without a `subagent_type`, and this session has no [general-purpose subagent](/docs/en/sub-agents#built-in-subagents) to fall back on. That is the case in two setups:
+
+* [`CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS=1`](/docs/en/env-vars) is set in non-interactive mode, which removes every built-in subagent
+* The session's main-thread agent has a [`tools: Agent(...)` allowlist](/docs/en/sub-agents#restrict-which-subagents-can-be-spawned) that leaves out `general-purpose`
+
+**What to do:**
+
+* Usually nothing: the message lists the subagents the session does have, so Claude can retry with one of them
+* If Claude keeps failing, add `general-purpose` to the `tools: Agent(...)` allowlist, or unset `CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS`
+
+Before v2.1.235, the same call failed with `Agent type 'general-purpose' not found`.
+
### Memory index is over its read limit
Claude wrote to the [auto memory](/docs/en/memory#auto-memory) index `MEMORY.md` and left it over one of its read limits: 200 lines or 25KB. The write succeeded, but only the first 200 lines or 25KB, whichever comes first, load at the start of a session, so everything past the limit is dropped each time the index is read. Before v2.1.210, an over-limit index was silently truncated on the next load with no write-time signal.
@@ -1950,6 +2011,23 @@ When you message a teammate yourself, typing `@name` followed by the message in
* Ask the sender to resend the message; contention for the inbox lock is transient and clears on retry
* Check free disk space, and check that `~/.claude/teams` and the files under it are writable by your user
+### Message too large for cross-session delivery
+
+Claude's [cross-session message](/docs/en/cross-session-messaging) to another of your sessions on this machine was too long to send. Claude Code refused it, and the receiving session got nothing. The refusal appears in the sending session's tool result, not as a banner in your terminal. It names both sizes and how to make the message fit:
+
+```text wrap theme={null}
+Failed to send to api-worker: Message too large for cross-session delivery: the serialized message is 1,203,844 characters and the limit is 1,048,576. Shorten the message text — put bulk content in a file the recipient can read rather than in the message — or split it into smaller messages.
+```
+
+Resending the same text fails the same way.
+
+**What to do:**
+
+* Ask Claude to summarize the message, or to put the bulk content in a file and send the file's path
+* Ask Claude to split the content across several shorter messages
+
+Before v2.1.235, Claude Code reported an oversized message as sent. The receiving session dropped it unread.
+
## Background session errors
[Background sessions](/docs/en/agent-view) run without an interactive terminal of their own, so commands that need one behave differently there. These messages appear in the transcript of a background session, in the terminal that attaches to one, in the session or shell you dispatch from, or, for the [worktree-guard entries](#write-or-command-blocked-because-the-path-cannot-be-safely-resolved) below, in any session isolated in a worktree or running a worktree-isolated subagent; where a message is specific to one surface, its entry says so.
diff --git a/content/en/docs/claude-code/interactive-mode.md b/content/en/docs/claude-code/interactive-mode.md
index 34690c38b..0e30f6295 100644
--- a/content/en/docs/claude-code/interactive-mode.md
+++ b/content/en/docs/claude-code/interactive-mode.md
@@ -384,6 +384,103 @@ The shortcode must start the input or follow a space, so a `:` inside a word or
To turn the feature off, set [`emojiCompletionEnabled`](/docs/en/settings#available-settings) to `false` in `settings.json`. This disables both the suggestion popup and the inline replacement.
+## Check spelling as you type
+
+Claude Code can underline misspelled words in the prompt input while you type. It checks only the text in the input box, never Claude's replies or your files. It also checks nothing while the input box is in [shell mode](#shell-mode-with-prefix), `Ctrl+R` history search, or [voice dictation](/docs/en/voice-dictation).
+
+Spell checking is off by default, and Claude Code checks nothing in [screen reader mode](/docs/en/accessibility). Requires Claude Code v2.1.235 or later.
+
+### Prerequisites
+
+* Install [aspell](https://github.com/GNUAspell/aspell), [hunspell](https://github.com/hunspell/hunspell), or [ispell](https://en.wikipedia.org/wiki/Ispell) and make sure it's on your `PATH`. Claude Code runs the first of the three it finds, in that order, on every platform, including a `.cmd` shim a package manager installs on Windows.
+* To check that the program is on your `PATH`, run `aspell --version`, `hunspell --version`, or `ispell -v` in your terminal. A "command not found" error means it isn't on your `PATH` yet.
+
+### Turn spell checking on or off
+
+Claude Code reads the [`spellcheck`](/docs/en/settings#available-settings) setting from three places, and ignores it in a project's `.claude/settings.json` and `.claude/settings.local.json`. Turn it on from whichever one you use:
+
+
+
+ Add `spellcheck` to `~/.claude/settings.json`. It applies in every project you open, like the rest of your [user settings](/docs/en/settings#settings-files):
+
+ ```json theme={null}
+ {
+ "spellcheck": { "enabled": true }
+ }
+ ```
+
+
+
+ Save `spellcheck` in a JSON file, such as `spellcheck.json`:
+
+ ```json theme={null}
+ {
+ "spellcheck": { "enabled": true }
+ }
+ ```
+
+ Then pass the file to `--settings`. It applies to that session only:
+
+ ```bash theme={null}
+ claude --settings spellcheck.json
+ ```
+
+
+
+ Add `spellcheck` to one of your organization's [managed settings sources](/docs/en/permissions#managed-settings). It applies to every user who receives those settings, and they can't turn it off:
+
+ ```json theme={null}
+ {
+ "spellcheck": { "enabled": true }
+ }
+ ```
+
+
+
+To check that spell checking is on, type a misspelled word and a space. Claude Code underlines the word. If it doesn't, see [When Claude Code underlines nothing](#when-claude-code-underlines-nothing). To turn spell checking off again, set `enabled` to `false` in the same place, or remove `spellcheck`.
+
+To choose which of the three programs Claude Code runs, which dictionary it uses, or the underline color, add any of these fields next to `enabled`, in the same place:
+
+* `checker`: `aspell`, `hunspell`, or `ispell`. Claude Code doesn't fall back from a checker you name, and treats any other value as `auto`.
+* `language`: a dictionary name in your checker's form, such as `en_GB`. Claude Code ignores any value that isn't a plain dictionary name, such as a path or a name with spaces, and the checker uses its default dictionary.
+* `color`: a color name such as `yellow`, or a `#rrggbb`, `#rgb`, `rgb(r,g,b)`, `ansi256(n)`, or `ansi:` value. Claude Code uses your theme's error color by default and for any value it doesn't recognize.
+
+For example, this `spellcheck` setting runs hunspell with its `en_GB` dictionary and underlines words in yellow. It works the same in `~/.claude/settings.json`, in the file you pass to `--settings`, and in managed settings:
+
+```json theme={null}
+{
+ "spellcheck": {
+ "enabled": true,
+ "checker": "hunspell",
+ "language": "en_GB",
+ "color": "yellow"
+ }
+}
+```
+
+If more than one of the three places has a `spellcheck` setting, Claude Code uses only one of them: managed settings first, then `--settings`, then user settings. It doesn't combine fields from two places. For example, when `--settings` sets `spellcheck`, a `language` in your user settings has no effect.
+
+### What Claude Code underlines
+
+Shortly after you pause typing, Claude Code underlines the words the dictionary doesn't know. It leaves the word you're still typing alone until you move past it, and it never changes your text. It also skips text that looks like code:
+
+* Commands such as `/help`, `@` mentions, URLs, file paths, and flags such as `--verbose`
+* Words with digits, underscores, or a capital letter after the first, and text in backticks
+
+Claude Code also skips Chinese, Japanese, Korean, Thai, Lao, Khmer, and Myanmar text.
+
+Claude Code has no word list of its own: a word is misspelled when your checker says so. To stop Claude Code from underlining a word, add the word to your checker's personal dictionary, following the checker's own documentation. Claude Code picks up the new word after you restart it.
+
+### When Claude Code underlines nothing
+
+Claude Code underlines nothing when it can't keep a checker running:
+
+* No checker is installed, or the one you named in `checker` is missing
+* The checker fails twice in a row, at startup or later in the session. Claude Code restarts it after the first failure and stops checking after the second, until you restart Claude Code
+* The checker takes more than 15 seconds to answer, three times. Each time, Claude Code leaves the words it was waiting on unmarked; after the third, it stops checking until you restart Claude Code
+
+To find out which of these happened, start `claude --debug` with spell checking on and type a word. Then look for the `[spellcheck]` lines in the debug log at `~/.claude/debug/.txt`. One line names the program Claude Code started, or lists the ones it looked for and didn't find. Later lines say why it stopped. A missing-dictionary error there means the checker has no dictionary for your `language` value, or no default one when `language` is unset. Install one, or set `language` to a dictionary you have.
+
## Side questions with /btw
Use `/btw` to ask a question about your current work without adding to the conversation history.
diff --git a/content/en/docs/claude-code/mcp.md b/content/en/docs/claude-code/mcp.md
index ee81aec68..18da0a434 100644
--- a/content/en/docs/claude-code/mcp.md
+++ b/content/en/docs/claude-code/mcp.md
@@ -153,6 +153,66 @@ claude mcp add-json events-server \
The `type: "ws"` entry accepts the same `url`, `headers`, `headersHelper`, `timeout`, and `alwaysLoad` fields as `http`. Authentication is header-only, so pass a static token in `headers` or generate one at connect time with [`headersHelper`](#use-dynamic-headers-for-custom-authentication). The `claude mcp add --transport` flag doesn't accept `ws`.
+### Add a server from setup instructions written for another client
+
+MCP servers aren't specific to Claude Code, so a server's setup instructions may be written for Claude Desktop, Cursor, or another MCP client and give no `claude mcp add` command. To add the server anyway, look in those instructions for one of these three things:
+
+* **A URL** such as `https://mcp.example.com/mcp`: the server is remote.
+* **A launch command** such as `npx -y @example/mcp-server`: the server runs on your machine.
+* **An `mcpServers` JSON block**: configuration written for another client's settings file.
+
+Each is one of the inputs the four options in [Installing MCP servers](#installing-mcp-servers) take. Find the shape you have below to turn it into the command Claude Code accepts. Each command writes to [local scope](#local-scope) unless you add `--scope project` or `--scope user`.
+
+#### From a URL
+
+A URL means the server is remote. For an `https://` endpoint, add it with `--transport http`, or with `--transport sse` when the instructions say the endpoint uses SSE. For a `wss://` endpoint, use [Option 4](#option-4-add-a-remote-websocket-server) instead, since `--transport` doesn't accept `ws`:
+
+```bash theme={null}
+claude mcp add --transport http example https://mcp.example.com/mcp
+```
+
+If the instructions also give an API key or token header, pass it with `--header` as shown in [Option 1](#option-1-add-a-remote-http-server).
+
+#### From an `npx`, `uvx`, or binary command
+
+A launch command means the server runs as a local stdio process. Put the whole command after `--`, so Claude Code passes flags such as `-y` to the command that starts the server instead of reading them as its own options. Pass any environment variables the instructions ask for with `--env`, after the server name and before `--`:
+
+```bash theme={null}
+claude mcp add example --env API_KEY=your-key -- npx -y @example/mcp-server
+```
+
+[Option 3](#option-3-add-a-local-stdio-server) covers the `--` separator in full.
+
+#### From an `mcpServers` JSON block
+
+An `mcpServers` block written for another MCP client, such as Claude Desktop, uses the wrapper key and entry shape Claude Code reads. Pass `claude mcp add-json` the object inside `mcpServers`, not the wrapper. Two entries need a repair first:
+
+* **A `url` with no `type`**: add `"type": "http"`, `"type": "sse"`, or `"type": "ws"` to match the endpoint. Claude Code reads an entry with no `type` as a stdio server, so a `url` entry without a `type` fails.
+* **A key with characters other than letters, numbers, hyphens, and underscores**: pick a server name that uses only those characters. Otherwise the key is the server name.
+
+For example, this block:
+
+```json theme={null}
+{
+ "mcpServers": {
+ "example": {
+ "command": "npx",
+ "args": ["-y", "@example/mcp-server"]
+ }
+ }
+}
+```
+
+becomes this command:
+
+```bash theme={null}
+claude mcp add-json example '{"command":"npx","args":["-y","@example/mcp-server"]}'
+```
+
+[Add MCP servers from JSON configuration](#add-mcp-servers-from-json-configuration) covers shell escaping and the `--scope` flag for `add-json`. To share the server with your team instead, add `--scope project`, or add the entry under `mcpServers` in `.mcp.json` at your project root and commit it. [Project scope](#project-scope) covers how Claude Code loads and approves that file.
+
+Each `claude mcp add` and `claude mcp add-json` command prints an `Added ...` line. To check that Claude Code connected, run `claude mcp get `; [Server status](#server-status) covers the statuses it shows and the approval step for `.mcp.json` servers.
+
### Managing your servers
Once configured, you can manage your MCP servers with these commands:
diff --git a/content/en/docs/claude-code/model-config.md b/content/en/docs/claude-code/model-config.md
index 4cc44f551..25884e2be 100644
--- a/content/en/docs/claude-code/model-config.md
+++ b/content/en/docs/claude-code/model-config.md
@@ -561,7 +561,7 @@ Claude Code checks these plan requirements only when it connects to the Anthropi
To turn off 1M context, set `CLAUDE_CODE_DISABLE_1M_CONTEXT=1`. Claude Code removes 1M model variants from the model picker. On models with a native 1M window, such as Sonnet 5 and Fable 5, it also treats the model as having a 200K context window:
* With auto-compaction on, sessions compact at the 200K boundary through [auto-compaction](#set-the-auto-compact-window). Setting the auto-compact window above 200K doesn't lift the hold, because Claude Code caps that window at the model's context window.
-* With auto-compaction off, sessions stop at the 200K boundary with a [`Prompt is too long` error](/docs/en/errors#prompt-is-too-long) instead of compacting.
+* With auto-compaction off, sessions stop at the 200K boundary with the [context-limit error](/docs/en/errors#prompt-is-too-long) instead of compacting.
Before v2.1.223, Claude Code held only Sonnet 5, Opus 4.8, and Opus 5 sessions to 200K. See [environment variables](/docs/en/env-vars).
diff --git a/content/en/docs/claude-code/quickstart.md b/content/en/docs/claude-code/quickstart.md
index 219bc5ad6..f17150cc6 100644
--- a/content/en/docs/claude-code/quickstart.md
+++ b/content/en/docs/claude-code/quickstart.md
@@ -29,19 +29,19 @@ To install Claude Code, use one of the following methods:
**macOS, Linux, WSL:**
- ```bash theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}
+ ```bash theme={null}
curl -fsSL https://claude.ai/install.sh | bash
```
**Windows PowerShell:**
- ```powershell theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}
+ ```powershell theme={null}
irm https://claude.ai/install.ps1 | iex
```
**Windows CMD:**
- ```batch theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}
+ ```batch theme={null}
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```
@@ -57,7 +57,7 @@ To install Claude Code, use one of the following methods:
- ```bash theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}
+ ```bash theme={null}
brew install --cask claude-code
```
@@ -69,7 +69,7 @@ To install Claude Code, use one of the following methods:
- ```powershell theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null} theme={null}
+ ```powershell theme={null}
winget install Anthropic.ClaudeCode
```
diff --git a/content/en/docs/claude-code/settings.md b/content/en/docs/claude-code/settings.md
index bd5c057b6..1ea7f0653 100644
--- a/content/en/docs/claude-code/settings.md
+++ b/content/en/docs/claude-code/settings.md
@@ -183,7 +183,7 @@ A few keys are read once at session start and apply on the next restart instead:
### Invalid entries in managed settings
-Managed settings parse tolerantly. When a managed configuration contains an entry that fails schema validation, Claude Code strips that entry, records a warning, and enforces every remaining valid policy. A single typo cannot disable the rest of your organization's policy. Run [`/doctor`](/docs/en/debug-your-config#check-resolved-settings) to list stripped entries with their source file and field.
+Managed settings parse tolerantly. When a managed configuration contains an entry that fails schema validation, Claude Code strips that entry, records a warning, and enforces every remaining valid policy. A single typo cannot disable the rest of your organization's policy. Run [`/doctor`](/docs/en/commands#all-commands) to list stripped entries with their source file and field.
This behavior is consistent across all three delivery mechanisms: [server-managed settings](/docs/en/server-managed-settings), plist and registry policies deployed through MDM, and `managed-settings.json` files. Requires Claude Code v2.1.169 or later.
@@ -327,6 +327,7 @@ This tolerance applies only to managed settings. User, project, and local settin
| `skillListingMaxDescChars` | **Default**: `1536`. Per-skill character cap on the combined `description` and `when_to_use` text in the [skill listing](/docs/en/skills#skill-descriptions-are-cut-short) Claude sees each turn. Text longer than this is truncated. Raise to keep long descriptions intact at the cost of more context per turn; lower to fit more skills under [`skillListingBudgetFraction`](#available-settings) | `2048` |
| `skillOverrides` | Per-skill visibility overrides keyed by skill name. Value is `"on"`, `"name-only"`, `"user-invocable-only"`, or `"off"`. Lets you hide or collapse a skill without editing its SKILL.md. Does not apply to plugin skills, which are managed through `/plugin`. The `/skills` menu writes these to `.claude/settings.local.json`. See [Override skill visibility from settings](/docs/en/skills#override-skill-visibility-from-settings) | `{"legacy-context": "name-only", "deploy": "off"}` |
| `skipWebFetchPreflight` | Skip the [WebFetch domain safety check](/docs/en/data-usage#webfetch-domain-safety-check) that sends each requested hostname to `api.anthropic.com` before fetching. Set to `true` in environments that block traffic to Anthropic, such as Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry deployments with restrictive egress. When skipped, WebFetch attempts any URL without consulting the blocklist | `true` |
+| `spellcheck` | Underline misspelled words in the prompt input as you type, using a spell checker you install. Read from user settings, the `--settings` flag, and managed settings only. See [Check spelling as you type](/docs/en/interactive-mode#check-spelling-as-you-type). Requires Claude Code v2.1.235 or later | `{"enabled": true, "language": "en_GB"}` |
| `spinnerTipsEnabled` | **Default**: `true`. Show tips in the spinner while Claude is working. Set to `false` to disable tips | `false` |
| `spinnerTipsOverride` | Override spinner tips with custom strings. `tips`: array of tip strings. `excludeDefault`: if `true`, only show custom tips; if `false` or absent, custom tips are merged with built-in tips | `{ "excludeDefault": true, "tips": ["Use our internal tool X"] }` |
| `spinnerVerbs` | Customize the action verbs shown while a turn is in progress. Set `mode` to `"replace"` to use only your verbs, or `"append"` to add them to the defaults | `{"mode": "append", "verbs": ["Pondering", "Crafting"]}` |
diff --git a/content/en/docs/claude-code/skills.md b/content/en/docs/claude-code/skills.md
index a704239f2..4801d1faa 100644
--- a/content/en/docs/claude-code/skills.md
+++ b/content/en/docs/claude-code/skills.md
@@ -781,7 +781,7 @@ Each key is a skill name and each value is one of four states:
The `/skills` menu labels the `"user-invocable-only"` state `user-only`.
-As of v2.1.199, `"off"` also hides the skill from the command lists advertised to [Remote Control](/docs/en/remote-control) clients and to [Agent SDK](/docs/en/agent-sdk/slash-commands) callers, in addition to the terminal `/` menu. Invoking a hidden skill by its full name still returns the `skillOverrides` error instead of running it.
+As of v2.1.199, `"off"` also hides the skill from the command lists advertised to [Remote Control](/docs/en/remote-control) clients and to [Agent SDK](/docs/en/agent-sdk/skills#discover-available-commands) callers, in addition to the terminal `/` menu. Invoking a hidden skill by its full name still returns the `skillOverrides` error instead of running it.
A skill that is absent from `skillOverrides` is treated as `"on"`. The example below collapses one skill to its name and turns another off entirely:
diff --git a/content/en/docs/claude-code/statusline.md b/content/en/docs/claude-code/statusline.md
index 42aa8a516..73fbed602 100644
--- a/content/en/docs/claude-code/statusline.md
+++ b/content/en/docs/claude-code/statusline.md
@@ -1072,7 +1072,7 @@ Community projects like [ccstatusline](https://github.com/sirmalloc/ccstatusline
* Terminal.app does not support clickable links
-* If link text appears but isn't clickable, Claude Code may not have detected hyperlink support in your terminal. This commonly affects Windows Terminal and other emulators not in the auto-detection list. Set the `FORCE_HYPERLINK` environment variable to override detection before launching Claude Code:
+* If link text appears but isn't clickable, Claude Code may not have detected hyperlink support in your terminal. Set the `FORCE_HYPERLINK` environment variable to override detection before launching Claude Code:
```bash theme={null}
FORCE_HYPERLINK=1 claude
diff --git a/content/en/docs/claude-code/sub-agents.md b/content/en/docs/claude-code/sub-agents.md
index aca8aaf20..38365b639 100644
--- a/content/en/docs/claude-code/sub-agents.md
+++ b/content/en/docs/claude-code/sub-agents.md
@@ -85,6 +85,8 @@ Built-in subagents are registered by default in interactive sessions. To restric
* To remove only the built-in `Explore` and `Plan` subagents, set [`CLAUDE_CODE_DISABLE_EXPLORE_PLAN_AGENTS=1`](/docs/en/env-vars). Claude reads and explores files directly instead of delegating to them. Requires Claude Code v2.1.198 or later.
* In [non-interactive mode](/docs/en/headless) and the [Agent SDK](/docs/en/agent-sdk/overview), set [`CLAUDE_AGENT_SDK_DISABLE_BUILTIN_AGENTS=1`](/docs/en/env-vars) to remove all built-in types and supply only your own.
+An Agent tool call that omits `subagent_type` fails with [`subagent_type is required`](/docs/en/errors#subagent-type-is-required) when the session has no `general-purpose` subagent to fall back on.
+
Beyond these built-in subagents, you can create your own with custom prompts, tool restrictions, permission modes, hooks, and skills. The following sections show how to get started and customize subagents.
## Quickstart: create your first subagent
@@ -960,7 +962,7 @@ Some main-conversation state never reaches a non-fork subagent:
#### Resume subagents
-Each subagent invocation creates a new instance with fresh context. To continue an existing subagent's work instead of starting over, ask Claude to resume it.
+Each subagent invocation creates a new instance rather than continuing an earlier one. To continue an existing subagent's work instead of starting over, ask Claude to resume it.
Resumed subagents retain their full conversation history, including all previous tool calls, results, and reasoning. The subagent picks up exactly where it stopped rather than starting fresh.
@@ -1072,7 +1074,7 @@ Claude Code turns fork mode on by default in interactive sessions and leaves it
You can tell fork mode is on from how Claude Code handles the Agent tool:
-* Claude can spawn a fork by requesting the `fork` subagent type. When Claude doesn't request a type, it gets the [general-purpose](#built-in-subagents) subagent, and subagents spawned from a definition, such as Explore, work as usual.
+* Claude can spawn a fork by requesting the `fork` subagent type. When Claude doesn't request a type, it gets the [general-purpose](#built-in-subagents) subagent, if the session still has that type. Subagents spawned from a definition, such as Explore, work as usual.
* Claude Code runs the subagents Claude spawns in the background, forks and non-fork subagents alike, apart from the [cases that stay in the foreground](#run-subagents-in-foreground-or-background). Claude Code also removes the Agent tool's `run_in_background` parameter, so Claude can't ask for the foreground.
Set the [`CLAUDE_CODE_FORK_SUBAGENT`](/docs/en/env-vars) environment variable to override the defaults:
diff --git a/content/en/home.md b/content/en/home.md
index c51f2e6b5..4eb6083e1 100644
--- a/content/en/home.md
+++ b/content/en/home.md
@@ -95,7 +95,7 @@ with Claude"
- Try the Workbench
+ Try the API in Playground
diff --git a/content/en/intro.md b/content/en/intro.md
index 7dbac8a0c..d0c73e129 100644
--- a/content/en/intro.md
+++ b/content/en/intro.md
@@ -75,7 +75,7 @@ Anthropic provides developer tools to help you build and scale applications with
- Prototype and test prompts in your browser with the Workbench.
+ Explore and understand the API in your browser with Playground.
diff --git a/content/en/manage-claude/access-transparency.md b/content/en/manage-claude/access-transparency.md
index 08ec14e48..341ad715a 100644
--- a/content/en/manage-claude/access-transparency.md
+++ b/content/en/manage-claude/access-transparency.md
@@ -167,7 +167,7 @@ The following table lists which surfaces are covered by Access Transparency. Cov
| Claude for Enterprise (claude.ai seats) | No | Not covered |
| Claude for Work | No | Not covered |
| Claude Free, Pro, Max | No | Consumer plans are not eligible |
-| Anthropic Workbench | No | The Workbench stores data in data stores that are not covered by Access Transparency |
+| Playground (Claude Console) | No | Not covered |
| Microsoft Foundry | No | Not available |
| Amazon Bedrock, Google Cloud | No | Partner-operated platforms; refer to those platforms' transparency controls |
diff --git a/content/en/manage-claude/admin-api.md b/content/en/manage-claude/admin-api.md
index 43605f213..9c25b61f9 100644
--- a/content/en/manage-claude/admin-api.md
+++ b/content/en/manage-claude/admin-api.md
@@ -88,13 +88,13 @@ This is useful for:
There are five organization-level roles. See more details in the [API Console roles and permissions](https://support.claude.com/en/articles/10186004-api-console-roles-and-permissions) article.
-| Role | Permissions |
-| ------------------ | ----------------------------------------------------------------------------- |
-| user | Can use Workbench |
-| claude\_code\_user | Can use Workbench and [Claude Code](https://code.claude.com/docs/en/overview) |
-| developer | Can use Workbench and manage API keys |
-| billing | Can use Workbench and manage billing details |
-| admin | Can do all of the preceding, plus manage users |
+| Role | Permissions |
+| ------------------ | ------------------------------------------------------------------------------ |
+| user | Can use Playground |
+| claude\_code\_user | Can use Playground and [Claude Code](https://code.claude.com/docs/en/overview) |
+| developer | Can use Playground and manage API keys |
+| billing | Can use Playground and manage billing details |
+| admin | Can do all of the preceding, plus manage users |
Organization owners and primary owners have all admin permissions and can additionally manage admins. All references to the admin role on this page also apply to owners and primary owners.
diff --git a/content/en/manage-claude/api-and-data-retention.md b/content/en/manage-claude/api-and-data-retention.md
index 0d78c6801..6842fbd5d 100644
--- a/content/en/manage-claude/api-and-data-retention.md
+++ b/content/en/manage-claude/api-and-data-retention.md
@@ -30,7 +30,7 @@ Under a ZDR arrangement, Anthropic does not store customer prompts or responses
### What ZDR does not cover
-* **Console and Workbench:** Any usage on Claude Console or the Workbench prompt-testing interface.
+* **Claude Console:** Any usage in the Claude Console, including Playground.
* **Claude Managed Agents:** Claude Managed Agents is a stateful resource; session transcripts persist until you delete them.
* **Claude consumer products:** Claude Free, Pro, and Max plans, including when customers on those plans use Claude's web, desktop, or mobile apps or Claude Code.
* **Claude Teams and Claude Enterprise product interfaces:** These interfaces are not ZDR-eligible. The exception is Claude Code used through Claude Enterprise with ZDR enabled; see [What ZDR covers](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention#what-zdr-covers).
@@ -59,7 +59,7 @@ The Claude API supports HIPAA-ready integrations for organizations that handle p
### What HIPAA readiness does not cover
* **Claude consumer products:** Claude Free, Pro, and Max plans.
-* **Console and Workbench:** Usage through the Claude Console interface (enabling HIPAA readiness from Console settings is supported; processing PHI through the Console is not covered).
+* **Claude Console:** Usage through the Claude Console interface (enabling HIPAA readiness from Console settings is supported; processing PHI through the Console is not covered).
* **Partner-operated platforms:** Amazon Bedrock and Google Cloud's Agent Platform. Refer to those platforms' compliance documentation.
* **Claude Platform on AWS and Microsoft Foundry:** HIPAA readiness is not available on these platforms.
* **Third-party integrations:** Data processed by external tools or services connected to your application.
diff --git a/content/en/manage-claude/cmek-aws-kms.md b/content/en/manage-claude/cmek-aws-kms.md
index c5798cf2f..8811845bc 100644
--- a/content/en/manage-claude/cmek-aws-kms.md
+++ b/content/en/manage-claude/cmek-aws-kms.md
@@ -190,6 +190,8 @@ How you register the key depends on which product you use.
+ Once the key is validated, attach it to a new workspace before you send any requests to that workspace. For a workspace that already receives requests, the key can take [up to a day to take effect](https://platform.claude.com/docs/en/manage-claude/cmek#how-it-works).
+
```bash
curl -sS -X POST https://api.anthropic.com/v1/organizations/workspaces/ \
-H "x-api-key: " \
diff --git a/content/en/manage-claude/cmek-azure-key-vault.md b/content/en/manage-claude/cmek-azure-key-vault.md
index f79ce74f4..eb3beb344 100644
--- a/content/en/manage-claude/cmek-azure-key-vault.md
+++ b/content/en/manage-claude/cmek-azure-key-vault.md
@@ -199,7 +199,7 @@ How you register the key depends on which product you use.
- Once the key is validated, attach it to a workspace to enable CMEK for that workspace's data.
+ Once the key is validated, attach it to a new workspace before you send any requests to that workspace. For a workspace that already receives requests, the key can take [up to a day to take effect](https://platform.claude.com/docs/en/manage-claude/cmek#how-it-works).
```bash
curl -sS -X POST https://api.anthropic.com/v1/organizations/workspaces/ \
diff --git a/content/en/manage-claude/cmek-google-cloud-kms.md b/content/en/manage-claude/cmek-google-cloud-kms.md
index ab4457160..ada0dc309 100644
--- a/content/en/manage-claude/cmek-google-cloud-kms.md
+++ b/content/en/manage-claude/cmek-google-cloud-kms.md
@@ -191,6 +191,8 @@ How you register the key depends on which product you use.
+ Once the key is validated, attach it to a new workspace before you send any requests to that workspace. For a workspace that already receives requests, the key can take [up to a day to take effect](https://platform.claude.com/docs/en/manage-claude/cmek#how-it-works).
+
```bash
curl -sS -X POST https://api.anthropic.com/v1/organizations/workspaces/ \
-H "x-api-key: " \
diff --git a/content/en/manage-claude/cmek.md b/content/en/manage-claude/cmek.md
index 7114c63b6..d52730bef 100644
--- a/content/en/manage-claude/cmek.md
+++ b/content/en/manage-claude/cmek.md
@@ -23,7 +23,9 @@ The use of CMEK is optional. Eligible organizations can **opt in** to use custom
## How it works
-Only Organization Admins (on Claude Platform) or Owners and the Primary Owner (on Claude Enterprise) can configure CMEK. On Claude Platform, CMEK is scoped per workspace and configured with the Admin API. On Claude Enterprise, CMEK is scoped per organization and configured in [claude.ai > Organization settings > Data and privacy](https://claude.ai/admin-settings/data-privacy-controls). On either product, CMEK protects data written after the key is enabled. Existing data (prior chats, files, and sessions) remains encrypted with Anthropic-managed keys and is not re-encrypted under your key.
+Only Organization Admins (on Claude Platform) or Owners and the Primary Owner (on Claude Enterprise) can configure CMEK. On Claude Platform, CMEK is scoped per workspace and configured with the Admin API. On Claude Enterprise, CMEK is scoped per organization and configured in [claude.ai > Organization settings > Data and privacy](https://claude.ai/admin-settings/data-privacy-controls). On either product, CMEK protects data written after your key takes effect. Existing data (prior chats, files, and sessions) remains encrypted with Anthropic-managed keys and is not re-encrypted under your key.
+
+On Claude Platform, Anthropic recommends attaching your key to a new workspace before you send any requests to that workspace. If you attach a key to a workspace that already receives requests, your key can take up to a day to take effect. Data written before then, like existing data, is encrypted with Anthropic-managed keys and is not re-encrypted.
CMEK configuration events appear in the [Compliance API Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed). The key operations Anthropic performs against your key (such as wrapping and unwrapping data keys) do not appear in the Compliance API; they appear in your cloud provider's audit logs.
@@ -53,7 +55,7 @@ For minimal latency, choose a region close to Anthropic's US infrastructure:
What CMEK covers depends on which product you use.
-### Encrypted
+### Encrypted with CMEK key
**Claude Platform**
@@ -77,7 +79,7 @@ Some features are turned off or substantially modified when CMEK is enabled. Thi
**Claude Platform**
-* Workbench in the Claude Console is disabled.
+* Playground in the Claude Console is disabled.
* Portions of the Compliance API that return raw content, such as prompts, responses, and files, are disabled.
* Other beta and research preview features may not be covered by CMEK.
@@ -88,10 +90,9 @@ Some features are turned off or substantially modified when CMEK is enabled. Thi
* Certain analytics are degraded: admin analytics for claude.ai skills and connectors (under claude.ai/analytics/usage and through the [Claude Enterprise Analytics API](https://platform.claude.com/docs/en/manage-claude/analytics-api)), Claude smart reports (under claude.ai/analytics/insights), and Claude Code contribution metrics (under claude.ai/analytics/claude-code).
* Audit log exports are disabled.
* Signed URLs for temporary file exchanges are disabled. These back organization data exports in claude.ai and Claude Code Remote file flows such as screenshot updates.
-* Personal preferences are disabled for users who belong to a CMEK-protected organization, across all organizations under the same parent. Users who do not belong to a CMEK-protected organization can still use them across all organizations.
* Compliance API [local session transcripts](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions) (Cowork and Claude Code on users' machines) currently return no message content. Session metadata is listed as usual, and the local session messages endpoint (`GET /v1/compliance/apps/sessions/local/{session_id}/messages`) returns each message with its content marked unavailable; see [Retrieve a local session transcript](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-a-local-session-transcript) for the response shape.
-### Not encrypted
+### Encrypted with Anthropic key
These features remain available, but their data is not encrypted under your key. You can disable any feature that is not appropriate for your use case in **Settings**.
@@ -107,6 +108,7 @@ These features remain available, but their data is not encrypted under your key.
* Claude Code Desktop, Claude Code on the web, and Claude in Slack. Anthropic recommends disabling any of these that are not appropriate for your use case in the admin console.
* Beta and research preview features may not be covered by CMEK and can break in CMEK organizations, for example, Claude Security and Claude Design.
* On-demand data export under **Settings** > **Privacy**.
+* [Personal preferences - Instructions for Claude section](https://claude.ai/new#settings/general). These are set at the account level and shared across all of a user's organizations.
On both products, account data for users in your organization (such as names, email addresses, and profile pictures) is not encrypted under your key.
@@ -140,7 +142,7 @@ Outside of [CSAM screening](https://support.claude.com/en/articles/9020328-csam-
## Limitations
* **Irreversible action:** Once a key is attached to a workspace, it cannot be detached or swapped. On Claude Platform, attaching a key also locks the workspace's data retention setting: you cannot turn off 30-day data retention for that workspace, and returning to zero data retention requires creating a new workspace and moving your traffic to it. Rotating the key material within the same key (for example, AWS KMS automatic rotation, a Cloud KMS rotation schedule, or an Azure Key Vault rotation policy) is supported transparently and requires no change in Anthropic. Switching to a *different* key requires creating a new workspace with the new key and migrating your data. Revoking or disabling the key makes all CMEK-protected data in that workspace permanently inaccessible, with no backout path.
-* **No retroactive encryption:** CMEK only protects data written after the key is enabled.
+* **No retroactive encryption:** CMEK only protects data written after your key takes effect (see [How it works](https://platform.claude.com/docs/en/manage-claude/cmek#how-it-works)).
* **Latency:** Operations that wrap or unwrap data keys make a round-trip to your key management service, which can add a small amount of latency to actions that read or write data at rest.
* **Revocation delay:** Key revocation can take up to 1 hour (the cache TTL). Requests already in flight during that window may continue to succeed.
* **KMS costs:** CMEK requires a key in a third-party key management service (AWS KMS, Google Cloud KMS, or Azure Key Vault), which may incur separate charges billed by your KMS provider.
diff --git a/content/en/manage-claude/usage-cost-api.md b/content/en/manage-claude/usage-cost-api.md
index d78422a2f..a69211024 100644
--- a/content/en/manage-claude/usage-cost-api.md
+++ b/content/en/manage-claude/usage-cost-api.md
@@ -310,9 +310,9 @@ Code execution costs appear in the cost endpoint grouped under `Code Execution U
Filter or group by `service_tier` in the usage endpoint and look for the `priority` value. Priority Tier costs are not available in the cost endpoint.
-### What happens with Anthropic Workbench usage?
+### What happens with Playground usage?
-API usage from the Workbench is not associated with an API key, so `api_key_id` will be `null` even when grouping by that dimension.
+API usage from Playground in the Claude Console (and from the legacy Workbench before it) is not associated with an API key, so `api_key_id` will be `null` even when grouping by that dimension.
### How is the default workspace represented?
diff --git a/content/en/manage-claude/wif-providers/aws.md b/content/en/manage-claude/wif-providers/aws.md
index 6f698d602..ffb74c06e 100644
--- a/content/en/manage-claude/wif-providers/aws.md
+++ b/content/en/manage-claude/wif-providers/aws.md
@@ -431,7 +431,7 @@ curl -sS https://api.anthropic.com/v1/oauth/token \
}" | jq
```
-A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common AWS-side cause is an `iss` mismatch (the per-account STS issuer URL must match the registered `issuer_url` exactly).
+A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason and see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common AWS-side cause is an `iss` mismatch (the per-account STS issuer URL must match the registered `issuer_url` exactly).
## Use EKS projected service-account tokens
@@ -785,7 +785,7 @@ curl -sS https://api.anthropic.com/v1/oauth/token \
}" | jq
```
-A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common EKS-side cause is the projected token's `aud` not matching the rule (project a token with `audience: https://api.anthropic.com`, not the IRSA default `sts.amazonaws.com`).
+A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason and see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common EKS-side cause is the projected token's `aud` not matching the rule (project a token with `audience: https://api.anthropic.com`, not the IRSA default `sts.amazonaws.com`).
## Scope your rule
diff --git a/content/en/manage-claude/wif-providers/azure.md b/content/en/manage-claude/wif-providers/azure.md
index 5581b12ce..7bc86a4bf 100644
--- a/content/en/manage-claude/wif-providers/azure.md
+++ b/content/en/manage-claude/wif-providers/azure.md
@@ -109,7 +109,7 @@ The wizard creates these resources for you. Use the following values whether you
```
- Managed identity workloads need `max_jwt_lifetime_seconds: 86400`. Azure issues managed identity tokens with up to 24 hours between `iat` and `exp` because it caches each resource's token for that window and offers no way to force an early refresh, and the issuer's 1-hour default rejects those tokens with `invalid_grant`. The Connect workload wizard's Microsoft Entra tile creates the issuer with `max_jwt_lifetime_seconds` set to `7500` and provides no field to change it during creation, so finish the wizard, then open **Settings → Workload identity → Issuers**, edit the issuer, and raise the value to `86400`. You can also update the issuer through the Admin API.
+ Managed identity workloads need `max_jwt_lifetime_seconds: 86400`. Azure issues managed identity tokens with up to 24 hours between `iat` and `exp` because it caches each resource's token for that window and offers no way to force an early refresh, and the issuer's 1-hour default rejects those tokens, so the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`). The Connect workload wizard's Microsoft Entra tile creates the issuer with `max_jwt_lifetime_seconds` set to `7500` and provides no field to change it during creation, so finish the wizard, then open **Settings → Workload identity → Issuers**, edit the issuer, and raise the value to `86400`. You can also update the issuer through the Admin API.
A longer accepted lifetime means a leaked Entra token stays exchangeable for longer. If a token leaks, the lever is disabling the federation rule; a tight `oid` match limits which identities can exchange a token in the first place, as described in [Scope your rule](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#scope-your-rule).
@@ -583,7 +583,7 @@ The samples fetch the managed identity token from the platform's token endpoint:
### Verify the setup
-From your Azure resource, run the cURL exchange shown in [Acquire and use the token](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#acquire-and-use-the-token) and confirm that `POST /v1/oauth/token` returns a `200` with an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, decode the Entra token (see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange) for the command) and check the most common Azure-side causes:
+From your Azure resource, run the cURL exchange shown in [Acquire and use the token](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#acquire-and-use-the-token) and confirm that `POST /v1/oauth/token` returns a `200` with an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason, then decode the Entra token (see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange) for the command) and check the most common Azure-side causes:
* **Issuer mismatch:** The registered `issuer_url` must match the token's `iss` claim exactly. A v2.0 token carries `https://login.microsoftonline.com//v2.0`; if the decoded `ver` claim is `1.0`, see [If your tokens are v1.0](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#if-your-tokens-are-v1-0).
* **Token lifetime:** Managed identity tokens carry up to 24 hours between `iat` and `exp`. If the issuer still has the wizard's `7500` (or the 1-hour default), raise `max_jwt_lifetime_seconds` to `86400` as described in [Configure Anthropic](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#configure-anthropic).
@@ -726,7 +726,7 @@ The wizard creates these resources for you. Use the following values whether you
```
- The Connect workload wizard's Microsoft Entra tile creates the issuer with `max_jwt_lifetime_seconds` set to `7500` (just over 2 hours), which covers the default 60 to 90 minute lifetime of `client_credentials` tokens. A tenant token-lifetime policy or Continuous Access Evaluation (CAE) can extend that lifetime. If your decoded token's `exp` minus `iat` exceeds 7500 seconds, edit the issuer in **Settings → Workload identity → Issuers** and raise `max_jwt_lifetime_seconds` to match, or exchanges fail with `invalid_grant`. If your tenant also runs managed-identity workloads from [Use a managed identity](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#use-a-managed-identity), use that section's `86400` value, which covers both paths.
+ The Connect workload wizard's Microsoft Entra tile creates the issuer with `max_jwt_lifetime_seconds` set to `7500` (just over 2 hours), which covers the default 60 to 90 minute lifetime of `client_credentials` tokens. A tenant token-lifetime policy or Continuous Access Evaluation (CAE) can extend that lifetime. If your decoded token's `exp` minus `iat` exceeds 7500 seconds, edit the issuer in **Settings → Workload identity → Issuers** and raise `max_jwt_lifetime_seconds` to match, or exchanges fail with the opaque `401` `authentication_error` response (message `Authentication failed`). If your tenant also runs managed-identity workloads from [Use a managed identity](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#use-a-managed-identity), use that section's `86400` value, which covers both paths.
A longer accepted lifetime means a leaked Entra token stays exchangeable for longer. If a token leaks, the lever is disabling the federation rule; a tight `oid` match limits which identities can exchange a token in the first place, as described in [Scope your rule](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#scope-your-rule).
@@ -1172,7 +1172,7 @@ Two different client IDs appear in the samples. `` is the audience app r
### Verify the setup
-From inside a labeled pod, run the cURL exchange shown in [Acquire and use the token](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#acquire-and-use-the-token-2) and confirm that `POST /v1/oauth/token` returns a `200` with an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, decode the Entra-issued token from step 1 (see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange) for the command) and check the most common Azure-side causes:
+From inside a labeled pod, run the cURL exchange shown in [Acquire and use the token](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#acquire-and-use-the-token-2) and confirm that `POST /v1/oauth/token` returns a `200` with an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason, then decode the Entra-issued token from step 1 (see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange) for the command) and check the most common Azure-side causes:
* **Issuer mismatch:** The registered `issuer_url` must match the token's `iss` claim exactly. A v2.0 token carries `https://login.microsoftonline.com//v2.0`; if the decoded `ver` claim is `1.0`, see [If your tokens are v1.0](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#if-your-tokens-are-v1-0).
* **Token lifetime:** If a tenant token-lifetime policy or CAE extends the `client_credentials` token past 7500 seconds, raise the issuer's `max_jwt_lifetime_seconds` as described in [Configure Anthropic](https://platform.claude.com/docs/en/manage-claude/wif-providers/azure#configure-anthropic-2).
diff --git a/content/en/manage-claude/wif-providers/gcp.md b/content/en/manage-claude/wif-providers/gcp.md
index 9279813a7..9fa3a2df1 100644
--- a/content/en/manage-claude/wif-providers/gcp.md
+++ b/content/en/manage-claude/wif-providers/gcp.md
@@ -429,7 +429,7 @@ curl -sS -H "Metadata-Flavor: Google" \
| jq -rR 'split(".")[1] | gsub("-";"+") | gsub("_";"/") | @base64d | fromjson'
```
-Check that `iss` is `https://accounts.google.com`, `aud` is `https://api.anthropic.com`, and `email` matches the value in your federation rule. Then run the exchange from the previous section. A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common Google Cloud-side cause is the `email` claim missing (request the token with `format=full` so it is included).
+Check that `iss` is `https://accounts.google.com`, `aud` is `https://api.anthropic.com`, and `email` matches the value in your federation rule. Then run the exchange from the previous section. A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason and see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common Google Cloud-side cause is the `email` claim missing (request the token with `format=full` so it is included).
## Scope your rule
diff --git a/content/en/manage-claude/wif-providers/github-actions.md b/content/en/manage-claude/wif-providers/github-actions.md
index 31b7166ff..eaf95121c 100644
--- a/content/en/manage-claude/wif-providers/github-actions.md
+++ b/content/en/manage-claude/wif-providers/github-actions.md
@@ -312,7 +312,7 @@ Each GitHub-issued identity token expires roughly five minutes after issuance. T
## Verify the setup
-A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common GitHub Actions-side cause is the `sub` claim format not matching (its trailing segment varies between `ref:...`, `environment:...`, and `pull_request` events).
+A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. A denied exchange returns an opaque `401` `authentication_error` with the fixed message `Authentication failed`, whichever check failed; in most cases the deny reason is recorded on the attempt's entry in the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history), and [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange) walks the checks in order. The most common GitHub Actions-side cause is the `sub` claim format not matching (its trailing segment varies between `ref:...`, `environment:...`, and `pull_request` events); the history entry shows reason `match_subject_prefix`.
## Restrict which workflows can authenticate
diff --git a/content/en/manage-claude/wif-providers/kubernetes.md b/content/en/manage-claude/wif-providers/kubernetes.md
index c43f0b111..4270389d1 100644
--- a/content/en/manage-claude/wif-providers/kubernetes.md
+++ b/content/en/manage-claude/wif-providers/kubernetes.md
@@ -290,7 +290,7 @@ The pod spec in [Configure Kubernetes](https://platform.claude.com/docs/en/manag
## Verify the setup
-A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common Kubernetes-side cause is a JWKS key mismatch (for `inline` mode, re-fetch with `kubectl get --raw /openid/v1/jwks` and update the issuer).
+A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason and see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common Kubernetes-side cause is a JWKS key mismatch (for `inline` mode, re-fetch with `kubectl get --raw /openid/v1/jwks` and update the issuer).
## Scope your rule
diff --git a/content/en/manage-claude/wif-providers/okta.md b/content/en/manage-claude/wif-providers/okta.md
index 9edceeb4b..a1e5835de 100644
--- a/content/en/manage-claude/wif-providers/okta.md
+++ b/content/en/manage-claude/wif-providers/okta.md
@@ -456,7 +456,7 @@ Each SDK tab shows the callable pattern: the Anthropic SDK calls your identity-t
## Verify the setup
-A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. On `400 invalid_grant`, see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common Okta-side cause is an `issuer_url` mismatch (it must include the `/oauth2/` path; the Okta org authorization server is not usable).
+A successful exchange returns an `access_token` beginning with `sk-ant-oat01-` and an `expires_in` value in seconds. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason and see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange); the most common Okta-side cause is an `issuer_url` mismatch (it must include the `/oauth2/` path; the Okta org authorization server is not usable).
## Scope your rule
diff --git a/content/en/manage-claude/wif-providers/spiffe.md b/content/en/manage-claude/wif-providers/spiffe.md
index d67062966..da3401c89 100644
--- a/content/en/manage-claude/wif-providers/spiffe.md
+++ b/content/en/manage-claude/wif-providers/spiffe.md
@@ -460,7 +460,7 @@ spire-agent api fetch jwt \
| jq -rR 'split(".")[1] | gsub("-";"+") | gsub("_";"/") | @base64d | fromjson'
```
-The `-output json` flag returns the SVID response and bundle response as a two-element JSON array, so `jq -r '.[0].svids[0].svid'` extracts the bare token. On older SPIRE versions without `-output`, the command prints a labeled block instead. In that case, pipe the default output through `awk '/^[[:space:]]*eyJ/{print $1; exit}'` to extract the token line. Check that `iss` is the OIDC Discovery Provider URL you registered, `sub` is the workload's SPIFFE ID, and `aud` contains `https://api.anthropic.com`. Then run the cURL example from [Acquire and use the token](https://platform.claude.com/docs/en/manage-claude/wif-providers/spiffe#acquire-and-use-the-token). A successful exchange returns an `access_token` beginning with `sk-ant-oat01-`. On `400 invalid_grant`, see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange). The most common SPIRE-side cause is a mismatch between SPIRE Server's `jwt_issuer` and the URL registered as the federation issuer.
+The `-output json` flag returns the SVID response and bundle response as a two-element JSON array, so `jq -r '.[0].svids[0].svid'` extracts the bare token. On older SPIRE versions without `-output`, the command prints a labeled block instead. In that case, pipe the default output through `awk '/^[[:space:]]*eyJ/{print $1; exit}'` to extract the token line. Check that `iss` is the OIDC Discovery Provider URL you registered, `sub` is the workload's SPIFFE ID, and `aud` contains `https://api.anthropic.com`. Then run the cURL example from [Acquire and use the token](https://platform.claude.com/docs/en/manage-claude/wif-providers/spiffe#acquire-and-use-the-token). A successful exchange returns an `access_token` beginning with `sk-ant-oat01-`. If the exchange fails with the opaque `401` `authentication_error` response (message `Authentication failed`), check the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) for the deny reason and see [Troubleshoot a failed exchange](https://platform.claude.com/docs/en/manage-claude/wif-reference#troubleshoot-a-failed-exchange). The most common SPIRE-side cause is a mismatch between SPIRE Server's `jwt_issuer` and the URL registered as the federation issuer.
## Scope your rule
diff --git a/content/en/manage-claude/wif-reference.md b/content/en/manage-claude/wif-reference.md
index e1768cf57..fa56e4ca3 100644
--- a/content/en/manage-claude/wif-reference.md
+++ b/content/en/manage-claude/wif-reference.md
@@ -216,17 +216,18 @@ claims.sub.startsWith("repo:acme-corp/") && claims.ref in ["refs/heads/main", "r
`POST /v1/oauth/token` returns errors in the standard [API error shape](https://platform.claude.com/docs/en/api/errors). The SDK wraps exchange failures in a typed `FederationExchangeError` (or language equivalent) that exposes the HTTP status, the response body, and the `request_id`.
-| Status | Error | Cause | Resolution |
-| ------ | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 400 | `invalid_request` | `federation_rule_id` is malformed or a required request field is missing. | Verify the `fdrl_` ID and that the request body includes all required fields. |
-| 400 | `invalid_request` | `workspace_id_required`: the federation rule is enabled for more than one workspace and the request omits `workspace_id`. | Set `ANTHROPIC_WORKSPACE_ID` (or the `workspace_id` body field on a raw request) to the `wrkspc_...` ID you want the token scoped to. See [Token exchange request](https://platform.claude.com/docs/en/manage-claude/wif-reference#token-exchange-request). |
-| 400 | `invalid_grant` | The JWT `iss` claim does not equal the registered `issuer_url` exactly. | Compare byte-for-byte, including trailing slashes and scheme: `jq -rR 'split(".")[1] \| gsub("-";"+") \| gsub("_";"/") \| @base64d \| fromjson \| .iss' <<< "$JWT"`. |
-| 400 | `invalid_grant` | JWKS fetch failed, JWKS is stale, or the JWT was signed with a key not in the JWKS. | For `inline` mode, update the issuer with the rotated keys. For `discovery` and `explicit_url`, confirm the JWKS endpoint is reachable on port 443; if the issuer recently rotated its signing key, see [Key rotation and caching](https://platform.claude.com/docs/en/manage-claude/wif-reference#key-rotation-and-caching). |
-| 400 | `invalid_grant` | The JWT `exp` claim is in the past (beyond the 30-second skew window). | Confirm your identity provider is projecting a fresh token and the SDK is re-reading the token file. |
-| 400 | `invalid_grant` | The JWT was verified but its claims do not satisfy the rule's `match` block. | Decode the JWT and compare each claim against the rule. `subject_prefix` is case-sensitive. `audience` requires an exact element match. |
-| 400 | `invalid_grant` | The `federation_rule_id` does not exist, is archived, or the JWT is not authorized for it (consolidated to prevent enumeration). | Confirm the rule ID in the Claude Console and that the rule has not been archived. |
-
-All `invalid_grant` failures return HTTP 400; the specific cause is logged server-side only and not exposed in the response.
+| Status | Error | Cause | Resolution |
+| ------ | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 400 | `invalid_request_error` | `federation_rule_id` is malformed or a required request field is missing. | Verify the `fdrl_` ID and that the request body includes all required fields. |
+| 400 | `invalid_request_error` | `workspace_id` is present but is not a well-formed `wrkspc_...` ID or the literal `default`. | Fix the `workspace_id` value; the response message names the expected format. |
+| 401 | `authentication_error` | The JWT `iss` claim does not equal the registered `issuer_url` exactly. | Compare byte-for-byte, including trailing slashes and scheme: `jq -rR 'split(".")[1] \| gsub("-";"+") \| gsub("_";"/") \| @base64d \| fromjson \| .iss' <<< "$JWT"`. |
+| 401 | `authentication_error` | JWKS fetch failed, JWKS is stale, or the JWT was signed with a key not in the JWKS. | For `inline` mode, update the issuer with the rotated keys. For `discovery` and `explicit_url`, confirm the JWKS endpoint is reachable on port 443; if the issuer recently rotated its signing key, see [Key rotation and caching](https://platform.claude.com/docs/en/manage-claude/wif-reference#key-rotation-and-caching). |
+| 401 | `authentication_error` | The JWT `exp` claim is in the past (beyond the 30-second skew window). | Confirm your identity provider is projecting a fresh token and the SDK is re-reading the token file. |
+| 401 | `authentication_error` | The JWT was verified but its claims do not satisfy the rule's `match` block. | Decode the JWT and compare each claim against the rule. `subject_prefix` is case-sensitive. `audience` requires an exact element match. |
+| 401 | `authentication_error` | The `federation_rule_id` does not exist, is archived, or the JWT is not authorized for it (consolidated to prevent enumeration). | Confirm the rule ID in the Claude Console and that the rule has not been archived. |
+| 401 | `authentication_error` | The federation rule is enabled for more than one workspace and the request omits `workspace_id`. The authentication history entry shows reason `workspace_id_required`. | Set `ANTHROPIC_WORKSPACE_ID` (or the `workspace_id` body field on a raw request) to the `wrkspc_...` ID you want the token scoped to. See [Token exchange request](https://platform.claude.com/docs/en/manage-claude/wif-reference#token-exchange-request). |
+
+Every assertion denial returns the same opaque `401` `authentication_error` with the fixed message `Authentication failed`, regardless of which check failed; a distinguishable error would let a caller probe rule configuration. The deny reason is recorded on the attempt's entry in the [authentication history](https://platform.claude.com/settings/workload-identity-federation?tab=history), for example `match_subject_prefix` when the `sub` claim fails the rule's `subject_prefix`, or `workspace_id_required` when the rule spans multiple workspaces and the request names none. Requests rejected before the rule's organization is corroborated (the `400 invalid_request_error` family above) leave no history entry; their response messages name the problem directly. A `401` with no matching history entry usually means the `federation_rule_id` itself was not recognized.
### Common SDK-side failures
@@ -240,7 +241,7 @@ All `invalid_grant` failures return HTTP 400; the specific cause is logged serve
## Troubleshoot a failed exchange
-A `400 invalid_grant` response is intentionally opaque; the specific cause is logged server-side only.
+A `401` `authentication_error` response is intentionally opaque and its message is always `Authentication failed`; the deny reason is recorded in the authentication history, not in the response.
Start with the [authentication history page](https://platform.claude.com/settings/workload-identity-federation?tab=history) in the Claude Console. Recent exchange attempts surface the issuer and rule that were evaluated, the JWT claims that were inspected, and which validation step failed, which usually short-circuits the following checks.
diff --git a/content/en/manage-claude/workspaces.md b/content/en/manage-claude/workspaces.md
index ec46818e0..09f94d85d 100644
--- a/content/en/manage-claude/workspaces.md
+++ b/content/en/manage-claude/workspaces.md
@@ -38,7 +38,7 @@ Members can have different roles in each workspace, allowing fine-grained access
| Role | Permissions |
| --------------------------- | ----------------------------------------------------------------------------------------------- |
-| Workspace User | Use the Anthropic Workbench only |
+| Workspace User | Use Playground only |
| Workspace Limited Developer | Create and manage API keys, use the API. Cannot access session tracing views or download files. |
| Workspace Developer | Create and manage API keys, use the API |
| Workspace Admin | Full control over workspace settings and members |
diff --git a/content/en/release-notes/overview.md b/content/en/release-notes/overview.md
index 46666e8be..aab713921 100644
--- a/content/en/release-notes/overview.md
+++ b/content/en/release-notes/overview.md
@@ -10,6 +10,10 @@ description: Updates to the Claude Platform, including the Claude API, client SD
For updates to Claude Code, see the [complete CHANGELOG.md](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md) in the `claude-code` repository.
+### August 18, 2026
+
+* Workbench is now [**Playground**](https://platform.claude.com/playground) in the Claude Console. Playground supports every Messages API parameter and includes templates that demonstrate API features such as code execution and web search. It shows the full SDK request and the API response for each run, to help you understand the API and build with it. For more, see the [Claude Help Center](https://support.claude.com/en/articles/8606378-how-do-i-use-playground) or try it at [platform.claude.com/playground](https://platform.claude.com/playground).
+
### August 11, 2026
* The [Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api) now returns transcripts of Cowork and Claude Code sessions that run on your users' machines, in beta for Claude Enterprise organizations. `GET /v1/compliance/apps/sessions/local` lists sessions across your organization, `GET /v1/compliance/apps/sessions/local/{session_id}` retrieves one session's metadata, and `GET /v1/compliance/apps/sessions/local/{session_id}/messages` returns its transcript, all with your existing Compliance Access Key and the `read:compliance_user_data` scope. See [Sessions on users' machines](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions).
diff --git a/content/github/claude-plugins-official/.claude-plugin/marketplace.json b/content/github/claude-plugins-official/.claude-plugin/marketplace.json
index cde7096b2..d527f620e 100644
--- a/content/github/claude-plugins-official/.claude-plugin/marketplace.json
+++ b/content/github/claude-plugins-official/.claude-plugin/marketplace.json
@@ -386,7 +386,7 @@
"url": "https://github.com/aws/agent-toolkit-for-aws.git",
"path": "plugins/aws-agents",
"ref": "main",
- "sha": "957cf377ea1dffccf1f8a54ded2be8666b6db41c"
+ "sha": "f986ec60a09a9fbcc31e950ecb6ec3d07d7fa9ec"
},
"homepage": "https://github.com/aws/agent-toolkit-for-aws"
},
@@ -689,7 +689,7 @@
"url": "https://github.com/carta/plugins.git",
"path": "plugins/carta-cap-table",
"ref": "main",
- "sha": "2a1d7ff578cbe26ad734b2afab931c24a6d32540"
+ "sha": "a26da2682642a04a5ddb0bffd89c596bb931230b"
},
"homepage": "https://carta.com"
},
@@ -705,7 +705,7 @@
"url": "https://github.com/carta/plugins.git",
"path": "plugins/carta-crm",
"ref": "main",
- "sha": "37b9d30cf11965c4d7e4629e72acb29f716f2989"
+ "sha": "a9f9af826bcc6319a50cd776d9410da64eb6ae90"
},
"homepage": "https://carta.com"
},
@@ -721,7 +721,7 @@
"url": "https://github.com/carta/plugins.git",
"path": "plugins/carta-investors",
"ref": "main",
- "sha": "9aec72dafd243759daa6df098225524a288a3f65"
+ "sha": "6a712b6d35742a7c20e4b46f2112d9f306661b9e"
},
"homepage": "https://carta.com"
},
@@ -1030,7 +1030,7 @@
"source": {
"source": "url",
"url": "https://github.com/CodSpeedHQ/codspeed.git",
- "sha": "745dc9a7b5aabd7a88090d7c550f22281b17ba7d"
+ "sha": "f85b328f2224e5ba115426b70bbab6701f3c1996"
},
"homepage": "https://codspeed.io"
},
@@ -1115,7 +1115,7 @@
"source": {
"source": "url",
"url": "https://github.com/crowdsecurity/crowdsec-skill.git",
- "sha": "2aa905ef2cfc025b6bb2d8085c9568910a09680a"
+ "sha": "f406fab58ee2cba4da256e82a2febe0d16bdc1e2"
},
"homepage": "https://www.crowdsec.net"
},
@@ -1267,7 +1267,7 @@
"source": {
"source": "url",
"url": "https://github.com/datadog-labs/claude-code-plugin.git",
- "sha": "c5c062abba0df33f6bfc2c0fd0f8d17857e3fa2c"
+ "sha": "cd4aedbcddf9473ef1d37c6d6d13e7c771df5242"
},
"homepage": "https://www.datadoghq.com/"
},
@@ -1281,7 +1281,7 @@
"source": {
"source": "url",
"url": "https://github.com/datahub-project/datahub-skills.git",
- "sha": "c3c76a6d26d7ed61cb875219ffa82a50cd144a93"
+ "sha": "8d8f0e87efc48f529ce06dcccbb13e9df932b7c3"
},
"homepage": "https://datahub.com"
},
@@ -1444,7 +1444,7 @@
"source": {
"source": "url",
"url": "https://github.com/exa-labs/exa-mcp-server.git",
- "sha": "c42a8a0bfe8f75eaf386e5bf278dd78eea56f9dc"
+ "sha": "66bacbe4afd35a7e1671be9ab55c2b6bf60aff34"
},
"homepage": "https://exa.ai/docs/reference/exa-mcp"
},
@@ -1468,7 +1468,7 @@
"url": "https://github.com/expo/skills.git",
"path": "plugins/expo",
"ref": "main",
- "sha": "0814f2c6375f873b07f144c93e855198915d5426"
+ "sha": "d1c68a21ec6a9249cfd2e3885364bb47b243adb2"
},
"homepage": "https://github.com/expo/skills/blob/main/plugins/expo/README.md"
},
@@ -1534,7 +1534,7 @@
"source": {
"source": "url",
"url": "https://github.com/firecrawl/firecrawl-claude-plugin.git",
- "sha": "2bd148f07c6d7240794e636ef89ced230cc3fd89"
+ "sha": "109f8bd4bdc37825106d5943a59dd72ece3cf094"
},
"homepage": "https://github.com/firecrawl/firecrawl-claude-plugin.git"
},
@@ -1629,7 +1629,7 @@
"source": {
"source": "url",
"url": "https://github.com/gemini-cli-extensions/google-cloud-storage.git",
- "sha": "fd5bfad63f86b4f314e9faafe1a0f317be0b3a55"
+ "sha": "7b4a44e40e65f9926f5e88fcee912432e5a791d4"
},
"homepage": "https://cloud.google.com/storage"
},
@@ -1771,7 +1771,7 @@
"source": {
"source": "url",
"url": "https://github.com/huggingface/skills.git",
- "sha": "ec0108293521ef698e451ec044e8b4feba6b732b"
+ "sha": "020194918dc4a27d5a5d9a154b6b56cc2bd21364"
},
"homepage": "https://github.com/huggingface/skills.git"
},
@@ -1799,7 +1799,7 @@
"source": {
"source": "url",
"url": "https://github.com/heygen-com/hyperframes.git",
- "sha": "049f5618d7d2be09543754f71cb379e1c0c309ac"
+ "sha": "3e4b08cdc18642d468d53f34c2fb64ab437807ae"
},
"homepage": "https://hyperframes.heygen.com"
},
@@ -2254,7 +2254,7 @@
"url": "https://github.com/awslabs/startups.git",
"path": "migrate/plugins/migration-to-aws",
"ref": "main",
- "sha": "f7c03e9f135a909114c1febe1ed804257826ec9f"
+ "sha": "77406441732d3a2e4c887e51166868e7a5b875c0"
},
"homepage": "https://github.com/awslabs/startups"
},
@@ -2378,7 +2378,7 @@
"source": {
"source": "url",
"url": "https://github.com/netlify/context-and-tools.git",
- "sha": "47848e2d6405291caeed0b23689878ec5253bb6f"
+ "sha": "5a62a5694417640a2bba11a0701c8995ecc40bcc"
},
"homepage": "https://github.com/netlify/context-and-tools"
},
@@ -2559,7 +2559,7 @@
"url": "https://github.com/growthxai/output.git",
"path": "coding_assistants/claude/plugins/outputai",
"ref": "main",
- "sha": "82e6b25d653b94aee18f621f1ac9ec0b6c0861a3"
+ "sha": "90d8cc05efc0dff192c6c0e4d50bdb50de9bc1a0"
},
"homepage": "https://output.ai"
},
@@ -2697,7 +2697,7 @@
"source": {
"source": "url",
"url": "https://github.com/PostHog/ai-plugin.git",
- "sha": "672b0076a11b4b4c4ef9d40dee832c10fefb244a"
+ "sha": "884a62b8427947d2f98214cb6fd5e05272795a71"
},
"homepage": "https://posthog.com/docs/model-context-protocol"
},
@@ -2817,7 +2817,7 @@
"source": {
"source": "url",
"url": "https://github.com/qdrant/skills.git",
- "sha": "864f969fc7f8c6c02e0133f37e4f0840fe0f1fab"
+ "sha": "cdcce09dfe0742ecf294649ec029c1f491320853"
},
"homepage": "https://skills.qdrant.tech"
},
@@ -2958,7 +2958,7 @@
"source": {
"source": "url",
"url": "https://github.com/resend/resend-skills.git",
- "sha": "4b1558df96241f0a7eb416a1ce262650f2a5f471"
+ "sha": "1187c26406662d8f4f6d68f24dc47146381bdfae"
},
"homepage": "https://resend.com"
},
@@ -3085,7 +3085,7 @@
"url": "https://github.com/forcedotcom/sf-skills.git",
"path": "plugins/builder/salesforce-development",
"ref": "main",
- "sha": "8a13a085744a7330397db4aa9fe6d2d1fc2c1867"
+ "sha": "94f1dbdb643245745ba2e5d5cd1b546514b780a7"
},
"homepage": "https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/salesforce-development"
},
@@ -3099,7 +3099,7 @@
"source": {
"source": "url",
"url": "https://github.com/sanity-io/agent-toolkit.git",
- "sha": "77a54f785085b7a70fb98ce9e33ef80f3775fce8"
+ "sha": "6b48aeddf90cc59257cfacc0a022a28340383a41"
},
"homepage": "https://www.sanity.io"
},
@@ -3133,7 +3133,7 @@
"url": "https://github.com/SAP/open-ux-tools.git",
"path": "packages/fiori-mcp-server",
"ref": "main",
- "sha": "b413e6bd0bb7c2523af9e2d37dcc3bf38c50945a"
+ "sha": "e7e6f970bd7bd173832050095f422ffb1e8722dd"
},
"homepage": "https://github.com/SAP/open-ux-tools/tree/main/packages/fiori-mcp-server"
},
@@ -3479,7 +3479,7 @@
"source": {
"source": "url",
"url": "https://github.com/supabase-community/supabase-plugin.git",
- "sha": "aadcf51499969e5ed476dadd19fdf688bcc0b250"
+ "sha": "8629243d1cd72309b533090a4c742f21747d02fa"
},
"homepage": "https://github.com/supabase-community/supabase-plugin"
},
@@ -3599,7 +3599,7 @@
"source": {
"source": "url",
"url": "https://github.com/togethercomputer/skills.git",
- "sha": "fa0811d63d3769609911126bd52bb60cbe5c99f7"
+ "sha": "644d38225bbdef0318462fe222f6f9883c8addcd"
},
"homepage": "https://www.together.ai"
},
@@ -3810,7 +3810,7 @@
"source": {
"source": "url",
"url": "https://github.com/villagesql/villagesql-skills.git",
- "sha": "288ed3324bbe733881ee8ba43deccdc7eb15075b"
+ "sha": "39490c14b7bfe116285bde686eb676cadf042642"
},
"homepage": "https://villagesql.com"
},
@@ -3835,7 +3835,7 @@
"source": {
"source": "url",
"url": "https://github.com/wix/skills.git",
- "sha": "a04e0e586da63359fa9d42bec9f7795319acbd05"
+ "sha": "bda0b16b2070cd96c1fcd63e90b32a281800ecb7"
},
"homepage": "https://dev.wix.com/docs/wix-cli/guides/development/about-wix-skills"
},
diff --git a/content/github/claude-plugins-official/.github/bump-tracking.json b/content/github/claude-plugins-official/.github/bump-tracking.json
index b2d9d7e9f..02b797ebd 100644
--- a/content/github/claude-plugins-official/.github/bump-tracking.json
+++ b/content/github/claude-plugins-official/.github/bump-tracking.json
@@ -1,5 +1,6 @@
{
"releases-only": [
+ "azure",
"carta-cap-table",
"carta-investors",
"chrome-devtools-mcp",
diff --git a/content/github/claude-plugins-official/plugins/claude-security/.claude-plugin/plugin.json b/content/github/claude-plugins-official/plugins/claude-security/.claude-plugin/plugin.json
index 0e3b01eb9..83bab5c3f 100644
--- a/content/github/claude-plugins-official/plugins/claude-security/.claude-plugin/plugin.json
+++ b/content/github/claude-plugins-official/plugins/claude-security/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "claude-security",
- "version": "0.10.1-rc7",
+ "version": "0.10.1",
"description": "Deep vulnerability scanning of your own code, run entirely inside your Claude Code session at a chosen effort tier, with every finding challenged before it is reported and the verification tally computed in code. Turns surviving findings into targeted patches, each verified by a panel of agents, that you apply when you choose. See the plugin README for the tiers, the report format, and the trust model.",
"author": {
"name": "Anthropic",
diff --git a/content/support/10186004-claude-console-roles-and-permissions.md b/content/support/10186004-claude-console-roles-and-permissions.md
index 667cb416a..7d7b2b1b8 100644
--- a/content/support/10186004-claude-console-roles-and-permissions.md
+++ b/content/support/10186004-claude-console-roles-and-permissions.md
@@ -6,7 +6,7 @@ The Claude Console uses a role-based access system with six distinct roles: User
### User
-- Can only use Workbench
+- Can only use the playground
- Can view MCP tunnels
@@ -14,7 +14,7 @@ The Claude Console uses a role-based access system with six distinct roles: User
### Claude Code User
-- Can use Workbench and **[Claude Code](https://code.claude.com/docs/en/overview)**
+- Can use the playground and **[Claude Code](https://code.claude.com/docs/en/overview)**
- Can access Claude Code workspace in your org
@@ -22,7 +22,7 @@ The Claude Console uses a role-based access system with six distinct roles: User
### Limited Developer
-- Can use Workbench and Claude Code
+- Can use the playground and Claude Code
- Can manage API keys and webhook endpoints
@@ -35,7 +35,7 @@ The Claude Console uses a role-based access system with six distinct roles: User
### Developer
-- Can use Workbench and Claude Code
+- Can use the playground and Claude Code
- Can manage API keys and webhook endpoints
@@ -51,7 +51,7 @@ The Claude Console uses a role-based access system with six distinct roles: User
### Billing
-- Can use Workbench
+- Can use the playground
- Can manage billing details
diff --git a/content/support/10310342-how-do-i-log-out-of-all-active-sessions.md b/content/support/10310342-how-do-i-log-out-of-all-active-sessions.md
index 43f6bf551..100602b9d 100644
--- a/content/support/10310342-how-do-i-log-out-of-all-active-sessions.md
+++ b/content/support/10310342-how-do-i-log-out-of-all-active-sessions.md
@@ -38,7 +38,7 @@ To regain access to your account on any device, you'll need to authenticate agai
If you used your Claude account to authenticate into Claude Code, you can manage your authorization tokens by navigating to **[Settings > Claude Code](https://claude.ai/settings/claude-code)**. To remove a token and log out of Claude Code, click the trash can icon.
-
+
## Unable to access your account?
diff --git a/content/support/10366376-how-can-i-delete-my-claude-console-account.md b/content/support/10366376-how-can-i-delete-my-claude-console-account.md
index 544b5b36e..f652c8e23 100644
--- a/content/support/10366376-how-can-i-delete-my-claude-console-account.md
+++ b/content/support/10366376-how-can-i-delete-my-claude-console-account.md
@@ -36,7 +36,7 @@ If you followed the steps above to delete your Console organization but want to
If you have an outstanding balance, you will see a message during the deletion flow that prompts you to pay the balance first by routing you to [Settings > Billing](https://platform.claude.com/settings/billing).
-
+
You must pay this outstanding balance before you’re able to move forward with the deletion process.
@@ -44,6 +44,6 @@ You must pay this outstanding balance before you’re able to move forward with
There are some scenarios where you will need to contact our team to delete your account. If this is the case, it will be noted when you try to delete your organization:
-
+
If you are seeing this message, this indicates that your Console organization cannot be deleted via the self-service pathway.
\ No newline at end of file
diff --git a/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md b/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md
index 07f62362d..a48fa89ce 100644
--- a/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md
+++ b/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md
@@ -6,6 +6,6 @@ As a Primary Owner or Owner of a Team or Enterprise plan, you can manage the abi
2. Use the toggle to change the **Rate chats** setting for your organization:
-
+
More information on how Anthropic collects, uses, and stores feedback data can be found in our Privacy Center: **[How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)**
\ No newline at end of file
diff --git a/content/support/10504853-manage-user-feedback-settings-on-claude-console.md b/content/support/10504853-manage-user-feedback-settings-on-claude-console.md
index df959f2f9..286f25cdf 100644
--- a/content/support/10504853-manage-user-feedback-settings-on-claude-console.md
+++ b/content/support/10504853-manage-user-feedback-settings-on-claude-console.md
@@ -8,6 +8,6 @@ To manage feedback for your Console organization:
2. Toggle the feedback switch on or off.
-
+
More information on how Anthropic collects, uses, and stores feedback data can be found in our Privacy Center: [How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)
\ No newline at end of file
diff --git a/content/support/10593882-share-and-unshare-chats.md b/content/support/10593882-share-and-unshare-chats.md
index bd9c17c1c..e8995dda7 100644
--- a/content/support/10593882-share-and-unshare-chats.md
+++ b/content/support/10593882-share-and-unshare-chats.md
@@ -38,12 +38,12 @@ To unshare a chat:
Users on free, Pro, or Max plans can review a log of shared chats by navigating to **[Settings > Privacy](https://claude.ai/settings/data-privacy-controls)**. Find the **Privacy settings** section and click “Manage” next to **Shared chats:**
-
+
This will open a **Shared chats** modal listing the title, date shared, and link to each chat, allowing you to easily review and access all your previously-shared content. From here, you also have the option to click “Unshare” next to each listed chat to revoke access to the last snapshot you shared:
-
+
If you don’t have any shared chat snapshots, the **Shared chats** modal will show “No shared content found”:
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/content/support/10684626-enable-and-use-web-search.md b/content/support/10684626-enable-and-use-web-search.md
index a9cb168a9..92e468b10 100644
--- a/content/support/10684626-enable-and-use-web-search.md
+++ b/content/support/10684626-enable-and-use-web-search.md
@@ -24,7 +24,7 @@ Web search expands Claude's knowledge with real-time data, helping you make bett
An Owner or Primary Owner must first enable web search for the entire workspace. This can be found in **[Admin settings > Capabilities](https://claude.ai/admin-settings/capabilities)**:
-
+
Once this is enabled at the workspace level, any member of the organization can switch it on while starting a chat by clicking the “+” button in the lower left corner of the chat window and selecting “Web search." Users can toggle this off for chats that don’t require web search capabilities.
diff --git a/content/support/10949351-getting-started-with-local-mcp-servers-on-claude-desktop.md b/content/support/10949351-getting-started-with-local-mcp-servers-on-claude-desktop.md
index 59390a521..3063353c0 100644
--- a/content/support/10949351-getting-started-with-local-mcp-servers-on-claude-desktop.md
+++ b/content/support/10949351-getting-started-with-local-mcp-servers-on-claude-desktop.md
@@ -48,7 +48,7 @@ for specific instructions.
Custom desktop extensions uploads allow Team and Enterprise plans to leverage organization-specific workflows that aren’t available in the public directory. After creating a custom desktop extension, Owners and Primary Owners can navigate to Settings > Extensions within Claude Desktop and click “Advanced settings” to access the **Extension Developer** section:
-
+
Click “Install Extension…” and select the .mcpb file. Follow the prompts to install and configure your custom desktop extension. For more in-depth information, please refer to our [desktop extension developer documentation](https://github.com/anthropics/mcpb).
diff --git a/content/support/11101966-use-voice-mode.md b/content/support/11101966-use-voice-mode.md
index 01ae06207..7578140eb 100644
--- a/content/support/11101966-use-voice-mode.md
+++ b/content/support/11101966-use-voice-mode.md
@@ -24,7 +24,7 @@ Voice mode transforms how you interact with Claude by:
2. Tap the sound wave symbol in the lower right corner of the chat window to activate voice mode:
-
+
3. Start talking and see your prompt automatically populate in the chat input.
@@ -32,7 +32,7 @@ Voice mode transforms how you interact with Claude by:
5. Claude will remain in voice mode until you click the “Stop” button in the lower right corner of the chat window:
-
+
### On mobile (iOS and Android)
@@ -40,7 +40,7 @@ Voice mode transforms how you interact with Claude by:
2. Tap the voice mode icon (sound wave symbol next to the microphone icon) in the text input field:
-
+
3. Choose a voice to personalize your experience.
@@ -78,7 +78,7 @@ To change the voice later:
- **On mobile:** Click the settings button in the bottom left corner while chatting with Claude in voice mode, then tap your preferred voice and pace:
-
+
## Choose a model
diff --git a/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md b/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md
index 0d4b7a754..c12816043 100644
--- a/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md
+++ b/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md
@@ -44,7 +44,7 @@ This article provides information on how to enable the Claude LTI integration in
5. Click "Install" and refresh the course page.
-
+
## Turn on the Claude LTI Integration in Claude for Education organization settings
diff --git a/content/support/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context.md b/content/support/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context.md
index 00687fdc1..a02ff68f0 100644
--- a/content/support/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context.md
+++ b/content/support/11817273-use-claude-s-chat-search-and-memory-to-build-on-previous-context.md
@@ -40,7 +40,7 @@ When Claude searches your previous chats, you will see this reflected in your cu
Yes, navigate to **[Settings > Memory](https://claude.ai/new#settings/customize-memory)** and switch the toggle next to "Search and reference chats" off:
-
+
## Can I exclude a specific past chat from searches?
@@ -80,7 +80,7 @@ Each project has its own separate memory space and dedicated project summary, so
You can toggle Claude’s memory on by navigating to **[Settings > Memory](https://claude.ai/new#settings/customize-memory)** and turning on **Generate memory from chats**:
-
+
If you want to disable Claude’s memory, click the toggle and you'll see two options:
@@ -184,7 +184,7 @@ When Claude searches your previous chats, you will see this reflected in your cu
Yes, navigate to **[Settings > Capabilities](https://claude.ai/settings/capabilities)** and find the **Preferences** section. Switch the toggle next to “Search and reference chats” off:
-
+
### Can I exclude a specific past chat from searches?
@@ -192,7 +192,7 @@ Incognito chats are available to all Claude users (free, Pro, Max, Team, and Ent
When starting a new chat with Claude outside of a project, you'll see a ghost icon in the upper right corner of your screen:
-
+
Clicking the ghost icon will open an incognito chat, creating a temporary conversation that isn’t saved to your chat history. Claude won’t pull information from incognito chats when searching previous conversations.
@@ -224,7 +224,7 @@ Each project has its own separate memory space and dedicated project summary, so
You can toggle Claude’s memory on by navigating to **[Settings > Capabilities](https://claude.ai/settings/capabilities)**:
-
+
If you want to disable Claude’s memory, click the toggle to see two options:
diff --git a/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md b/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md
index 55fd684ea..f4284ecfb 100644
--- a/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md
+++ b/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md
@@ -2,7 +2,7 @@
If you see the following pop-up when you log in to your Claude account, you’ll need to click the “Verify now” button to verify your payment method:
-
+
## What happens if I click “Remind me later?”
diff --git a/content/support/11869629-use-claude-with-android-apps.md b/content/support/11869629-use-claude-with-android-apps.md
index cff9e4668..53d0bbe46 100644
--- a/content/support/11869629-use-claude-with-android-apps.md
+++ b/content/support/11869629-use-claude-with-android-apps.md
@@ -222,7 +222,7 @@ Permission requirements vary by feature:
For features requiring permissions (like location or calendar access), Claude will request permission contextually with clear explanations of why the access is needed. You’ll be prompted to approve the action with three options: Allow once, Always allow, or Don't allow.
-
+
These permissions can be managed at any time in your device settings by going to Settings > Apps > Claude > Permissions. Click into each permission listed under **Allowed** and **Not allowed** to make changes. You can toggle between “Allow only while using the app” or “Ask every time” to change Claude’s access, or remove permissions by choosing “Don’t allow.” Claude will only request permissions if needed for specific features, and you can always choose to decline while still using other capabilities.
diff --git a/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md b/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md
index ad8b9e391..6e093200c 100644
--- a/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md
+++ b/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md
@@ -70,7 +70,7 @@ After navigating to **[Organization settings > Usage](https://claude.ai/admin-se
The **Usage and spend limits** section will show the current limit (if any) or **Unlimited**. Clicking on "Adjust limit" opens a modal where you can either input an amount and click "Set spend limit," or click "Set to unlimited" to remove the organization-wide monthly spend limit.
-
+
Changes to your organization’s overall spend limit go into effect immediately.
@@ -78,11 +78,11 @@ Changes to your organization’s overall spend limit go into effect immediately.
Owners and Primary Owners on **seat-based Enterprise plans only** can set spend limits that apply to all users within a specific seat tier.
-
+
Select the "By group" tab to see **Standard seats** and **Premium seats** groups. Click the "..." icon next to the current limit, then "Edit limit." This opens a modal where you can either select "Set dollar amount" and input an amount, or click "Unlimited" to remove the limit for that seat type. Click "Set limit" to save your changes.
-
+
---
@@ -90,11 +90,11 @@ Select the "By group" tab to see **Standard seats** and **Premium seats** groups
Owners and Primary Owners can also set individual monthly spend limits for each member by finding **Spend limits by user** and clicking the "..." button next to the user, then "Edit limit."
-
+
Enter the amount and click "Set limit." Alternatively, selecting "Set to unlimited" will remove that member's monthly spend limit (they will still be subject to any organization or seat-level spend limits).
-
+
This allows owners fine control over usage credits, so you can set limits for different members based on their roles or individual needs. Once a user reaches their defined spend limit, this will automatically pause their usage credits until the end of the month. They will need to wait for their usage limits to reset before using Claude again.
diff --git a/content/support/12012173-get-started-with-claude-in-chrome.md b/content/support/12012173-get-started-with-claude-in-chrome.md
index b3c5bfad7..46460c3d5 100644
--- a/content/support/12012173-get-started-with-claude-in-chrome.md
+++ b/content/support/12012173-get-started-with-claude-in-chrome.md
@@ -36,7 +36,7 @@ Follow these steps to enable the Claude in Chrome connector in your desktop app:
4. Toggle the connector on, then download and install the extension if you haven’t already.
-
+
Completing these steps will add Claude in Chrome to the “Connectors” drop-down on your chats with Claude. This is disabled by default, so you’ll need to enable it manually for each conversation.
diff --git a/content/support/12083917-change-your-team-plan-from-monthly-to-annual-billing.md b/content/support/12083917-change-your-team-plan-from-monthly-to-annual-billing.md
index 8967287b6..70b5e3e81 100644
--- a/content/support/12083917-change-your-team-plan-from-monthly-to-annual-billing.md
+++ b/content/support/12083917-change-your-team-plan-from-monthly-to-annual-billing.md
@@ -8,11 +8,11 @@ Owners and Primary Owners of Team plans with monthly subscriptions can switch fr
3. Or from /upgrade, click the “Switch to Annual plan” button:
-
+
4. The confirmation screen will display the total cost for your upgrade from monthly to annual billing:
-
+
5. Click “Confirm subscription.”
diff --git a/content/support/12111783-create-and-edit-files-with-claude.md b/content/support/12111783-create-and-edit-files-with-claude.md
index d5bb17dda..2da847657 100644
--- a/content/support/12111783-create-and-edit-files-with-claude.md
+++ b/content/support/12111783-create-and-edit-files-with-claude.md
@@ -48,7 +48,7 @@ These capabilities make it easy to produce professional documents by simply chat
To give Claude access to external data sources, toggle **Allow network egress** on:
-
+
### Enabling on Claude Mobile
@@ -66,11 +66,11 @@ Team and Enterprise organization owners can control network access settings in *
- **Allow network egress to package managers and specific domains:** Claude can access package managers plus additional domains you specify. Add domains individually to whitelist specific resources your organization needs:
-
+
**All domains:** Claude has full internet access except for domains on Anthropic's legal blocklist. While this provides maximum flexibility for file creation and analysis tasks, it’s also the riskiest option. Please review the **[security considerations below](#h_0ee9d698a1)** before enabling “All domains”:
-
+
---
diff --git a/content/support/12157520-claude-code-usage-analytics.md b/content/support/12157520-claude-code-usage-analytics.md
index 0e2616112..9e3ff0429 100644
--- a/content/support/12157520-claude-code-usage-analytics.md
+++ b/content/support/12157520-claude-code-usage-analytics.md
@@ -50,7 +50,7 @@ The **Usage** tab displays the following metrics for your organization. Data on
- **Top commands**: The Claude Code commands used most often across your organization.
-
+
### User-level metrics
diff --git a/content/support/12260368-use-incognito-chats.md b/content/support/12260368-use-incognito-chats.md
index 0494d4b1d..6aa4e9965 100644
--- a/content/support/12260368-use-incognito-chats.md
+++ b/content/support/12260368-use-incognito-chats.md
@@ -30,7 +30,7 @@ Incognito chats are temporary conversations that aren't saved to your chat histo
When starting a new chat with Claude outside of a project, you'll see a ghost icon in the upper right corner of your screen:
-
+
1. Click the ghost icon to enable incognito mode.
diff --git a/content/support/12293051-use-claude-in-xcode.md b/content/support/12293051-use-claude-in-xcode.md
index c23b09a33..727cf78bd 100644
--- a/content/support/12293051-use-claude-in-xcode.md
+++ b/content/support/12293051-use-claude-in-xcode.md
@@ -34,7 +34,7 @@ To start using Claude in Xcode:
3. Log in with your Claude account.
-
+
## Usage limits
diff --git a/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md b/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md
index b6218c668..484c0cae1 100644
--- a/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md
+++ b/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md
@@ -46,7 +46,7 @@ To enable usage credits on your paid Claude plan:
8. You can also enable auto-reload to automatically make a purchase when your balance falls below a threshold you set:
-
+
**Note:** There is a daily redemption limit of $2000.
diff --git a/content/support/12466728-troubleshoot-claude-error-messages.md b/content/support/12466728-troubleshoot-claude-error-messages.md
index ad6be4414..9ff962ed9 100644
--- a/content/support/12466728-troubleshoot-claude-error-messages.md
+++ b/content/support/12466728-troubleshoot-claude-error-messages.md
@@ -58,4 +58,4 @@ Capacity issues will not appear on our status page because they represent normal
Service incidents are disruptions where Claude is unavailable or significantly degraded for all or most users. These represent actual technical problems with our systems. To check for confirmed incidents, visit status.claude.com, where you'll find real-time updates on scope, impact, and resolution progress for any active incidents.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/content/support/12512180-use-skills-in-claude.md b/content/support/12512180-use-skills-in-claude.md
index 381ee4c2b..22b22422c 100644
--- a/content/support/12512180-use-skills-in-claude.md
+++ b/content/support/12512180-use-skills-in-claude.md
@@ -166,7 +166,7 @@ To remove a custom skill you've uploaded:
4. To delete the custom skill entirely, click the "..." button next to the toggle, then select "Delete":
- 
+ 
5. Click "Delete" in the confirmation prompt.
diff --git a/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md b/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md
index 12738426a..79d28052d 100644
--- a/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md
+++ b/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md
@@ -20,11 +20,11 @@ The desktop extension allowlist is disabled by default, so an organization Owner
4. Switch to the "Desktop" tab:
-
+
5. Toggle **Allowlist** on:
-
+
## What happens after enabling the allowlist?
@@ -42,7 +42,7 @@ Consider completing the allowlist setup during off-hours to minimize disruption
**Important:** The allowlist requires Claude Desktop version 0.13.91 or higher, so users should update the desktop app by clicking “Claude”, then either “Check for updates” or “Restart to update to Claude 0.13.91”:
-
+
## Managing allowed extensions
@@ -60,7 +60,7 @@ After enabling the allowlist, you can choose which extensions to allow:
If you want to remove an extension from the allowlist, click the “...” button and “Remove from allowlist.”
-
+
## Uploading custom extensions
diff --git a/content/support/12618689-claude-code-on-the-web.md b/content/support/12618689-claude-code-on-the-web.md
index 493ab4bcd..088ecc819 100644
--- a/content/support/12618689-claude-code-on-the-web.md
+++ b/content/support/12618689-claude-code-on-the-web.md
@@ -10,7 +10,7 @@ This feature works with repositories you may not have on your local machine. You
Claude Code for web enables asynchronous development workflows. With Claude Code in your terminal or editor, you typically work synchronously: you make a request, wait for Claude to respond, review the changes, then make another request. Synchronous work like this gives you fine-grained control but requires your attention throughout the process. Claude Code on the web handles this differently: you can assign a larger task, let Claude work independently, and return later to review the completed work.
-
+
You can also run multiple tasks in parallel. Since each task runs in its own isolated environment, you can have Claude working on several different issues or repositories simultaneously. Each task proceeds independently and creates its own pull request when complete. More than one task can work on the same repository at the same time.
@@ -18,13 +18,13 @@ You can also run multiple tasks in parallel. Since each task runs in its own iso
When you start a task, Claude Code on the web creates an isolated virtual machine for your work. Your GitHub repository is cloned into this environment, which comes pre-configured with common development tools and language ecosystems.
-
+
Claude prepares the environment by running any setup commands you've defined in your repository's configuration. This includes installing dependencies, setting up databases, or running other initialization steps your project needs. If your task requires network access, maybe to install packages or fetch data, you can configure the level of internet access the environment has.
Once the environment is ready, Claude begins working on your task. Claude reads your code, makes changes, writes tests, and runs commands to verify the work. You can monitor progress and provide guidance through the web interface if needed.
-
+
When Claude completes the task, it pushes the changes to a new branch in your GitHub repository. You receive a notification and can review the changes, then create a pull request directly from the interface. The pull request includes all of Claude's work, ready for your review and any additional changes you want to make.
diff --git a/content/support/12626668-use-quick-entry-with-claude-desktop-on-mac.md b/content/support/12626668-use-quick-entry-with-claude-desktop-on-mac.md
index b6af40a9e..d53887908 100644
--- a/content/support/12626668-use-quick-entry-with-claude-desktop-on-mac.md
+++ b/content/support/12626668-use-quick-entry-with-claude-desktop-on-mac.md
@@ -40,7 +40,7 @@ When you first open the updated version of Claude Desktop, you'll see a prompt t
Once enabled, double-tapping Option will open a text box where you can type your message and start a new chat. You can also click "New chat" to see your five most recent conversations.
-
+
### Enable the voice shortcut (optional)
diff --git a/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md b/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md
index 91a496907..d0c13ea81 100644
--- a/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md
+++ b/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md
@@ -22,7 +22,7 @@ This page includes the following analytics:
- Sessions in Cowork
-
+
### Who’s using Claude?
@@ -34,7 +34,7 @@ This page includes the following analytics:
Use the dropdown on the **Active members and assigned seats** chart to filter by product, including Claude Design.
-
+
### How are they using Claude?
@@ -48,9 +48,9 @@ Use the dropdown on the **Active members and assigned seats** chart to filter by
- How agentic is their work? (beta)
-
+
-
+
### What are the results?
@@ -66,7 +66,7 @@ Use the dropdown on the **Active members and assigned seats** chart to filter by
- Estimated time saved
-
+
### How much is Claude costing?
@@ -82,9 +82,9 @@ This section includes the following analytics:
- Spend by model (month-to-date, quarter-to-date, year-to-date, 1 year)
-
+
-
+
## Export a spend report
@@ -160,7 +160,7 @@ Navigate to **[Analytics > Claude Chat](https://claude.ai/analytics/usage)** to
- Top members by chats
-
+
### Projects
@@ -172,7 +172,7 @@ Navigate to **[Analytics > Claude Chat](https://claude.ai/analytics/usage)** to
- Top members by project usage
-
+
### Artifacts
@@ -182,7 +182,7 @@ Navigate to **[Analytics > Claude Chat](https://claude.ai/analytics/usage)** to
- Top 10 users by artifacts generated (month-to-date, quarter-to-date, year-to-date, 1 year)
-
+
---
@@ -278,7 +278,7 @@ Navigate to **[Analytics > Cowork](https://claude.ai/analytics/cowork)** to view
- Daily, weekly, and monthly active Cowork users
-
+
**Note:** Cowork analytics are available alongside Chat and Claude Code data in the **[Analytics API](https://platform.claude.com/docs/en/manage-claude/analytics-api)**.
@@ -288,7 +288,7 @@ Navigate to **[Analytics > Cowork](https://claude.ai/analytics/cowork)** to view
When your admin turns on individual usage analytics, any member of the organization can see their own usage broken down by product, model, and skill, along with where they stand against any spend limits set for them. Individual usage analytics are available in **[Settings > Usage](https://claude.ai/settings/usage)**.
-
+
---
diff --git a/content/support/12902446-claude-in-chrome-permissions-guide.md b/content/support/12902446-claude-in-chrome-permissions-guide.md
index 6a5de3a0d..f83c2c917 100644
--- a/content/support/12902446-claude-in-chrome-permissions-guide.md
+++ b/content/support/12902446-claude-in-chrome-permissions-guide.md
@@ -28,7 +28,7 @@ In "Manually approve," Claude checks with you before it acts. What that looks li
Claude creates a plan from your prompt, which you can approve before Claude starts. The plan specifies which websites you're allowing Claude to access, as well as the approach it will follow:
-
+
Note that Claude will only use the websites listed in the plan, so you’ll need to manually approve any additional access requests.
@@ -62,7 +62,7 @@ When you choose "Skip all approvals," Claude doesn't pause to ask, and nothing c
There are some websites on which Claude requires approval for every action. If you navigate to one of these sites, a **New permissions required** prompt will appear in the extension side panel, Claude Cowork, or Claude Code where Claude will ask for permission before accessing the page or taking any action.
-
+
### Permission options
diff --git a/content/support/12997503-team-plan-billing-faqs.md b/content/support/12997503-team-plan-billing-faqs.md
index fa5a2fb69..6c359a245 100644
--- a/content/support/12997503-team-plan-billing-faqs.md
+++ b/content/support/12997503-team-plan-billing-faqs.md
@@ -18,7 +18,7 @@ Your organization's billing address determines where your invoices are sent. You
If you want to use a name other than the one tied to your payment method, an organization Owner should check the "Use a different name on invoices" box when adding or updating your payment method in **[Organization settings > Billing](https://claude.ai/admin-settings/billing)**:
-
+
## When will I be billed?
diff --git a/content/support/13132885-set-up-single-sign-on-sso.md b/content/support/13132885-set-up-single-sign-on-sso.md
index 0f238c5b5..451147443 100644
--- a/content/support/13132885-set-up-single-sign-on-sso.md
+++ b/content/support/13132885-set-up-single-sign-on-sso.md
@@ -42,7 +42,7 @@ You can verify multiple domains for a single organization, but all domains must
3. Enter the domain(s) you want to verify in the **Update organization email domains** modal and click the “+” button:
-
+
4. Click “Save” when you’re finished adding domains.
@@ -50,7 +50,7 @@ You can verify multiple domains for a single organization, but all domains must
6. Enter your domain in the text box and click “Continue”:
-
+
7. The setup screen displays a TXT record. **Copy the full Value using the copy button**—it begins with `anthropic-domain-verification-` and is longer than what's visible in the box. In your DNS provider, add a TXT record with **Host/Name** set to `@` (the root of your domain) and **Value** set to the copied string. Add it alongside any existing TXT records; don't replace them. The value is case-sensitive, so paste it exactly.
@@ -76,7 +76,7 @@ Clicking "Refresh" re-checks your DNS; it won't show Verified until the publishe
If the record is correct and propagated but the status still shows Pending, contact Support.
-
+
**Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Organization and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains.
@@ -116,7 +116,7 @@ For IdP-specific setup instructions, see:
You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the **Organization and access** page, under the **Authentication** section:
-
+
When SSO is required, users must use the “Continue with SSO” option to log in to their Claude/Console accounts. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.”
diff --git a/content/support/13133195-set-up-jit-or-scim-provisioning.md b/content/support/13133195-set-up-jit-or-scim-provisioning.md
index 25e3082a8..19d87bc87 100644
--- a/content/support/13133195-set-up-jit-or-scim-provisioning.md
+++ b/content/support/13133195-set-up-jit-or-scim-provisioning.md
@@ -34,7 +34,7 @@ Use this table to help decide which provisioning mode is right for your organiza
Both JIT and SCIM can be combined with **Enable group mappings** to control role or seat tier assignment based on IdP group membership. If you select either of these options for your provisioning mode, **Enable group mappings** will appear within the **User provisioning** section:
-
+
### Available roles and seat tiers
@@ -118,7 +118,7 @@ Once your IdP is connected, continue to Step 3.
4. Toggle **Enable group mappings** on (if it’s not already):
-
+
5. In the **Enable group mappings** section, click “Add” next to each role and select the corresponding group from your IdP in the dropdown.
@@ -170,7 +170,7 @@ Verify you have enough seats purchased and available to add members to your org.
4. **For SCIM:** Click "Sync" to prompt an immediate sync, or wait for the automatic sync cycle:
-
+
### I lost Admin/Owner access after enabling group mappings
diff --git a/content/support/13163631-configuring-session-security-settings.md b/content/support/13163631-configuring-session-security-settings.md
index 9c4931a4c..35e5d59e1 100644
--- a/content/support/13163631-configuring-session-security-settings.md
+++ b/content/support/13163631-configuring-session-security-settings.md
@@ -18,7 +18,7 @@ Session duration controls allow Enterprise and Console Admins to set a maximum s
5. Confirm your selection by clicking “Enable.”
-
+
### For Console Admins
@@ -32,7 +32,7 @@ Session duration controls allow Enterprise and Console Admins to set a maximum s
5. Confirm your selection by clicking “Enable.”
-
+
### What happens after enabling shortened session length?
@@ -50,7 +50,7 @@ You can change the session duration at any time by selecting a new value from th
- Sessions scheduled to expire beyond the new duration will have their expiration shortened accordingly.
-
+
## Disabling session length settings
diff --git a/content/support/13189465-log-in-to-your-claude-account.md b/content/support/13189465-log-in-to-your-claude-account.md
index b50c1d94c..275e156d7 100644
--- a/content/support/13189465-log-in-to-your-claude-account.md
+++ b/content/support/13189465-log-in-to-your-claude-account.md
@@ -2,7 +2,7 @@
When you open Claude on a web browser ([claude.ai](http://claude.ai)), the desktop app, or a mobile app, you will see two different options for logging in to your Claude account.
-
+
## Continue with Google
diff --git a/content/support/13325567-account-management-faqs.md b/content/support/13325567-account-management-faqs.md
index 5a05b9662..2827c84d0 100644
--- a/content/support/13325567-account-management-faqs.md
+++ b/content/support/13325567-account-management-faqs.md
@@ -44,6 +44,6 @@ The email domain that was used to create your Team or Enterprise plan organizati
Owners can remove domains by opening up the same modal and clicking the trash can icon to the right of the domain:
-
+
While the account creator must use a business email address, you can add public domains like @gmail.com, @yahoo.com, and @hotmail.com as allowed domains for other members of your organization.
\ No newline at end of file
diff --git a/content/support/13345190-get-started-with-claude-cowork.md b/content/support/13345190-get-started-with-claude-cowork.md
index 5e507c5a8..50f106e4b 100644
--- a/content/support/13345190-get-started-with-claude-cowork.md
+++ b/content/support/13345190-get-started-with-claude-cowork.md
@@ -42,7 +42,7 @@ With Cowork, you can describe an outcome, step away, and come back to finished w
- If you're a Team or Enterprise plan admin, you can **[use OpenTelemetry (OTel) to monitor Claude Cowork activity](https://support.claude.com/en/articles/14477985-monitor-claude-cowork-activity-with-opentelemetry)** across your organization.
-- Please review **[Use Cowork safely](https://support.claude.com/en/articles/13364135-using-cowork-safely)** for more information.
+- For more information, review **[Use Cowork safely](https://support.claude.com/en/articles/13364135-using-cowork-safely)**.
For important limitations and considerations for Team and Enterprise organizations using Cowork, see **[Cowork for Team and Enterprise plans](https://support.claude.com/en/articles/13455879-cowork-for-team-and-enterprise-plans)**.
@@ -178,7 +178,7 @@ To set global instructions:
3. Type your instructions in the text box and click "Save":
-
+
### Folder instructions
@@ -214,7 +214,7 @@ If you find yourself hitting usage limits frequently when using Cowork, consider
- Monitoring your individual usage in **[Settings > Usage](https://claude.ai/settings/usage)**.
-See **[Usage limit best practices](https://support.claude.com/en/articles/9797557-usage-limit-best-practices)** for more information.
+For more information, see **[Usage limit best practices](https://support.claude.com/en/articles/9797557-usage-limit-best-practices)**.
---
@@ -298,10 +298,6 @@ We're iterating on Cowork based on feedback. If you encounter issues or have sug
This message is expected and indicates that Cowork is updating to the most recent version to apply any fixes and improvements.
-### I don't see Cowork on web or mobile
-
-Cowork on web and mobile is rolling out gradually across paid plans. Make sure you're on an eligible plan and, on mobile, that you've updated to the latest version of the app.
-
### Claude stopped working on my task
For local sessions, ensure the Claude Desktop app was open throughout the entire task. If the app was closed or your computer went to sleep, the session may have ended. Sessions in the cloud keep running in the background; open the session from any surface to check its progress.
diff --git a/content/support/13346458-customizing-your-console-appearance-settings.md b/content/support/13346458-customizing-your-console-appearance-settings.md
index 7d2137a39..62e21cdc6 100644
--- a/content/support/13346458-customizing-your-console-appearance-settings.md
+++ b/content/support/13346458-customizing-your-console-appearance-settings.md
@@ -8,4 +8,4 @@
3. Select from Light, System, or Dark under **Color mode**.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/content/support/13364135-use-claude-cowork-safely.md b/content/support/13364135-use-claude-cowork-safely.md
index 2d1671525..d2da625e7 100644
--- a/content/support/13364135-use-claude-cowork-safely.md
+++ b/content/support/13364135-use-claude-cowork-safely.md
@@ -2,9 +2,9 @@
Cowork sessions run in the cloud on Anthropic's servers (in beta), and Claude reaches your files, browser, and apps through the Claude Desktop app. These capabilities come with risks worth understanding. This article covers what we've built to keep you safe, what you should watch for, and how to protect yourself when using Cowork.
-Claude Cowork is available for paid plans (Pro, Max, Team, Enterprise) on desktop, web, mobile. For where to find it on each surface and what's available where, see **[Use Claude Cowork on web, desktop, and mobile](https://support.claude.com/en/articles/15520349)**. On Max and Team plans, on Pro plans as the rollout reaches you, and on Enterprise plans where your admin has enabled it, you can also run a Cowork session directly in the Claude in Chrome side panel.
+Claude Cowork is available for paid plans (Pro, Max, Team, Enterprise) on desktop, and in beta on web and mobile for Pro, Max, and Team plans, and Enterprise plans when enabled by an owner. For where to find it on each surface and what's available where, see **[Use Claude Cowork on web, desktop, and mobile](https://support.claude.com/en/articles/15520349)**.
-Claude Cowork is in beta on web and mobile for Max, Team, and Enterprise plans, and will be rolling out to Pro plans over the next several weeks.
+On Max and Team plans, on Pro plans as the rollout reaches you, and on Enterprise plans where your admin has enabled it, you can also run a Cowork session directly in the Claude in Chrome side panel.
---
diff --git a/content/support/13371040-log-in-to-your-console-account.md b/content/support/13371040-log-in-to-your-console-account.md
index 5d5afa086..8faeebddf 100644
--- a/content/support/13371040-log-in-to-your-console-account.md
+++ b/content/support/13371040-log-in-to-your-console-account.md
@@ -2,7 +2,7 @@
When you navigate to the **[Claude Console](https://platform.claude.com)**, you will see two different options for logging in to your Console account.
-
+
## Continue with Google
@@ -74,4 +74,4 @@ If you've previously authenticated using Google, you can follow these steps to u
### Can I have both a Claude account and a Console account?
-Yes, you can have both a Claude account (for using Claude at claude.ai) and a Console account (for accessing the Workbench and Claude API). These are separate accounts, though you can use the same email address for both. Learn more in **[Can I have a Claude account and a Console account?](https://support.claude.com/en/articles/8987223-can-i-have-a-claude-account-and-a-console-account)**
\ No newline at end of file
+Yes, you can have both a Claude account (for using Claude at claude.ai) and a Console account (for accessing the playground and Claude API). These are separate accounts, though you can use the same email address for both. Learn more in **[Can I have a Claude account and a Console account?](https://support.claude.com/en/articles/8987223-can-i-have-a-claude-account-and-a-console-account)**
\ No newline at end of file
diff --git a/content/support/13455879-use-claude-cowork-on-team-and-enterprise-plans.md b/content/support/13455879-use-claude-cowork-on-team-and-enterprise-plans.md
index edd1e33a8..efdc0f633 100644
--- a/content/support/13455879-use-claude-cowork-on-team-and-enterprise-plans.md
+++ b/content/support/13455879-use-claude-cowork-on-team-and-enterprise-plans.md
@@ -4,21 +4,19 @@ This article explains important limitations and considerations for Team and Ente
## Availability
-Claude Cowork is available for paid plans (Pro, Max, Team, Enterprise) on:
+Claude Cowork is available on paid plans (Pro, Max, Team, Enterprise). Availability varies by surface:
-- **Claude Desktop for macOS**
+- **Claude Desktop for macOS** — Available on all paid plans. **[Click here](https://claude.ai/api/desktop/darwin/universal/dmg/latest/redirect)** to download.
- - **[Click here](https://claude.ai/api/desktop/darwin/universal/dmg/latest/redirect)** to download
+- **Claude Desktop for Windows** — Available on all paid plans. Cowork requires the latest version of Claude for Windows. Download or update at **[claude.com/download](http://claude.com/download)**.
-- **Claude Desktop for Windows**
+- **Web (beta)**, at claude.ai — Available on Pro, Max, and Team plans. On Enterprise plans, available where an admin has enabled it.
- - **Windows users:** Cowork requires the latest version of Claude for Windows. Download or update at **[claude.com/download](https://claude.com/download)**.
+- **Claude Mobile** **(beta)** — Available on Pro, Max, and Team plans, in the latest version of Claude for iOS and Claude for Android. On Enterprise plans, available where an admin has enabled it.
-- **Web**, at claude.ai
+- **Claude in Chrome side panel** — Available on Max and Team plans, and rolling out to Pro plans. On Enterprise plans, available where an admin has enabled it. For more information, see **[Get started with Claude in Chrome](https://support.claude.com/en/articles/12012173-get-started-with-claude-in-chrome)**.
-- **Claude Mobile**, in the latest version of Claude for iOS and Claude for Android
-
-Claude Cowork is in beta on web and mobile for Team and Enterprise plans. On web and mobile, Claude Cowork sessions run in Anthropic's cloud.
+On web and mobile, Claude Cowork sessions run in Anthropic's cloud.
---
diff --git a/content/support/13641943-visual-and-interactive-content.md b/content/support/13641943-visual-and-interactive-content.md
index 6ba27590e..99bc59dba 100644
--- a/content/support/13641943-visual-and-interactive-content.md
+++ b/content/support/13641943-visual-and-interactive-content.md
@@ -18,7 +18,7 @@ Claude can show current weather conditions and forecasts when you ask about the
Claude automatically displays temperatures in Fahrenheit for US locations and Celsius for everywhere else.
-
+
Weather is powered by Google Maps ().
@@ -28,7 +28,7 @@ When you ask about recipes, Claude can display formatted recipe cards that are e
**Note:** Visual recipe cards are available on web and desktop only. On mobile, Claude provides recipe information as text in the conversation.
-
+
### Custom visuals
@@ -76,7 +76,7 @@ For example, if you ask Claude to help you plan a trip, it might ask you to:
This content appears at the bottom of the chat. You can still type a response if you prefer.
-
+
---
diff --git a/content/support/13756069-public-sector-faqs.md b/content/support/13756069-public-sector-faqs.md
index d4d952b67..118796b6c 100644
--- a/content/support/13756069-public-sector-faqs.md
+++ b/content/support/13756069-public-sector-faqs.md
@@ -6,7 +6,7 @@
Select your product based on both your technical/functional requirements, and also your compliance/security/deployment environment requirements. Here is a list of options:
-
+
### What is Claude for Government (C4G)?
diff --git a/content/support/13837433-manage-plugins-for-your-organization.md b/content/support/13837433-manage-plugins-for-your-organization.md
index b3b73ab26..5c59e88a8 100644
--- a/content/support/13837433-manage-plugins-for-your-organization.md
+++ b/content/support/13837433-manage-plugins-for-your-organization.md
@@ -106,7 +106,7 @@ Your personal GitHub token is verified to confirm you have access, then Cowork u
An initial sync runs automatically when you connect a repository. After that, organization owners can opt-in to continued automatic updates per marketplace by going to **[Organization settings > Plugins](https://claude.ai/admin-settings/plugins)**, clicking the menu button in the upper right corner of the marketplace, then toggling "Sync automatically" on:
-
+
Enabling automatic sync creates a webhook on the connected repository. The person turning the toggle on must have admin-level access to that repository on GitHub. This is checked through their personal GitHub connection, which is separate from the Claude GitHub App installation. Without admin access, the page shows "Cannot access repository. Ensure the repository exists and the Claude GitHub App is installed," even when the App is installed correctly and manual updates work.
diff --git a/content/support/13837440-use-plugins-in-claude.md b/content/support/13837440-use-plugins-in-claude.md
index be2274ffe..696ca7aa8 100644
--- a/content/support/13837440-use-plugins-in-claude.md
+++ b/content/support/13837440-use-plugins-in-claude.md
@@ -40,7 +40,7 @@ In Cowork, open the "Cowork" tab first, then open **Customize**.
You can also upload a custom plugin file if you built one yourself or received one from a colleague. On Claude Desktop and in Cowork, plugins you add yourself are saved locally to your computer.
-
+
If you're on the Enterprise plan and your organization has skill scanning turned on, plugins are checked for malicious content when they're installed or updated. A plugin with malicious content is blocked, and one that may carry risk shows a caution banner. Learn more about **[skill and plugin scanning](https://support.claude.com/en/articles/15927065)**.
@@ -50,7 +50,7 @@ If you're on the Enterprise plan and your organization has skill scanning turned
Each plugin you install adds skills you can use while working with Claude. Type "/" or click the "+" button to see the available skills from your installed plugins, in chat and in Cowork. Click any skill to see its details.
-
+
---
diff --git a/content/support/13854387-schedule-recurring-tasks-in-claude-cowork.md b/content/support/13854387-schedule-recurring-tasks-in-claude-cowork.md
index 45f146c93..e8e45ad2e 100644
--- a/content/support/13854387-schedule-recurring-tasks-in-claude-cowork.md
+++ b/content/support/13854387-schedule-recurring-tasks-in-claude-cowork.md
@@ -4,7 +4,7 @@ Scheduled tasks allow you to delegate work to Claude Cowork by creating tasks th
Scheduled tasks are available in Cowork for all paid plans (Pro, Max, Team, Enterprise).
-Claude Cowork is in beta on web and mobile, and rolling out over the next several weeks starting with the Max plan, with more plans to follow.
+Claude Cowork is available for paid plans (Pro, Max, Team, Enterprise) on desktop, and in beta on web and mobile for Pro, Max, and Team plans, and Enterprise plans when enabled by an owner.
## What scheduled tasks can do
@@ -52,7 +52,7 @@ There are two ways to create a scheduled task:
6. You can explicitly confirm you want to schedule the task when prompted by Claude by clicking “Schedule":
-
+
7. Claude will create and schedule your task, and it will be added to the **Scheduled tasks** page.
diff --git a/content/support/13930458-set-up-role-based-permissions-on-enterprise-plans.md b/content/support/13930458-set-up-role-based-permissions-on-enterprise-plans.md
index 063d24e46..d87bd8d80 100644
--- a/content/support/13930458-set-up-role-based-permissions-on-enterprise-plans.md
+++ b/content/support/13930458-set-up-role-based-permissions-on-enterprise-plans.md
@@ -66,7 +66,7 @@ Create roles that delegate parts of administration without granting the Owner ro
4. For each team or department, decide which features they need access to.
-
+
Remember: any feature you want to control per-group must be **enabled** at the organization level. If a feature is toggled off at the organization level, no custom role can grant access to it.
@@ -84,7 +84,7 @@ Create your custom roles before enabling any features or migrating members. This
3. Name the role and toggle the appropriate capabilities on the **Capabilities** tab, or choose "All capabilities" or "All generally available" to grant everything at once:
-
+
4. On the **Permissions** tab, set admin permissions for the role. See **Step 3**.
@@ -114,7 +114,7 @@ Set admin permissions on each role to delegate access to admin settings, like bi
3. Select the **Permissions** tab, between **Capabilities** and **Connectors**.
-
+
### **Set admin permissions**
@@ -154,7 +154,7 @@ Set connector permissions on each role to control which connectors, and which to
The default settings for new roles are permissive. When creating or modifying a role, confirm the settings on each tab to avoid granting unintended permissions.
-
+
### Set connector-level permissions
@@ -170,7 +170,7 @@ The **Connectors** tab lists an **All connectors** row at the top, followed by e
Choosing “Always allow,” “Needs approval,” or “Blocked” applies that level to every tool on the connector. The **All connectors** row works the same way one level up: it sets a baseline for every connector at once, including any connector you add later. Use it to set a role’s default, then override individual connectors.
-
+
### Set how members connect
@@ -192,7 +192,7 @@ Set a connector to **Custom** to reveal its tools as individual rows. Each tool
Per-tool permissions let a role reach part of a connector. For example, with Jira set to **Custom**, its `search_issues` tool set to “Needs approval,” and every other Jira tool set to “Blocked,” members with the role can search Jira but nothing else. Claude only sees the tools you’ve granted, so asking it to create a ticket returns “I don’t have a tool for that” rather than an error.
-
+
### Review cross-role conflicts
@@ -200,7 +200,7 @@ Because connector permissions are additive across roles, blocking a connector in
If you have unsaved edits when you open a linked role, you’re asked to discard them first.
-
+
### Verify enforcement
@@ -250,13 +250,13 @@ Verify model access after you've migrated members to "Custom" roles. See **Step
4. Assign each group to the custom roles you created in step 2.
-
+
-
+
If you use SCIM directory sync, you can sync groups from your identity provider instead of creating them manually. For details on SCIM group sync, see **[Manage groups and group spend limits on Enterprise plans](https://support.claude.com/en/articles/13799932-manage-groups-and-group-spend-limits-on-enterprise-plans)**.
-
+
**Multiple organizations under the same parent organization:** Groups are managed at the parent organization level and propagate to all child organizations. You may see members from other organizations listed in a group—this doesn't mean they have access to your organization. Custom roles assigned to a group only grant capabilities to members who are part of your specific organization.
@@ -298,7 +298,7 @@ Use this path only if your organization already enabled group mappings for role
3. Save your changes. Members in those IdP groups are migrated to "Custom" roles on the next sync.
-
+
Members in IdP groups mapped to "Custom" roles follow the permissions of the custom roles assigned to their groups in Claude. Members in IdP groups mapped to User follow the organization-level capability settings. If a member is in groups across both mappings, "Custom" roles take precedence.
@@ -314,11 +314,11 @@ Use this path if your organization hasn’t enabled group mappings.
3. Use the bulk assignment tool in the Members table to change the selected members' role to "Custom."
-
+
-
+
-
+
We recommend migrating a pilot group first—one team or department—and verifying their access is correct before expanding to the rest of the organization.
@@ -354,9 +354,9 @@ Enabling a feature at the organization level doesn't mean everyone gets it—cus
Navigate to the “Usage” page to assign a per-user monthly spend limit to any group.
-
+
-
+
Note the following precedence rules:
diff --git a/content/support/13947068-assign-tasks-from-anywhere-in-claude-cowork.md b/content/support/13947068-assign-tasks-from-anywhere-in-claude-cowork.md
index 0193bafd4..199f397b0 100644
--- a/content/support/13947068-assign-tasks-from-anywhere-in-claude-cowork.md
+++ b/content/support/13947068-assign-tasks-from-anywhere-in-claude-cowork.md
@@ -48,11 +48,11 @@ Follow these steps to get started:
5. You’ll land on a page describing the functionality. Click “Get started”:
-
+
6. On the next screen, you can give Claude access to your files and keep your computer awake by toggling those on:
-
+
7. Click “Finish setup.”
diff --git a/content/support/14116274-organize-your-tasks-with-projects-in-claude-cowork.md b/content/support/14116274-organize-your-tasks-with-projects-in-claude-cowork.md
index 7c89ee013..a73633d9d 100644
--- a/content/support/14116274-organize-your-tasks-with-projects-in-claude-cowork.md
+++ b/content/support/14116274-organize-your-tasks-with-projects-in-claude-cowork.md
@@ -22,23 +22,23 @@ Cowork is available for paid plans (Pro, Max, Team, Enterprise) on:
Find **Projects** in the left navigation panel and click the “+” button to see the three different ways to create a project:
-
+
### Start from scratch
Selecting “Start from scratch” allows you to set up a new folder with instructions and files:
-
+
### Import from a Claude project
After selecting “Import from project,” you’ll see a “Search projects in Chat…” field:
-
+
Clicking into the field will display a drop-down showing your recent projects, but you can also use it to search all your projects. After you select a chat project (bulk upload is not supported), you can name the new Cowork project and choose where to save it on your computer:
-
+
Clicking “Create” will transfer the files and instructions from your existing Claude project and create a new Cowork project.
@@ -46,11 +46,11 @@ Clicking “Create” will transfer the files and instructions from your existin
If you select “Use an existing folder,” you’ll be prompted to pick a file to use as context for the new Cowork project:
-
+
After selecting a folder, you can name the new Cowork project, choose where to save it on your computer, add instructions, and attach any additional files. Click “Create” to start using your new project:
-
+
---
diff --git a/content/support/14128542-let-claude-use-your-computer-in-cowork.md b/content/support/14128542-let-claude-use-your-computer-in-cowork.md
index 9a4aff883..e01f7fdcd 100644
--- a/content/support/14128542-let-claude-use-your-computer-in-cowork.md
+++ b/content/support/14128542-let-claude-use-your-computer-in-cowork.md
@@ -40,7 +40,7 @@ If your work involves a physical machine, Claude keeps working while you step aw
Claude asks for your permission before accessing each application. You’ll see a prompt and must approve before Claude can interact with that app. Some apps are off-limits by default.
-
+
Claude is trained to avoid risky operations—like transferring funds, modifying or deleting files, or handling sensitive data—and to flag signs of prompt injection. However, these safeguards aren't perfect, and Claude may occasionally act outside these boundaries.
@@ -128,7 +128,7 @@ To start using computer use:
3. Find the **Computer use** toggle and turn it on:
-
+
4. Open Cowork or Claude Code in the desktop app and start a session.
diff --git a/content/support/14479288-claude-cowork-architecture-overview.md b/content/support/14479288-claude-cowork-architecture-overview.md
index e5fcda045..bed53c1f3 100644
--- a/content/support/14479288-claude-cowork-architecture-overview.md
+++ b/content/support/14479288-claude-cowork-architecture-overview.md
@@ -4,11 +4,11 @@ This article explains where Claude Cowork runs, how each execution mode is isola
This article is for Enterprise admins. The architecture described here is the same across all plans. The device-level admin controls at the end apply to Team and Enterprise plans.
-Claude Cowork is in beta on web and mobile for Max, Team, and Enterprise plans, and will be rolling out to Pro plans over the next several weeks.
+Claude Cowork is in beta on web and mobile for Pro, Max, and Team plans, and Enterprise plans when enabled by an owner.
## Where Claude Cowork runs
-Cowork sessions run in the cloud by default: the agent loop and code execution run on Anthropic's servers, and sessions and files are saved to the member's Claude account. Cloud execution is in beta and rolling out gradually across plans.
+Cowork sessions run in the cloud by default: the agent loop and code execution run on Anthropic's servers, and sessions and files are saved to the member's Claude account.
Local execution remains available for existing desktop deployments: the agent loop and code execution run on the member's device, as described below.
diff --git a/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md b/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md
index 67c3d9cd6..2b97a33fa 100644
--- a/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md
+++ b/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md
@@ -50,7 +50,7 @@ You can trigger a manual sync from two places in your admin settings.
2. Click "Check for updates" under **SCIM sync**:
-
+
3. Select whether to sync members, groups, or both.
@@ -62,7 +62,7 @@ You can trigger a manual sync from two places in your admin settings.
3. Select whether to sync members, groups, or both:
-
+
**Note:** If you trigger a manual sync while background changes are processing, your organization takes the most recent change for each member or group. If multiple changes are queued for the same member or group, you may need to resync again to make sure everything applies correctly.
diff --git a/content/support/14503613-sso-login.md b/content/support/14503613-sso-login.md
index c2020c61f..edaee9608 100644
--- a/content/support/14503613-sso-login.md
+++ b/content/support/14503613-sso-login.md
@@ -47,9 +47,9 @@ Before configuring your Identity Provider (IdP), you must verify ownership of yo
3. Wait for the DNS propagation. Once the platform detects the record, the domain status will update to “**Verified**.”
-
+
-
+
**Important:** Each domain can only have one identity provider. If multiple organizations share a single login domain, IT administrators from both organizations will be able to modify login settings. Contact **[Anthropic Support](https://claude.fedstart.com/support)** for assistance with multi-organization setups. For more details about multi-organization setups, see our **[SCIM provisioning guide](https://support.claude.com/en/articles/14503643-set-up-scim-in-claude-for-government)**.
@@ -77,7 +77,7 @@ Once your SAML application is set up in your IdP, provide Anthropic with the det
- Claims Information — Attribute mappings for user name and email.
-
+
**Tip:** Using a metadata XML file: Most IdPs let you download a metadata.xml file. Upload it on the identity settings page to auto-fill the Signing Certificate, IdP Entity ID, and SSO URL. Some IdPs (like Entra ID) also include claims information in the metadata file; if present, the system will suggest field mappings automatically.
diff --git a/content/support/14503643-set-up-scim-in-claude-for-government.md b/content/support/14503643-set-up-scim-in-claude-for-government.md
index 230a3382a..b69f7a370 100644
--- a/content/support/14503643-set-up-scim-in-claude-for-government.md
+++ b/content/support/14503643-set-up-scim-in-claude-for-government.md
@@ -41,7 +41,7 @@ With SCIM, login and provisioning are separate. Your IdP tells Anthropic who sho
**Important**: Store this key securely. It cannot be retrieved after you leave the page.
-
+
### Step 2: Configure SCIM in your Identity Provider
@@ -67,7 +67,7 @@ After enabling the integration in your IdP:
**Warning**: When you fully enable SCIM provisioning, any users who were **not** synced via SCIM will be removed from the organization. Confirm that all expected users appear in the sync before proceeding.
-
+
### Step 4: Map groups to roles and seat tiers
@@ -83,7 +83,7 @@ SCIM provisioning uses IdP groups to assign roles and seat tiers within Claude f
3. Save your mappings.
-
+
If you manage multiple organizations under a single parent (see below), each organization maintains its own role and seat tier mappings. Switch between organizations using the organization selector in the bottom-left corner of the page.
diff --git a/content/support/14503775-mcp-web-search.md b/content/support/14503775-mcp-web-search.md
index c9951b772..10161e837 100644
--- a/content/support/14503775-mcp-web-search.md
+++ b/content/support/14503775-mcp-web-search.md
@@ -4,7 +4,7 @@ The Web Search connector gives Claude the ability to search the public internet
For questions about web search in commercial Claude, see **[Enabling and using web search](https://support.claude.com/en/articles/10684626-enabling-and-using-web-search)**.
-
+
## How Web Search differs for Claude for Government
diff --git a/content/support/14604397-set-up-your-design-system-in-claude-design.md b/content/support/14604397-set-up-your-design-system-in-claude-design.md
index a2fea3252..ae4521e25 100644
--- a/content/support/14604397-set-up-your-design-system-in-claude-design.md
+++ b/content/support/14604397-set-up-your-design-system-in-claude-design.md
@@ -72,7 +72,7 @@ To validate your design system, create a test project and see if the output matc
Once you’re satisfied with the design system quality, make sure the “Published” toggle is switched on. After publishing, any projects created from the Claude Design homescreen while in your organization will use your design system instead of the default.
-
+
---
diff --git a/content/support/14604406-claude-design-admin-guide-for-team-and-enterprise-plans.md b/content/support/14604406-claude-design-admin-guide-for-team-and-enterprise-plans.md
index 0c396b962..86cbef871 100644
--- a/content/support/14604406-claude-design-admin-guide-for-team-and-enterprise-plans.md
+++ b/content/support/14604406-claude-design-admin-guide-for-team-and-enterprise-plans.md
@@ -18,7 +18,7 @@ Team and Enterprise plan admins can enable this organization-wide by following t
2. Find the **Claude Design** toggle under **Anthropic Labs** and switch it on.
-
+
---
diff --git a/content/support/14604416-get-started-with-claude-design.md b/content/support/14604416-get-started-with-claude-design.md
index 2c34cfaf8..afddeebdb 100644
--- a/content/support/14604416-get-started-with-claude-design.md
+++ b/content/support/14604416-get-started-with-claude-design.md
@@ -153,7 +153,7 @@ Use the “Export” button in the upper right corner when viewing your project
- Send to Claude Code Web
-
+
You can also share projects within your organization using a shareable link. Sharing options include view-only, comment, and edit access.
diff --git a/content/support/15330088-set-a-default-model-for-your-organization.md b/content/support/15330088-set-a-default-model-for-your-organization.md
index 27d0031c1..6eb3f58d2 100644
--- a/content/support/15330088-set-a-default-model-for-your-organization.md
+++ b/content/support/15330088-set-a-default-model-for-your-organization.md
@@ -46,7 +46,7 @@ The organization default applies to every member. To set it:
4. Click “Save changes.”
-
+
---
diff --git a/content/support/15520349-use-claude-cowork-on-web-desktop-and-mobile.md b/content/support/15520349-use-claude-cowork-on-web-desktop-and-mobile.md
index 4a7e14cf6..6958a250d 100644
--- a/content/support/15520349-use-claude-cowork-on-web-desktop-and-mobile.md
+++ b/content/support/15520349-use-claude-cowork-on-web-desktop-and-mobile.md
@@ -2,7 +2,7 @@
Claude Cowork is available on desktop, web, mobile, and in the Claude in Chrome side panel. Your sessions and files live with your Claude account and go where you go, on any device. This article explains how to start a Cowork session and what's available on each surface.
-Claude Cowork is in beta on web and mobile for Pro, Max, and Team plans. On Enterprise plans, Cowork on web and mobile is available where an admin has enabled it. Cowork is also available in the Claude in Chrome side panel on Max and Team plans, on Pro plans as it rolls out, and on Enterprise plans where an admin has enabled it. See **[Claude in Chrome admin controls](https://support.claude.com/en/articles/13065128-claude-in-chrome-admin-controls#h_bdb63199e1)** for enablement steps.
+Claude Cowork is in beta on web and mobile for Pro, Max, and Team plans, and on Enterprise plans where an admin has enabled it. Cowork is also available in the Claude in Chrome side panel on Max and Team plans, on Pro plans as it rolls out, and on Enterprise plans where an admin has enabled it. See **[Claude in Chrome admin controls](https://support.claude.com/en/articles/13065128-claude-in-chrome-admin-controls#h_bdb63199e1)** for enablement steps.
---
diff --git a/content/support/15694740-manage-model-access-for-your-organization.md b/content/support/15694740-manage-model-access-for-your-organization.md
index 450d15b89..ae4461d8e 100644
--- a/content/support/15694740-manage-model-access-for-your-organization.md
+++ b/content/support/15694740-manage-model-access-for-your-organization.md
@@ -42,9 +42,9 @@ The organization setting is the ceiling, so a role can’t grant access to a mod
If any custom role uses the model you’re disabling as its default, you’ll be prompted to change that role’s default before the change can be saved.
-
+
-
+
---
@@ -62,7 +62,7 @@ If any custom role uses the model you’re disabling as its default, you’ll be
Only models the role grants access to can be selected as that role’s default model.
-
+
---
@@ -80,7 +80,7 @@ Effort limits determine how much computation members on a role can apply per res
5. Click "Save" to save your changes.
-
+
Members on the role see only effort levels at or below the cap in their model menu. Note that available effort levels differ depending on the model, and some models don’t support effort level settings at all. For an explanation of each level, see **[Change the model, effort, and thinking settings](https://support.claude.com/en/articles/8664678)**.
diff --git a/content/support/15936181-get-started-with-1password-for-claude.md b/content/support/15936181-get-started-with-1password-for-claude.md
index b4eae4618..e31682807 100644
--- a/content/support/15936181-get-started-with-1password-for-claude.md
+++ b/content/support/15936181-get-started-with-1password-for-claude.md
@@ -52,7 +52,7 @@ Once the requirements are in place, you can set up 1Password from a few places i
4. Toggle on **Password managers**:
-
+
Once enabled, eligible users will see the discovery options above. Users still need to install and set up the required apps and extensions themselves.
diff --git a/content/support/8114491-get-started-with-claude.md b/content/support/8114491-get-started-with-claude.md
index f8b3ea0e1..2939f3f9b 100644
--- a/content/support/8114491-get-started-with-claude.md
+++ b/content/support/8114491-get-started-with-claude.md
@@ -36,7 +36,7 @@ You use **prompts** to communicate with Claude. The best approach is to speak to
Type your prompt into the chat interface and click the submit button to start a conversation with Claude. You can click the "+" button in the lower left or type "/" to view additional options and commands:
-
+
---
diff --git a/content/support/8114513-business-associate-agreements-baa-for-commercial-customers.md b/content/support/8114513-business-associate-agreements-baa-for-commercial-customers.md
index 6f6b8e600..63c236171 100644
--- a/content/support/8114513-business-associate-agreements-baa-for-commercial-customers.md
+++ b/content/support/8114513-business-associate-agreements-baa-for-commercial-customers.md
@@ -8,7 +8,7 @@ Anthropic provides a BAA covering our HIPAA-ready services, such as use of our f
**Important:** To use the 1P API with PHI, your organization’s Primary Owner will need to sign a BAA and then reach out to your Anthropic contact or our[**Sales team**](https://claude.com/contact-sales) to get this turned on.
-For clarity, the BAA only covers the single organization that accepted it, and excludes features such as Workbench, Claude Console, Claude Cowork, or features currently in beta such as Claude in Office and Claude Design. As part of the BAA, customers of Anthropic’s HIPAA-ready services are subject to certain configuration requirements and limitations on what features/integrations are available.
+For clarity, the BAA only covers the single organization that accepted it, and excludes features such as Claude Console, Claude Cowork, or features currently in beta such as Claude in Office and Claude Design. As part of the BAA, customers of Anthropic’s HIPAA-ready services are subject to certain configuration requirements and limitations on what features/integrations are available.
Not all API features are covered; see the **[Implementation Guide](https://trust.anthropic.com/resources?s=2zblcrsgb00l3x9l2tpjf&name=[anthropic]-2025-type-1-hipaa-report-(-1-p-api).pdf)** for the full list of eligible and non-eligible features.
diff --git a/content/support/8114521-how-can-i-access-the-claude-api.md b/content/support/8114521-how-can-i-access-the-claude-api.md
index 6545c6af7..76accd87f 100644
--- a/content/support/8114521-how-can-i-access-the-claude-api.md
+++ b/content/support/8114521-how-can-i-access-the-claude-api.md
@@ -1,6 +1,6 @@
# How can I access the Claude API?
-Organizations interested in building with the Claude API can create a [Claude Console account](https://platform.claude.com). The Claude Console is where you can create API keys, add users to your team, set up billing, and experiment with Claude on the Workbench. Please note that access to the API is subject to our [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms).
+Organizations interested in building with the Claude API can create a [Claude Console account](https://platform.claude.com). The Claude Console is where you can create API keys, add users to your team, set up billing, and experiment with Claude on the playground. Please note that access to the API is subject to our [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms).
Read more about [building with the Claude API here](https://claude.com/platform/api).
diff --git a/content/support/8114531-i-created-a-claude-console-organization-how-do-i-start-using-the-claude-api.md b/content/support/8114531-i-created-a-claude-console-organization-how-do-i-start-using-the-claude-api.md
index 7e697a5d9..9b7d5b8f0 100644
--- a/content/support/8114531-i-created-a-claude-console-organization-how-do-i-start-using-the-claude-api.md
+++ b/content/support/8114531-i-created-a-claude-console-organization-how-do-i-start-using-the-claude-api.md
@@ -1,6 +1,6 @@
# I created a Claude Console organization - how do I start using the Claude API?
-To use the Claude API and Workbench, add usage credits to your organization's balance. You’ll need to fill out some additional information about your organization and use case. Then, you’ll enter your payment details and fund your account.
+To use the Claude API and the playground, add usage credits to your organization's balance. You’ll need to fill out some additional information about your organization and use case. Then, you’ll enter your payment details and fund your account.
Once you’ve purchased usage credits for your account, you’re ready to use the API in your commercial application. You can [find more information on prepaid billing and credits here](https://support.claude.com/en/articles/8977456-how-do-i-pay-for-my-api-usage).
diff --git a/content/support/8230524-delete-or-rename-a-conversation.md b/content/support/8230524-delete-or-rename-a-conversation.md
index 90686b376..c22e1dd05 100644
--- a/content/support/8230524-delete-or-rename-a-conversation.md
+++ b/content/support/8230524-delete-or-rename-a-conversation.md
@@ -44,15 +44,15 @@ These steps apply to Claude for iOS, listed on the App Store as Claude by Anthro
4. If deleting, tap "Delete" again in the confirmation prompt.
-
+
-
+
You can also delete the conversation you have open: tap the "⋯" button in the top right corner, tap "Delete," then confirm.
-
+
-
+
## Delete or rename a conversation on Claude for Android
@@ -66,9 +66,9 @@ These steps apply to the Claude for Android, listed on Google Play as Claude by
3. If deleting, tap "Delete" again in the confirmation prompt.
-
+
-
+
**To delete multiple conversations at once:**
@@ -78,9 +78,9 @@ These steps apply to the Claude for Android, listed on Google Play as Claude by
3. Tap the trash icon, then tap "Delete" in the confirmation prompt.
-
+
-
+
## What happens when you delete a conversation
diff --git a/content/support/8325618-paid-plan-billing-faqs.md b/content/support/8325618-paid-plan-billing-faqs.md
index d937250bc..5b885f7de 100644
--- a/content/support/8325618-paid-plan-billing-faqs.md
+++ b/content/support/8325618-paid-plan-billing-faqs.md
@@ -50,7 +50,7 @@ There's no separate option to remove a card, and updating to a new card replaces
If you want to use a name other than the one tied to your payment method, check the "Use a different name on invoices" box when adding or updating your payment method in **[Settings > Billing](https://claude.ai/settings/billing)**.
-
+
## How can I edit a paid invoice?
diff --git a/content/support/8606378-how-do-i-use-the-workbench.md b/content/support/8606378-how-do-i-use-the-workbench.md
index aa7bac153..4bbd811e3 100644
--- a/content/support/8606378-how-do-i-use-the-workbench.md
+++ b/content/support/8606378-how-do-i-use-the-workbench.md
@@ -1,12 +1,12 @@
-# How do I use the Workbench?
+# How do I use the playground?
-We’ve recently updated Workbench. The new Workbench enables developers to try out Claude models and API features directly in the Claude Console, but no longer supports saving prompt history or evaluating prompts.
+**Workbench is now the playground**. Playground enables developers to try out Claude models and API features directly in the Claude Console, but does not support saving prompt history or evaluating prompts.
-**Workbench (legacy) is no longer available to new users and will be retired for all users on August 17, 2026**. If you're still using the legacy version, see the section below, **[How do I use Workbench (legacy)?](#h_b659fc7faa)**, and if there are prompts, completions, or evals you wish to retain, **consider exporting your data before August 17, 2026.**
+If you have saved data from **Workbench (legacy)** that you wish to export, you can do so until **September 1, 2026** in **[Console settings](https://platform.claude.com/settings/privacy)**. This data will no longer be recoverable after September 1, 2026. See **[How do I export my Workbench data from Console?](#h_ce935c603b)** for more.
-## What is Workbench?
+## What is the playground?
-Workbench is built directly on the public **[Messages API](https://platform.claude.com/docs/en/build-with-claude/working-with-messages)**, so the request you build in Workbench is the same request you'll send in your code.
+The playground is built directly on the public **[Messages API](https://platform.claude.com/docs/en/build-with-claude/working-with-messages)**, so the request you build in the playground is the same request you will send in your code.
Use it to:
@@ -18,13 +18,13 @@ Use it to:
- Export your work as a code snippet you can run in your own application
-Workbench doesn't store your prompts or conversations on Anthropic's servers. Your current draft stays in your browser, and you can go to the "code" tab to keep a copy of any request.
+Playground doesn't store your prompts or conversations on Anthropic's servers. Your current draft stays in your browser, and you can go to the “code" tab to keep a copy of any request.
-## Open Workbench
+## Open the playground
1. Log in to the **[Claude Console](https://platform.claude.com/)**.
-2. Select "Workbench" in the navigation.
+2. Select "Playground" in the navigation.
3. If your organization uses workspaces, choose the workspace you want to work in.
@@ -38,108 +38,70 @@ Workbench doesn't store your prompts or conversations on Anthropic's servers. Yo
4. Edit your prompt and run it again to keep iterating.
-Workbench also includes example templates you can load and modify.
+Playground also includes example templates you can load and modify.
## Choose a model and adjust settings
Use the model selector to switch between Claude models, and open the model settings to adjust parameters like temperature and maximum output tokens.
-Running the same prompt with different models or settings is a quick way to see how the response changes. As you think about building your application with the Messages API, use the workbench to understand the power of the models.
+Running the same prompt with different models or settings is a quick way to see how the response changes. As you think about building your application with the Messages API, use the playground to understand the power of the models.
## Use tools and structured outputs
-Add tool definitions to your request to test tool use, and use structured outputs to have Claude return data in a shape you define. Workbench shows tool calls and tool results in the response, so you can see exactly how they're represented in the API.
+Add tool definitions to your request to test tool use, and use structured outputs to have Claude return data in a shape you define. Playground shows tool calls and tool results in the response, so you can see exactly how they're represented in the API.
## View the raw request and response
-Workbench can show the raw API request and response, including the full message structure, stop reason, and usage. This is the same shape your application sends and receives and is a practical way to try out the features of the Messages API.
+Playground can show the raw API request and response, including the full message structure, stop reason, and usage. This is the same shape your application sends and receives and is a practical way to try out the features of the Messages API.
## Turn your work into code
-Click the "code" toggle to export your current request as a code snippet. The snippet reflects exactly what you've tested in the Workbench, so you can paste it into your project and run it with your own API key.
+Click the "code" toggle to export your current request as a code snippet. The snippet reflects exactly what you've tested in the playground, so you can paste it into your project and run it with your own API key.
-Code examples in our documentation include an "Open in Workbench" option, which loads the example into Workbench so you can run and modify it.
+Code examples in our documentation include an "Open in Playground" option, which loads the example into the playground so you can run and modify it.
---
-## How do I use Workbench (legacy)?
+## How do I export my Workbench data from Console?
-**Note: Workbench (legacy) is no longer available to new users and will be retired for all users on August 17, 2026.** After this date, Workbench (legacy) and any saved prompts, prompt versions, and evals stored in it will no longer be accessible. Use the Export option to download your data before then.
+1. Go to **[Claude Console](https://platform.claude.com/settings/privacy)**.
-Workbench (legacy) allows you to create and test prompts within your Claude Console account. You can enter your prompt into the "Human" dialogue box and click "Run" to test Claude's output. Click on the + icon in the upper left to create a new prompt, or click on the bulleted list icon to see prompts you've tested in the past:
+2. In the **Export Workbench data** dialog, choose what to include alongside your prompts:
-
+ 1. **Model completions** — saved responses from past runs
-Workbench (legacy) also allows you to configure several settings when prompting Claude. You can click on the slider icon to review your model settings. This allows you to select the model, temperature, and max tokens to sample:
-
-
-
-After crafting your prompt, click on the "Get code" button to generate a sample using our Python and Typescript SDKs:
-
-
-
-## How can I access my previous work and prompt history in Workbench (legacy)?
-
-You can access your previous Workbench prompts on your Console account by following these steps:
-
-1. Log in at platform.claude.com.
-
-2. Navigate to your [Workbench](https://platform.claude.com/workbench).
-
-3. Click the "List prompts" button on the upper left corner of the page, next to the "+" button to create a new prompt:
-
-
-
-4. A list of your previously-saved prompts will appear.
-
-5. You can use the search bar at the top of the prompt list if you're looking for something specific.
-
-**Important:** When you run a prompt on Workbench (legacy), Claude's response is not saved by default. You need to manually add responses from Claude to your current prompt on the Workbench by clicking "Add to Conversation" at the bottom of the output. If you aren't seeing something in your history that you were expecting, it's possible that it wasn't added to the conversation.
-
-## How do I export my data from Workbench (legacy)?
-
-1. Open **[Workbench (legacy)](https://platform.claude.com/workbench)** in the Claude Console.
-
-2. In the banner at the top of the page, select "Export data."
-
-3. In the **Export Workbench data** dialog, choose what to include alongside your prompts:
-
- - **Model completions** — saved responses from past runs
-
- - **Uploaded files** — images and PDFs attached to your prompts
+ 2. **Uploaded files** — images and PDFs attached to your prompts
**Note:** Including either may significantly increase the export size.
-4. Select "Export." Your data is packaged as JSON, and we'll email you a download link when it's ready.
+Primary Owners or Admins also have the option to export data for their entire organization.
+
+3. Select "Export." Your data is packaged as JSON, and we'll email you a download link when it's ready.
-Export your data before **August 17, 2026**. It will not be accessible after Workbench (legacy) is retired.
+Export your data before **September 1, 2026**. It won't be accessible after this date.
---
## Frequently asked questions
-### What’s changing in Workbench?
+### What happened to Workbench (legacy)?
-We’re refreshing Workbench to be a simpler, stateless way to try Claude models and API features in the Console. The main differences are that it now:
+**Workbench (legacy) is now retired.** The playground replaces it for trying Claude models and API features in the Console. It does not support saving prompt history or evaluating prompts.
-- It doesn't store your work on Anthropic's servers. Your current draft stays in your browser, and you can export any request as code. With Workbench (legacy) you were able to save prompts, prompt history, and run evals.
-
-- It is built directly on the public Messages API and shows the full request and response, so what you see matches what your code sends and receives.
+### What's the difference between Workbench (legacy) and the playground?
-- Saved prompts, prompt versions, evals, and prompt sharing aren't part of the refreshed Workbench. Use the export function in the legacy version to download your data.
+The playground is a simpler, stateless way to try Claude models and API features in the Console. The main differences is that it now:
-### Will Workbench (legacy) keep working for me right now?
-
-**Workbench (legacy) is no longer available to new users and will be retired for all users on August 17, 2026.** If you used Workbench (legacy) prior to **June 16, 2026**, you'll continue to have access until the retirement date and will see a banner in Workbench linking to the legacy version so you can export your data. Accounts that started using Workbench on or after June 16, 2026 do not have access to Workbench (legacy). After August 17, 2026, Workbench (legacy) will no longer be available to anyone.
+- It doesn't store your work on Anthropic's servers. Your current draft stays in your browser, and you can export any request as code. With Workbench (legacy) you were able to save prompts, prompt history, and run evals.
-### What happens to my saved prompts and evals?
+- It is built directly on the public Messages API and shows the full request and response, so what you see matches what your code sends and receives.
-They remain in Workbench (legacy) until it is retired on August 17, 2026. Use the Export option in Workbench (legacy) to download them before that date. The refreshed Workbench doesn't include saved prompts or evals, so keep your exported copies in your own tools, such as the repository where your application code lives.
+- Saved prompts, prompt versions, evals, and prompt sharing aren't part of the playground. Use the export function in the legacy version to download your data.
### How do I get access to my existing data from Workbench (legacy)?
-Your saved prompts and completions are available in Workbench (legacy) until August 17, 2026. You'll see an Export option in Workbench (legacy) that lets you download your saved prompts, prompt revisions, and completions. Export your data before the retirement date, as it will not be accessible afterward.
+You can no longer access this data directly in Console. You can export it as JSON in **[Claude Console](https://platform.claude.com/settings/privacy)** until September 1, 2026. After this date, it will no longer be recoverable.
-### Can I import my Workbench (legacy) data into refreshed Workbench?
+### Can I import my Workbench data into the playground?
-No. The refreshed version of Workbench doesn't save prompts or conversations, so there's nothing to import into. The export gives you a copy of your Workbench data so you can keep it or move it into your own tools.
\ No newline at end of file
+No. The playground doesn't save prompts or conversations, so there's nothing to import into. The export gives you a copy of your Workbench data so you can keep it or move it into your own tools.
\ No newline at end of file
diff --git a/content/support/8887527-customizing-your-appearance-settings.md b/content/support/8887527-customizing-your-appearance-settings.md
index 9157a89de..5084219b1 100644
--- a/content/support/8887527-customizing-your-appearance-settings.md
+++ b/content/support/8887527-customizing-your-appearance-settings.md
@@ -8,7 +8,7 @@
3. Select from Light, Match System, and Dark under **Color mode**.
-
+
## How to change your font
@@ -16,10 +16,10 @@
2. Select from Default, Match System, and Dyslexic Friendly.
-
+
## Can I disable the sidebar?
It's not currently possible to completely disable the sidebar. You can click the button on the top right of the sidebar to open or close it.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/content/support/8977456-how-do-i-pay-for-my-claude-api-usage.md b/content/support/8977456-how-do-i-pay-for-my-claude-api-usage.md
index d2dc77ff4..40be8593a 100644
--- a/content/support/8977456-how-do-i-pay-for-my-claude-api-usage.md
+++ b/content/support/8977456-how-do-i-pay-for-my-claude-api-usage.md
@@ -1,8 +1,8 @@
# How do I pay for my Claude API usage?
-Claude API and Workbench usage is billed via prepaid "usage credits." Credits must be purchased prior to using the API, and your credits will be applied to your usage according to our current **[pricing](https://claude.com/pricing#api)**. These credits can be used for API access, Workbench usage, and Claude Code. Failed requests are not charged, and you will only be billed for successful API calls and completed tasks.
+Claude API and the playground usage is billed via prepaid "usage credits." Credits must be purchased prior to using the API, and your credits will be applied to your usage according to our current **[pricing](https://claude.com/pricing#api)**. These credits can be used for API access, the playground usage, and Claude Code. Failed requests are not charged, and you will only be billed for successful API calls and completed tasks.
-You can track credit usage in your **[Claude Console settings on the Billing page](https://platform.claude.com/settings/billing)**. If you run out of credits, you will no longer be able to call the API or use Workbench. You can choose to set up an auto-reload that purchases additional credits when your balance falls below a set limit.
+You can track credit usage in your **[Claude Console settings on the Billing page](https://platform.claude.com/settings/billing)**. If you run out of credits, you will no longer be able to call the API or use the playground. You can choose to set up an auto-reload that purchases additional credits when your balance falls below a set limit.
To add usage credits and adjust your auto-reload settings, navigate to your Billing page. Click on the “Buy credits” button, and enter in the amount of credits you would like to purchase. After you’ve purchased your credits, they will be immediately available to you.
diff --git a/content/support/9028421-how-can-i-delete-my-claude-account.md b/content/support/9028421-how-can-i-delete-my-claude-account.md
index cbcbd51ab..068e43208 100644
--- a/content/support/9028421-how-can-i-delete-my-claude-account.md
+++ b/content/support/9028421-how-can-i-delete-my-claude-account.md
@@ -2,7 +2,7 @@
Once you are logged in, click your initials or name in the lower left corner and select "Settings." Navigate to **[Settings > Account](https://claude.ai/settings/account)** and click the "Delete account" button:
-
+
## Considerations for paid Claude accounts
@@ -20,4 +20,4 @@ If you have multiple accounts associated with the same email address, you'll nee
There are some scenarios where you will need to **[contact our team](https://support.claude.com/en/articles/9015913-how-to-get-support)** to delete your account. If this is the case, it will be noted in your account:
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/content/support/9266767-what-is-the-team-plan.md b/content/support/9266767-what-is-the-team-plan.md
index fd6ba8bab..48dbb4246 100644
--- a/content/support/9266767-what-is-the-team-plan.md
+++ b/content/support/9266767-what-is-the-team-plan.md
@@ -96,7 +96,7 @@ Usage limits differ between Standard and Premium seats in the following ways:
**Standard seats:** Team plan Standard seats offer 1.25x more usage per session than the Pro plan and have a weekly usage limit that applies across all models.
-**Premium seats:** Team plan Premium seats offer 6.25x more usage per session than the Pro plan. Users assigned to these seats also have two weekly usage limits: one that applies across all models and another for Sonnet models only.
+**Premium seats:** Team plan Premium seats offer 6.25x more usage per session than the Pro plan and have a weekly usage limit that applies across all models.
### Do usage limits apply across the team or to individual members?
diff --git a/content/support/9519177-how-can-i-create-and-manage-projects.md b/content/support/9519177-how-can-i-create-and-manage-projects.md
index 76f51fb9d..63d63933c 100644
--- a/content/support/9519177-how-can-i-create-and-manage-projects.md
+++ b/content/support/9519177-how-can-i-create-and-manage-projects.md
@@ -104,19 +104,19 @@ Starring a project allows for quick access from your projects and chats list, vi
You can move a standalone chat into a project by clicking on the dropdown arrow next to the chat name, then “Add to project”:
-
+
Browse or search for the correct project in the **Move chat** modal that appears, then click on it to move the chat.
-
+
You can also remove chats from projects, or move them between projects, using the same dropdown menu within the chat:
-
+
You can move chats into projects in bulk from **[Your chat history page](https://claude.ai/recents)**:
-
+
Select the chats you want to move, then click the icon next to the number of selected chats to move them into your project.
diff --git a/content/support/9519189-manage-project-visibility-and-sharing.md b/content/support/9519189-manage-project-visibility-and-sharing.md
index 628a5372f..cc79eefcf 100644
--- a/content/support/9519189-manage-project-visibility-and-sharing.md
+++ b/content/support/9519189-manage-project-visibility-and-sharing.md
@@ -12,7 +12,7 @@ When creating a project on a Team or Enterprise plan, you can choose between two
- **Private:** Only invited members can view and use the project.
-
+
## What are public projects?
@@ -22,11 +22,11 @@ If you choose to share a project with the rest of your organization upon creatio
Yes, you can switch the visibility of a project you created as public to private at any time by opening the project and clicking the “Share” button to the right of the project name:
-
+
Click “Everyone at [your organization]” under **General access** and select “Only people invited” to change the project from public to private:
-
+
## What are private projects?
@@ -36,11 +36,11 @@ Choosing “Only people invited” keeps your project private so that you are th
Yes, you can switch the visibility of a project you created as private to public at any time by opening the project and clicking the “Share” button to the right of the project name:
-
+
Click “Only people invited” under General access and select “Everyone at [your organization]” to change the project from private to public:
-
+
## Add and remove access to private projects
diff --git a/content/support/9534590-cost-and-usage-reporting-in-the-claude-console.md b/content/support/9534590-cost-and-usage-reporting-in-the-claude-console.md
index 176ad3b88..4545c5fce 100644
--- a/content/support/9534590-cost-and-usage-reporting-in-the-claude-console.md
+++ b/content/support/9534590-cost-and-usage-reporting-in-the-claude-console.md
@@ -8,7 +8,7 @@ The Claude Console provides detailed cost and usage reporting to help you effect
Users with access to these reports can click into them on the left navigation menu on the Console:
-
+
---
@@ -46,9 +46,9 @@ The [Usage page](https://platform.claude.com/usage) offers a detailed breakdown
6. Use the export button to download a CSV of the displayed data.
-
+
-
+
### Rate Limit Use
@@ -88,6 +88,6 @@ The [Cost page](https://platform.claude.com/cost) helps you understand your spen
5. Use the export button to download a CSV of the cost data.
-
+
**Note**: Currently, it's not possible to break down usage or cost by individual users.
\ No newline at end of file
diff --git a/content/support/9547008-publish-and-share-artifacts.md b/content/support/9547008-publish-and-share-artifacts.md
index 131e7ba07..31bc0b553 100644
--- a/content/support/9547008-publish-and-share-artifacts.md
+++ b/content/support/9547008-publish-and-share-artifacts.md
@@ -56,11 +56,11 @@ Publishing also adds the artifact to the **[Artifacts](https://claude.ai/artifac
After publishing, you'll see a “Get embed code” button.
-
+
Click it to open a modal with automatically generated code you can copy and paste to embed your artifact on another website.
-
+
You must specify which websites can embed your artifact by entering URLs in the **Allowed domains** field, separated by commas.
@@ -116,7 +116,7 @@ Artifacts created on Team or Enterprise accounts can only be shared within your
4. Click “Share & copy link” to make this version shareable.
-
+
### Who can access shared artifacts
@@ -138,7 +138,7 @@ When you share an artifact, viewers also gain access to any attachments and file
2. In the **Artifact shared** modal, click “Unshare.”
-
+
---
diff --git a/content/support/9927533-disable-public-projects-for-your-organization.md b/content/support/9927533-disable-public-projects-for-your-organization.md
index 7e9b740b6..ce9086cc0 100644
--- a/content/support/9927533-disable-public-projects-for-your-organization.md
+++ b/content/support/9927533-disable-public-projects-for-your-organization.md
@@ -10,7 +10,7 @@ Follow these steps:
2. Find **Public projects** and toggle it off
-
+
## How does disabling public projects work?