Anthropic · Claude

Who can use it: Claude Code 2.1.314 and later.

How to use it: Enable permissions.blockWritesOutsideWorkingDirectories in managed or user settings.

Tip: Explicitly define working directories and enforce this setting in CI and on shared machines.

Who can use it: For users of Claude Code in VS Code and the Claude Desktop Code tab; coverage has expanded subject to provider and telemetry conditions.

How to use it: Update Claude Code; leave the Idle compaction option in /config enabled in settings.

Tip: Before pausing a long task, check context usage with /context and /usage.

Who can use it: Beta for Claude Console and Claude Enterprise organizations; the analytics-usage-cost-2026-08-24 beta header is required.

How to use it: Send POST requests to the /v1/organizations/analytics/usage and /v1/organizations/analytics/cost endpoints with the relevant beta header.

Tip: Track costs by workspace and service account as well as by model to identify budget variances.

Who can use it: Support continues for existing users; the new Analytics API is recommended for new integrations.

How to use it: Follow the Migrate from the Usage and Cost API guide to move to the new usage and cost endpoints.

Tip: Instead of removing the old endpoints immediately, compare their results with the new API for a while during migration.

Who can use it: Claude Enterprise organizations; eligibility may vary with configurations such as HIPAA or customer-managed encryption.

How to use it: Enable Smart reports, surveys, and pooled group budgets in admin settings; select a team and date range to create a report.

Tip: Use reports to identify repeatable skills and missing connectors, not to measure individual performance.

Who can use it: Claude for Legal and Claude Enterprise teams; subject to organization configuration and relevant connectors.

How to use it: Open the Artifacts gallery in Claude or the Claude for Legal page, then choose a legal template.

Tip: Use the automated initial review as a source-linked preliminary step, not as a substitute for a lawyer’s assessment.

Who can use it: First-party Claude API.

How to use it: Send the request body directly, ensuring it does not exceed the 128 MB limit; also check your client and gateway limits.

Tip: For large requests, still count tokens in advance and test timeout and proxy limits.

Who can use it: Financial advisor teams and organizations; connector access depends on the relevant provider and Claude organization permissions.

How to use it: Install the Claude for Financial Advisors plugin from Claude Marketplace and select the providers you’ll use during setup.

Tip: Limit recommendations from every Skill that works with portfolio or client data to the advisor’s final decision.

Who can use it: Verified nonprofit organizations; installed automatically on Team and Enterprise plans at no extra cost. A separate discount was announced for verified nonprofits in low- and middle-income countries.

How to use it: Ask Claude to map where your organization stores its information; other nonprofit Skills use this map.

Tip: Before submitting grant applications, check figures cited by Claude against the original documents.

Who can use it: Claude Enterprise organizations; requires an Admin API key, the read:claude_tag or write:claude_tag scope, and the experimental-claude-tag-2026-10-21 beta header. Not available for Claude Console organizations.

How to use it: Call the /v1/organizations/claude_tag/ endpoints with an appropriate Admin API key.

Tip: Before changing channel settings, use the API to check whether the active value comes from the workspace or the channel.

Who can use it: Developers with Google Cloud projects and an eligible Anthropic-managed Claude Models setup.

How to use it: Enable Anthropic-managed Claude Models in your Google Cloud project, then configure IAM permissions and Marketplace billing.

Tip: Compare Anthropic API, Google-managed, and Anthropic-managed options based on your latency, IAM, and billing requirements.

Who can use it: The Agent Skills standard is publicly available and can be used with Claude and other agent platforms that support the standard.

How to use it: Create Skills based on SKILL.md and share them according to the agentskills.io standard.

Tip: For enterprise Skills, keep instructions, scripts, and reference files separate and versioned.

Who can use it: Claude Platform developers; the API version is available for Claude 4.7 and later.

How to use it: Apply the SDK and client changes in the Migration to API version 2026-10-21 guide.

Tip: Before upgrading the client in production, compare both the old and new API versions using the same test suite.

Who can use it: Research preview and waitlist; initially for Pro and Max subscribers in the US, on iOS, Android, and claude.ai.

How to use it: Join the Claude Duet waitlist and connect your apps with an approval flow.

Tip: Start with reversible, low-risk tasks and clearly define which situations should trigger a notification.

Who can use it: Users of the User Profiles API on Claude Platform.

How to use it: Use the enforcement_status[] filter on the GET /v1/user_profiles endpoint.

Tip: Before applying restrictions across an organization, log profile records associated with end-customer IDs.

Who can use it: Claude Console organization administrators and Managed Agents; if web fetch is disabled, an API request returns 400, while an agent call returns an error result.

