Dot AI — Issues and Improvements

[KevinDavilaDotCMS]

Description

Some bugs and UX improvements have been identified across the Dot AI feature, including the Image Playground, Block Editor, and the "Search and Chat with dotCMS" interface. This task tracks all reported items as sub-tasks.

Acceptance Criteria

• [Sub-task 1] Embeddings/indexes fail outside SYSTEM_HOST

  • Embeddings and indexes should work regardless of whether the host is listed in SYSTEM_HOST.
  • Investigate the validation/resolution logic and fix so non-SYSTEM_HOST origins are supported.

• [Sub-task 2] Image Playground — size dropdown uses hardcoded values incompatible with some models

  • Replace the fixed size dropdown with an editable/free-input field so users can specify dimensions supported by their selected model.
  • Ensure the new input includes basic format validation (e.g., widthxheight).

• [Sub-task 3] Block Editor — same size dropdown issue as Image Playground

  • Apply the same fix from Sub-task 2 to the Block Editor size selector.

• [Sub-task 4] Image Playground — results overflow the container
  • Generated image results should be fully visible and not overflow their container.
  • Fix layout/CSS so results are properly constrained and scrollable if needed.

• [Sub-task 5] "Search and Chat with dotCMS" — form submits despite HTML validation errors

  • When required fields fail HTML validation, the form should not submit.
  • The endpoint should not be called until all fields are valid.
  • Fix the form submission handler to respect validation state before firing the request.

• [Sub-task 6] "Search and Chat with dotCMS" — model dropdown is always empty

  • Clarify and document whether the model values in the dropdown should match the user-configured values or come from a separate source.
  • Populate the dropdown correctly based on that definition.

• [Sub-task 7] client.ai.search() — non-existent indexName returns empty array without explanation

  • When an unknown indexName is passed, the API (/api/v1/ai/search) should return a descriptive error message instead of an empty array.
  • Update the response to clearly indicate that the index was not found.

---

Priority

None

Additional Context

• Endpoint involved in Sub-task 7: /api/v1/ai/search
• Sub-tasks 2 and 3 share the same root cause — the size values are hardcoded and not validated against the selected model's supported dimensions.
• Sub-tasks 5 and 6 both affect the "Search and Chat with dotCMS" interface and may be addressed in the same component.