Guide the content agents to prefer "content" and "content type" over "node" and "node type"

Created on 7 February 2025, about 2 months ago

Problem/Motivation

Drupal's very helpfully confusing naming between node/content ends up coming out in responses... We should try and instruct the LLM in how to both interpret and respond.

Steps to reproduce

Ask it to create a content type named titled "Blog" when "Blog" already exists. It will fail, but the response is typically along the lines of "the node type blog already exists" .

Proposed resolution

The following instruction helped a lot:

For reference, the term content is synonymous with node and term content type is synonymous with node type. You should always use content and content type in your response, unless the user uses node or node type.

I expect we'll also need to review one-shot response etc.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

🇬🇧United Kingdom andrewbelcher

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024