Skip to main content
Version: Latest
Technical ManualLooking for step-by-step instructions? In the User Manual: AI ProfilesChat Interactions

Claude Integration

Feature NameAI Claude Orchestrator
Feature IDCrestApps.OrchardCore.AI.Chat.Claude

This module wires the shared Claude support from CrestApps.Core into Orchard Core and exposes the related Orchard settings and editors.

Capabilities​

  • tenant-level Claude settings under Settings -> Artificial Intelligence -> Claude
  • encrypted Anthropic API key storage
  • Claude model discovery from the Anthropic models API
  • per-item Claude model overrides for AI Profiles, AI Profile templates, and Chat Interactions
  • per-item Effort level overrides (Default, Low, Medium, High)
  • template-to-profile propagation for Claude session settings

Enable the feature​

Enable AI Claude Orchestrator when you want Claude to appear as an Orchard-managed orchestrator option for:

  • AI profiles
  • AI profile templates
  • chat interactions

Orchard configuration​

Claude configuration can come from both shell configuration and tenant site settings.

appsettings.json​

The module binds shared Claude options from the CrestApps:AI:Claude section:

{
"OrchardCore": {
"CrestApps": {
"AI": {
"Claude": {
"ApiKey": "<anthropic-api-key>",
"BaseUrl": "https://api.anthropic.com",
"DefaultModel": "claude-sonnet-4-5"
}
}
}
}
}
SettingTypeDefaultDescription
ApiKeystringnullAnthropic API key. A key stored in the site settings replaces this value when API-key authentication is selected there.
BaseUrlstringhttps://api.anthropic.comAnthropic API base address.
DefaultModelstringnullModel used when a profile, template, or interaction does not select one.
note

The OrchardCore wrapper is how the host appsettings.json is shaped. A tenant that overrides these values in its own App_Data/Sites/{tenant}/appsettings.json writes the same keys without the wrapper, starting at CrestApps, because that file is already scoped to the tenant.

Site settings​

In Orchard Core, go to Settings -> Artificial Intelligence -> Claude.

From there you can configure:

  • authentication type
  • API key
  • base URL
  • default model

When API key authentication is enabled, the stored API key is encrypted at rest. The editor also uses the configured Claude connection to populate the available model list from Anthropic so Orchard users can pick a model instead of typing one manually.

Tenant site settings override the shell configuration for values such as the base URL and default model. When API-key authentication is used, the key is stored encrypted.

How Orchard users work with Claude​

Once the feature is configured, selecting the Claude orchestrator in the Orchestrator field of a profile (see AI profiles) or a chat interaction shows a Claude configuration block:

  • AI profile editors can select Claude models and an Effort level
  • AI profile template editors can store Claude model and Effort level defaults
  • chat interaction editors can pick Claude-backed model settings and an Effort level

When you create a new AI Profile from a profile-source template, the saved Claude settings are copied to the generated profile so the template can act as a reusable Claude preset.

If the site is not configured with an API key, the Claude model selectors remain effectively unavailable.

Shared framework documentation​

Detailed Claude runtime guidance lives in CrestApps.Core: