Cite as: Real Problem AI problem “Why do my prompts live in so many places that I can't tell which version broke prod?”. Opportunity score 7.7 out of 10 (severity 7, AI feasibility 9, market signal 8, competition gap 6). Category AI / Agents. Trend LLM. Source signal: Hacker News "prompt versioning is the new database migrations" thread (May 2026), PromptLayer and Humanloop changelog discussions.. Canonical URL: https://www.realproblem.ai/archive/why-do-my-prompts-live-in-22-places-and-i-cant-tell-which-version-broke-prod.
Why do my prompts live in so many places that I can't tell which version broke prod?
Prompts live in Python strings, Notion docs, Cursor files, PromptLayer, and Bob's head. When the agent breaks in the middle of the night, nobody knows which prompt is live.
Who has it: Teams of 2-15 shipping LLM features (support, sales, internal tools).
Evidence
Teams describe a production regression caused by someone editing a prompt directly in a prompt tool, with no review, test or rollback, followed by hours of manual diffing.
Our summary of a complaint that recurs in public posts, not a quote. Nobody submitted it to Real Problem AI.
Seen in: Hacker News "prompt versioning is the new database migrations" thread (May 2026), PromptLayer and Humanloop changelog discussions.Scoring breakdown
Existing players
- PromptLayer · Catalog without strong git semantics
- Humanloop · Closer, enterprise-priced
- LangSmith · Tracing-first, weak prompt diff UX
What they are missing
Git-native prompt management: every prompt is a file, branched, PR'd, eval'd in CI, and shippable with feature flags. Diff a prod prompt vs canary in one click. Replay yesterday's traffic against the new prompt before merging.
Stack hint
#AI16 · Canonical URL: https://www.realproblem.ai/archive/why-do-my-prompts-live-in-22-places-and-i-cant-tell-which-version-broke-prod