How to use it: Configure Allow web search and web fetch, along with domain lists, under Claude Console > Capabilities.

Tip: Limit the allowlist to the hosts your agent actually needs instead of using broad wildcards.

Who can use it: Claude Enterprise organizations.

How to use it: Follow the Inference hooks setup in the Claude Platform documentation and configure hooks for your organization.

Tip: Measure latency and errors in hooks; test rules that could block critical production calls in shadow mode first.

Who can use it: Claude Platform organizations; contact the Anthropic account team and use the webhooks-2026-10-07 header for beta access.

How to use it: Register a webhook destination at the /v1/organizations/webhooks endpoints.

Tip: Implement signature verification, retries, and an idempotency key in your webhook receiver.

Who can use it: Claude Code 2.1.304 and later; Code Review levels are for Team and Enterprise organizations.

How to use it: Run /auto-mode-setup in a Claude Code session; in Code Review settings, select Quick, Standard, or Deep for the repository.

Tip: Run Auto mode setup on a trusted sample project, and don’t generalize its recommendations without reviewing the suggested rules.

Who can use it: Claude Code 2.1.302 and later.

How to use it: Use CLAUDE_CODE_AUTO_MODE_MODEL for Auto mode; turn idle compaction on or off under /config > Idle compaction.

Tip: When changing the classifier model, compare safety refusal and latency metrics on the same project.

Who can use it: Claude Code 2.1.302 and later; terminal, Agent SDK, desktop, and VS Code surfaces.

How to use it: Set CLAUDE_CODE_FORK_SUBAGENT=0 to disable the default; no action is needed to enable it.

Tip: Separate task boundaries and working branches to prevent write conflicts in shared files during parallel subtasks.

Who can use it: Claude Opus 5.5 users; Claude Platform and Microsoft Foundry Azure deployments. Preview status continues for Claude Opus 5 and 4.8.

How to use it: Enable Fast mode in a Claude Opus 5.5 request; the fast-mode-2026-02-01 header is no longer required.

Tip: Use the speed boost for non-critical, latency-sensitive tasks; monitor the Fast mode rate limit during periods of heavy traffic.

Who can use it: Claude Team and Enterprise; an administrator must enable it in Claude Code settings and install the GitHub App.

How to use it: Enable Code Review in Claude Code settings, install the GitHub App, and select the repositories to review; reviews will start automatically on new PRs.

Tip: Start with Deep for critical repositories and Quick for small, frequently changing repositories, then monitor review times.

Who can use it: Claude Enterprise; requires an existing Compliance Access Key and the read:compliance_user_data scope.

How to use it: Call the GET /v1/compliance/organizations/{org_uuid}/user_preferences endpoint.

Tip: When exporting user instructions, apply your access and retention policies for personal or sensitive content.

Who can use it: Claude Models API users; the field returns true or false depending on the supported model.

How to use it: Read capabilities.thinking.types.between_tools in the GET /v1/models response and choose the thinking setting accordingly.

Tip: Read this capability field to select compatible models dynamically instead of hard-coding model IDs.

Who can use it: Claude Console and Claude Managed Agents users; beta.

How to use it: Add an OpenTelemetry destination in Claude Console and enable span settings in the SDK you use.

Tip: Mask prompt content in traces and store only latency, token, and tool-call metrics by default.

Who can use it: Claude Platform on AWS users.

How to use it: Create a scheduled deployment for Managed Agents and select the AWS Platform environment as the target.

Tip: Use idempotent operations and safeguards against duplicate runs for scheduled tasks.

Who can use it: Beta; requires the managed-agents-2026-04-01 beta header and a workflows enabled configuration in the multiagent field.

How to use it: Set multiagent: {type: multiagent_20261001, workflows: {type: enabled}} in the agent definition and monitor workflow_run events.

Tip: Test the workflow on a small set of documents and verify stage outputs and reruns of failed agents.

Who can use it: Dashboards is in beta on paid plans; Motion is in beta on Team and Enterprise. An Enterprise administrator must enable it in Artifacts settings.

How to use it: Request a dashboard in the chat box or type /motion to open the Motion option.

Tip: Verify the query and last refresh time for every chart in a dashboard before sharing it.

Who can use it: Free, Pro, Max, Team, and Enterprise; on Enterprise, availability depends on administrator policies, with the default enablement date specified as October 15, 2026.

How to use it: Request Docs, Slides, or Design in any conversation, or choose a template from the Artifacts tab.

Tip: Before sharing team templates, have the Enterprise administrator check Artifacts and sharing policies.

Who can use it: Beta on all paid Claude plans; in Team and Enterprise, an owner or primary owner must enable the connectors.

How to use it: Install the add-on from Google Workspace Marketplace and use Extensions > Claude > Open Claude; to edit from chat, enable the Google connectors.

Tip: Keep the default Ask before edits mode and review each change in the approval card.

Who can use it: Claude API, Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry; Türkiye is on the list of supported regions, but no separate rollout for Türkiye was specified for this release.

How to use it: Use the claude-haiku-5-5 model ID on Claude Platform; in Claude apps, select Haiku 5.5 from the model picker.

Tip: Try Haiku 5.5 as a helper model alongside more expensive models for summarization, classification, compaction, and subagent tasks.

Who can use it: The official announcement covers Max, Ultra, and Team; the help article details eligibility for Max and Team. Free, Pro, and Enterprise are not eligible.

How to use it: Use claude.ai > Settings > Billing or, for Team, Organization settings > Billing > API credits > Link organization.

Tip: Since you can link the credit to only one Console organization, check your choice before selecting a production or testing organization.

Who can use it: Beta for Python and TypeScript SDK users; Haiku 5.5 is especially targeted at fast, high-volume use.

How to use it: Subclass the browser use or computer use toolset class in the SDK and implement your own automation method.

Tip: Before using these with real accounts, verify URL permissions and the human approval callback in a limited test environment.

Who can use it: Claude API and Claude Platform surfaces with token-based pricing.

How to use it: No changes are needed to existing prompt caching requests; monitor Sonnet 5.5 usage at the new price.

Tip: Get more value from the discount by caching shared system instructions for long tasks.

Who can use it: Claude Managed Agents; limited network environments with web tools enabled.

How to use it: Add the required hosts to allowed_hosts in the environment definition, and bring the URL into context through a user message or web_search result before calling web_fetch.

Tip: Test allowed_hosts and allowed_domains together to verify redirect and subdomain behavior.

Who can use it: Cybersecurity professionals and organizations whose eligibility is verified; an application and program approval are required.

How to use it: Verify your organization and intended use through the Cyber Verification Program application process.

Tip: Clearly document the defensive scope, human approval points, and abuse-prevention controls in your application.

Who can use it: Claude Models API users.

How to use it: Read the capabilities.server_tools.web_search and code_execution fields in the response to GET /v1/models or GET /v1/models/{model_id}.

Tip: Automatically configure the toolset based on these fields instead of including unsupported tools in the request body.

Who can use it: Claude Code 2.1.287 and later; trusted marketplace plugins and local plugins.

How to use it: Install a mod plugin or install one from the marketplace with /plugin install; run /reload-plugins when needed.

Tip: Because Mods run code with your permissions, install them only from sources you trust and review the manifest.

Who can use it: Claude Models API users.

How to use it: Read the line field in the model list response; its value may be null for models that do not belong to a family.

Tip: For routing that can handle new model releases, use the line field instead of extracting family names from ID strings with regex.

Who can use it: Dreams research preview; Managed Agents access and an account for a supported model are required.

How to use it: Select a model from a supported model family in the Dreams configuration.

Tip: Have a person review automatically generated workflow suggestions before adding them to production Skills.

Who can use it: The model will be available in the Claude API until November 30, 2026; it is planned to be retired from the API afterward.

How to use it: Replace the model ID with claude-sonnet-5-5 and apply the differences in thinking and tool_choice documented in the Sonnet 5.5 migration guide.

Tip: Before the retirement date, compare staging and production responses using the same evaluation set.

Who can use it: Claude Platform developers; stable client.organization and ant organization surfaces are available in new SDK releases and the ant CLI.

How to use it: Upgrade to the relevant version of the Python, TypeScript, C#, Go, Java, PHP, or Ruby SDK and use client.organization.

Tip: Rather than removing old beta calls immediately, compare response schemas with the stable methods for a while.

Who can use it: Claude API, Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Azure; Türkiye is on the list of supported regions, with no dedicated Türkiye rollout specified. Text watermarking is applied to new models in the EU.

How to use it: Use the claude-sonnet-5-5 model ID on Claude Platform; in Claude apps, select Sonnet 5.5 from the model picker.

Tip: Start with Low or Medium effort for routine coding and document tasks, and increase effort only for complex tasks.

Who can use it: Developers on paid Claude plans; a single MCP connector or a plugin bundle hosted on GitHub can be submitted.

How to use it: Submit your plugin at claude.ai/directory/manage/new, fix the automated validation results, and publish it after approval.

Tip: Run the pre-submission test suite to validate MCP 2.0, MCP Apps, and Enterprise Managed Auth extensions early.

