Supported AI modules
CCC pushes context into an AI call only when it can identify the caller.
Agent runs are identified through the AI Agents events. Any other
chat() call is identified by its request tags, and a consumer type has
to claim those tags before context reaches it. See
Consumer API for how to write one.
A module that sends no tags, or whose tags no consumer type claims, gets no push. That is the usual reason a feature appears to ignore its configured context.
Coverage in 1.0.x
Each row was checked against the module release named in the last column.
| Module or call site | How CCC identifies it | Push in 1.0.x | Checked |
|---|---|---|---|
| AI Agents — every agent, including agents behind AI Assistants | agent consumer type, shipped with CCC |
Yes | CCC 1.0.0-rc2 |
| AI Answers | Runs an AI Agents agent, so the agent type covers it |
Yes | 1.0.0-beta4 |
| AI Automators | automator consumer type, shipped with CCC. Present only when ai_automators is installed |
Yes, off by default | AI 1.4.12 and 1.5.2 |
| AI CKEditor | ckeditor consumer type, shipped with that project, from 1.5.0-beta2. One consumer per CKEditor tool |
Yes | 1.5.0-beta5 |
| AI Validations | validation consumer type, shipped with that project, from 1.4.0. One consumer per AI field validation rule, matched by the tag ai_validations:{rule_uuid} |
Yes | 1.4.0 |
| AI Translate — the agent run, when translation is driven by an agent or the Tool API | Runs as an agent, so the agent type covers the agent's own prompt |
Yes | 1.4.4 |
| AI Translate — the translation request itself, on every path: the Translate tab, Drush, an agent, or the Tool API | The chat-proxy provider sends the tag ai_translate, which no consumer type claims in this release. A translate type is merged in ai_translate#3585555 and is not in a release yet |
No, planned | 1.4.4 |
| AI Assistants that are not backed by an agent | Sends the tag ai_assistant_api, which CCC excludes on purpose. See Chatbots and AI Assistants |
No | AI 1.5.2 |
| AI Content Suggestions | Sends the tag ai_content_suggestions, but no consumer type claims it |
No | 1.5.2 and 1.6.0-alpha2 |
| AI Image Alt Text | Sends the tag ai_image_alt_text, from 1.0.4, but no consumer type claims it. Earlier releases send no tags |
No | 1.0.4 |
| AI Search, the RAG assistant action | Calls chat() with no tags. It runs inside a classic AI Assistant. For search answers with context, use AI Answers |
No | 2.0.0-alpha3 |
For AI Automators, turn on Push context automatically for each
automator that should receive context. The automator type defaults
push_enabled to FALSE, so installing the module or enabling the
consumer type does not turn on push for individual automators.
Driving AI Translate from an agent gives the agent its context, but the
translation request the tool sends is a separate chat() call that
carries only the ai_translate tag. Until a release of AI Translate has
a consumer type that claims that tag, no path delivers context to the
text being translated.
What a module needs to receive push
For the generic chat path, all three requirements must be met:
- Request tags on its
chat()call. The third argument ofchat()carries them. A call with no tags cannot be identified. - A consumer type that claims those tags. It maps a tag to a consumer ID, so the site can configure that consumer like any other.
- No excluded request tags. CCC skips generic routing if the call
carries
ai_agents,ai_assistant_api,ai_context, orai_context_subcontext, even when a consumer type claims another tag on the same call. Agent requests use the agent subscribers instead. Assistant requests (ai_assistant_api) get no push on the generic path. The two internal CCC tags prevent recursive context selection.
Two shipped examples are worth copying. AiContextConsumerTypeCKEditor
in AI CKEditor registers one consumer per CKEditor tool.
AiContextConsumerTypeValidation in AI Validations registers one per AI
field validation rule and matches the tag ai_validations:{rule_uuid}.
Both live in their own project, not in CCC.
The table describes automatic push. A module with no consumer type can
still pull context from its own code with getRenderedContext() on the
ai_context.selection_factory service; see
API stability.
Module versions move. If a feature here is listed as receiving no push and you believe it should, check whether that project has since added a consumer type before filing against CCC.
Related documentation
- Consumer configuration -- configuring the consumers that do receive context
- Consumer API -- writing a consumer type for a module that is not listed here
- Page and entity context -- how context reaches a request once the caller is identified
- Access boundaries -- what reaches AI tools outside the site