Can the prompt agent update API please be idempotent?

[TWolversonReply]

Technical Feedback

If I deploy prompt agents from continuous integration, a new version is created on update regardless of whether the prompt has changed. This is likely to produce an endlessly growing tail of identical versions that are a nuisance for ongoing support.

Desired Outcome

Describe the desired outcome.

Current Workaround

Describe the current workaround.

[jubins]

Totally agree with this. The current behavior makes CI/CD pipelines messy since every pipeline run creates a new version even when nothing has changed, and over time you end up with hundreds of identical versions that are impossible to audit or clean up.

A clean fix would be for the update API to compute a hash or fingerprint of the prompt content and config, and skip the version bump if nothing has changed. Essentially the same idempotency pattern that tools like Terraform and Helm use.