AI Agents
| Module | CrestApps.OrchardCore.AI.Agent |
| Manifest ID | CrestApps.OrchardCore.AI.Agent |
The Orchard agent module surfaces agent profiles inside Orchard Core so they can participate in module-driven AI experiences such as profile-based chat, A2A hosting, and other Orchard-managed orchestration flows.
What this module adds in Orchard Core
- Orchard-aware AI tools for system, recipe, tenant, content, role, user, workflow, analytics, and communication scenarios
- agent-related profile editing support through the Orchard AI profile experience
- compatibility with Orchard modules such as A2A host, recipes, tenants, content types, contents, and workflows when those features are enabled
How to use it in Orchard
- Enable AI Agents together with the base AI features.
- Go to Artificial Intelligence -> Profiles.
- Create or edit the AI profile that should participate in agent scenarios.
- Enable the related Orchard features if you want additional tool categories to appear.
The exact tool set available to agents depends on which Orchard modules are enabled. For example, tenant-management tools only light up when Orchard tenants support is enabled, and recipe tools depend on Orchard recipes support.
For the complete Orchard-specific AI function catalog, including the feature that enables each function and its description, see AI Tools.
Orchard-specific role of agent profiles
In Orchard Core, agent profiles are useful when you want:
- specialized AI capabilities that can be attached to other AI experiences
- locally hosted agents that can be exposed through A2A Host
- Orchard-aware AI automation over content, tenants, recipes, roles, users, and workflows
Feature composition
The agent module becomes more useful as you add Orchard features:
- Recipes adds recipe-related tools
- Tenants adds tenant-management tools
- Contents and Content Types add content-management tools
- Workflows adds workflow-related tools
Shared framework documentation
The reusable agent model, agent invocation patterns, and delegation concepts are documented in CrestApps.Core: