🐛 Bug Fixes
- Engagement Cloud segments and profiles load again. KIO again reads segments, profiles, and A/B campaigns from CoreMedia Engagement Cloud. Since backend 2.3.0, these requests failed and KIO couldn't use any Engagement Cloud data.
- Playbook details no longer get lost in delegated tasks. Previously, KIO copied playbook instructions into the tasks it delegates to its specialized agents, and some details from the playbooks got lost. The agents now see which playbooks apply to the request and load the original playbook when they need more details, including playbooks that another playbook references as
[[<playbook-id>]].
- Follow-up suggestions no longer go missing. KIO sometimes showed no follow-up suggestions below an answer, even though the model had generated them. KIO now shows them reliably.
- Status messages stay in the user's language more reliably. KIO's instructions now require status messages to use the language of the user's request. Previously, some messages could switch to another language, such as the language of the edited content or of a requested tone of voice.
- New content follows the language of its site. When creating content, KIO now determines the language from the site the content is created in, unless the user requests a language or the content is based on existing content. Previously, KIO could write content in another language, for example when a tone of voice or brand name suggested a different market.
- Image texts go to the right image. When KIO wrote texts for several images at once, such as captions or detail texts for selected pictures, it sometimes applied a text to the wrong image. KIO now keeps track of which image belongs to which content item.
- Content searches by date and content fields work. KIO now finds content by fields such as a validity date, for example "articles that expire before next week", by creator, by tag, and by links between content items, such as unused pictures. Previously, these repository searches failed with a malformed query error.
- Content variants get their targeting. KIO now resolves named Engagement Cloud profiles and segments when creating a variant, and reports when it can't find them.
- Existing variants can be retargeted. Editors can replace or clear the Engagement Cloud segments and profiles assigned to an existing content variant.
- KIO works on the content you mean. For requests like "this" or "it", KIO now works on the open content, and asks which content is meant when the open content, the Library selection, and content from earlier in the conversation leave it unclear. Previously, KIO could change content still selected in the Library, or the baseline of an open variant, instead of the open content.
Validated LLM Models
OpenAI
| Model |
Model ID |
| GPT-5.6-Terra |
gpt-5.6-terra |
| GPT-5.6-Luna |
gpt-5.6-luna |
| GPT-6-Luna |
gpt-6-luna |
Azure AI
| Model |
Model ID |
| GPT-5.6-Terra |
gpt-5.6-terra |
Amazon Bedrock Converse
| Model |
Model ID |
| Anthropic Claude Sonnet 4.6 |
us.anthropic.claude-sonnet-4-6 |
| Anthropic Claude Haiku 4.5 |
us.anthropic.claude-haiku-4-5-20251001-v1:0 |
See Supported LLM Providers for the full compatibility matrix.