Who can use it: Claude Platform, Amazon Web Services, Google Cloud, and Microsoft Azure; verification programs apply to high-risk work such as cybersecurity and life sciences.

How to use it: Use the claude-opus-5-5 model ID on Claude Platform; in Claude Code or Claude apps, select Opus 5.5 from the model picker.

Tip: Route context-heavy work such as long, open-ended code migrations to Opus 5.5, and narrow, repetitive tasks to Sonnet or Haiku.

Who can use it: Claude Enterprise; a Compliance Access Key and the read:compliance_user_data scope are required. The cache diagnostics beta header is available to API users.

How to use it: Filter Compliance sessions with product_surface=claude_in_chrome; read the diagnostics field using the cache-diagnosis-2026-04-07 header.

Tip: When storing Chrome transcripts, separately review user privacy, access scope, and retention period.

Who can use it: Gradual rollout; initially available on web, desktop, and mobile for Pro and Max. In Team beta and Enterprise, the Chat and Cowork unified setting must be enabled.

How to use it: In Claude, write the desired output directly; manage connected apps under Customize > Connectors and global instructions under Settings > Your Claude.

Tip: For tasks with real-world impact, check the Auto/Manual permission setting in the message box and approve critical steps.

Who can use it: Artifacts is available on all plans, including Free; Docs, Slides, and Design are in beta on Enterprise and remain off until an administrator enables them.

How to use it: Ask for a design, deck, or doc in a conversation, or select Output > the relevant template from the message box.

Tip: For enterprise visual consistency, first import your design system on the Artifacts page.

Who can use it: Beta on all paid Claude plans; requires approval through Salesforce’s beta program and setup by an organization administrator.

How to use it: Have an administrator request access through AgentExchange, connect Salesforce for the organization, and install the plugin from Claude Marketplace.

Tip: Keep the default approval step for CRM writes and limit automatic updates to low-risk fields.

Who can use it: Claude API beta; requires the compact-2026-09-04 beta header.

How to use it: Send the compaction parameter at the top level of the request, then use the returned signed compaction block as the first block in the next request.

Tip: To preserve short-term context, leave the latest user and tool turns intact and compact only the older section.

Who can use it: Claude API beta; especially for Claude Fable 5.1 and new accounts using preserved thinking.

How to use it: Send the thinking-binding-controls-2026-08-01 header and log thinking_mismatch_allowed records in input_transformations.

Tip: Before moving to enforcement, measure which client or history edit each mismatch record came from.

Who can use it: Claude Managed Agents; server-side permission policies.

How to use it: Add an auto rule to the permission policy and process the evaluation and evaluated_permission fields in the agent event stream.

Tip: For tools that can write data or incur costs, start with rules that require approval rather than auto.

Who can use it: ant CLI 1.32.0 and access to Claude Managed Agents.

How to use it: Run the ant beta:sessions connect command; use the --web option to open the Claude Console session viewer locally.

Tip: For long-running agent tasks, use the terminal connection for monitoring and approvals; don’t print secrets to terminal history.

Who can use it: Claude API; integrations using the cache-diagnosis-2026-04-07 beta header.

How to use it: Send diagnostics:{previous_message_id:null} in the first request, then send a diagnostics object containing the previous message ID in subsequent requests.

Tip: Before enabling cache diagnostic logs in production, review the retention policy for sensitive request fingerprints.

Who can use it: ant CLI 1.30.0 and Claude Platform resources.

How to use it: Create resource definition files in the repository, run ant apply, and add the generated claude-lock.json file to version control.

Tip: Review the plan output before applying in CI, and use a separate lock file for production resources.

Who can use it: Applicable models on Google Cloud; requires the mid-conversation-output-config-2026-07-01 beta header.

How to use it: Add a role=system message and output_config.effort to the messages array.

Tip: Preserve the cache by using low effort for routine tasks and high effort on the final turn when verification is required.

Who can use it: Fable 5.1 is available on Claude API, Amazon Bedrock, AWS, Google Cloud, and Microsoft Foundry; Mythos 5.1 is available through verified cybersecurity and life sciences programs, initially to a limited number of U.S. organizations.

How to use it: Use the claude-fable-5-1 model ID in the API; apply to the appropriate trusted access program for Mythos 5.1.

Tip: For preserved thinking and tool_choice compatibility in Fable 5.1, apply the request changes in the migration guide before upgrading.

Who can use it: Claude API and supported cloud deployments with token-based pricing; Mythos access is limited to verified programs.

How to use it: Use prompt caching to resend the same context; specify the model ID as claude-fable-5-1 or, if authorized, claude-mythos-5-1.

Tip: For long, tool-heavy tasks, measure cache read savings by moving fixed instructions into the cache.