## Development strategy - All work for this revamp lands on a long-lived integration branch `1.x-ai-revamp`, cut from `1.x`. - Each child issue is developed in its own issue fork; its MR targets `1.x-ai-revamp`, not `1.x`. - `1.x` is merged into `1.x-ai-revamp` regularly (merge, never rebase) to keep it current. - Once all child issues are merged, `1.x-ai-revamp` is merged into `1.x` in a single integration MR. - Breaking changes are acceptable (`canvas_ai` is beta). The upgrade path is a `hook_update_N` that deletes stale `ai_agent` config entities plus system-prompt/config updates; no data migration. ## Key changes | Agent deleted | Replaced with | |---------------|---------------| | Drupal Canvas Template Builder Agent and its tools | Drupal Canvas Page Builder Agent with new tools | | Drupal Canvas Title Generation Agent and its tools | Drupal Canvas Page Builder Agent with new tools | | Drupal Canvas Metadata Generation Agent and its tools | Drupal Canvas Page Builder Agent with new tools | | Drupal Canvas AI Orchestrator and its tools | Drupal Canvas Agent (new) — answers questions about Drupal Canvas, possibly with a tool that reads existing documentation in future | ## Prototype [Drupal Canvas AI V2.html](/uploads/c314deceeee5e425d1c8a61550b496c4/Drupal_Canvas_AI_V2.html) ## **Try it out — step by step** 1. **Open the HTML file on a browser. You land on the config screen.** Just look at the two things that matter: the **Main agent** dropdown and the **Tools** below it. Don't change anything yet. 2. **Click "Save configuration."** You'll see it confirm. (This applies your setup and starts a clean session.) 3. **Click through to the Canvas UI** (the editor with the chat panel). 4. **Type anything in the chat and send.** Notice: **the main agent is the one answering.** Out of the box that's the **Drupal Canvas Agent** — its job is answering questions _about_ Drupal Canvas, so it responds by explaining what it can do rather than building anything. 5. **Now click the wrench and pick the Page Builder tool**, type any prompt, and send → **watch it build the page** live in the canvas. 6. **Send again** → it takes the next step (documents the page / makes its edit), so you see the flow continue. 7. **Now go back and change the main agent and tools** (e.g. set Component Agent as main), save, and return to the chat → **notice the assistant UI changes to match** — the agent answering and the available tools update. That's the whole point: config drives the chat, and it's direct and easy to follow.