Skip to content

💡 Request - Warn before replacing array/rich text fields in update_entry #320

@markferritto

Description

Is your feature request related to a problem? Please describe.
When updating entries with update_entry, providing a full value for an array field (e.g. sections) or rich text field replaces the entire field. The AI often assumes “update this section” means “replace the whole thing” when the user meant “add to it.” That silently removes content that was not approved for removal. Example: updating a Guidelines tab overwrote existing “Pair with labels” and “Shape” blocks instead of adding only the requested content.

Describe the solution you'd like

  • Before any destructive write to a pre-existing field that contains embedded entries or rich text, return a warning such as: “This field currently has N embedded entries. Proceeding will replace all of them.”
  • Or: a fetch-before-write gate that shows a before/after diff.
  • Or: distinguish additive operations (append to array/richText) from destructive operations (replace field entirely) in the API.

Describe alternatives you've considered

  • Relying on AI instructions to always fetch before updating — not enforced by the tool.
  • Adding more detailed docs — helps but doesn’t prevent accidental overwrites.

Additional context
Reported after content was overwritten during a docsite update. The AI had no way to know it was about to replace content the user wanted to keep.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions