PR #23968: fix(prompt_studio): fall back to dotprompt_content from DB when Prompt Studio editor loads

• Repository: BerriAI/litellm
• Author: NIK-TIGER-BILL
• State: open | merged: False
• Link: https://github.com/BerriAI/litellm/pull/23968

Description (problem / solution / changelog)

Summary

Fixes #23935

When prompts are saved via the Prompt Studio UI or PUT /prompts/{id}, the content is stored in litellm_params.dotprompt_content (and sometimes prompt_data.content). However, the GET /prompts/{id}/info endpoint only read content from the in-memory prompt callback, which is only populated for file-based dotprompt — not for UI-saved prompts.

Result: the Prompt Studio editor always opened blank after saving via the UI.

Changes

Added a fallback in get_prompt_info(): after checking the callback, read litellm_params.dotprompt_content and prompt_data.content from the stored PromptSpec to populate raw_prompt_template when the callback did not yield content.

Testing

1. Open Prompt Studio
2. Create and save a prompt via the UI
3. Reopen the prompt — editor now shows the saved content instead of being blank

Changed files

• litellm/proxy/prompts/prompt_endpoints.py (modified, +19/-0)

PR #23972: fix(prompts): Prompt Studio fails to load prompts saved via UI

• Repository: BerriAI/litellm
• Author: BillionClaw
• State: open | merged: False
• Link: https://github.com/BerriAI/litellm/pull/23972

Description (problem / solution / changelog)

Issue

Prompt Studio fails to load any prompt that was saved via the Prompt Studio UI "Update" button or the PUT /prompts/{id} API using prompt_data. The editor opens blank with a generic "New prompt" placeholder instead of the actual prompt content.

Root cause: The Prompt Studio save path writes prompt content to litellm_params.prompt_data.content (body only, no YAML frontmatter) and sets litellm_params.dotprompt_content = null. But the Prompt Studio load path only reads from litellm_params.dotprompt_content:

let t = e?.prompt_spec?.litellm_params?.dotprompt_content || "";
if (!t) throw Error("No dotprompt_content found in API response");

When dotprompt_content is null, it throws and silently falls back to a blank editor. The prompt data is actually persisted correctly in prompt_data.content — it's just never read back.

Fix

Modified parseExistingPrompt to:

1. First try to parse dotprompt_content (existing behavior)
2. If not available, fall back to parsing prompt_data with both direct and nested formats
3. Updated error message to mention both data sources

Changes

• Modified parseExistingPrompt in utils.ts to check for prompt_data as fallback
• Added parsePromptData helper function to handle both direct {content, metadata} and nested {prompt_id: {content, metadata}} formats
• Added comprehensive tests for prompt_data parsing scenarios

Testing

All 37 tests pass, including 6 new tests for prompt_data fallback:

• Parsing prompt_data with direct format
• Parsing prompt_data with nested format
• Preferring dotprompt_content over prompt_data
• Parsing developer messages from prompt_data
• Parsing tools from prompt_data
• Default values for empty prompt_data

Fixes #23935

Changed files

• ui/litellm-dashboard/src/components/prompts/prompt_editor_view/utils.test.ts (modified, +138/-1)
• ui/litellm-dashboard/src/components/prompts/prompt_editor_view/utils.ts (modified, +78/-2)