Skip to content

Fix: add LangSmith to prompt-management-system.mdx #332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
orlando21 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix: add LangSmith to prompt-management-system.mdx #332

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions content/blog/prompt-management-system.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "4 Best Prompt Management Systems for LLM Developers in 2025 "
title: "5 Best Prompt Management Systems for LLM Developers in 2025 "
description: "Explore the top prompt management systems built for developers, with support for prompt versioning, tracing, and CI/CD workflows."
date: "2025-11-26"
readTime: "7 min read"
Expand All @@ -21,7 +21,8 @@ The four systems we examine are:
1. [Lilypad](#1-lilypad)
2. [Agenta](#2-agenta)
3. [PromptHub](#3-prompthub)
4. [Langfuse](#4-langfuse)
4. [Langfuse](#4-langfuse)
5. [LangSmith](#5-langsmith)

## 4 Questions to Ask When Choosing a Prompt Management Tool

Expand Down Expand Up @@ -270,6 +271,21 @@ Langfuse offers:
* Dynamic referencing of other prompts within a prompt, enabling modular and reusable prompt architectures that support DRY (Don't repeat yourself) prompt engineering directly in the UI.
* Structured evaluation features like datasets for benchmarking, A/B testing workflows, and user feedback capture mechanisms.

### 5. LangSmith

![LangSmith Diagram](/assets/blog/prompt-management-system/langsmith-diagram.webp)

@willbakst willbakst Dec 5, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to actually add this asset to the public folder at this path.

@orlando21 orlando21 Dec 12, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have permission to push this asset to public


[LangSmith](https://www.langchain.com/langsmith) is a closed source observability and prompt management platform for teams building with LangChain, and features a prompt hub where users can design, version, tag, and deploy prompts via a visual playground or SDK. However, LangSmith treats prompts as isolated artifacts (separate from the logic that runs them) which may introduce drift.

LangSmith allows you to:

* Save prompt versions using Git-like identifiers to keep track of changes, roll back, compare, and pin as known-good versions deployed in production.
* Embed prompts directly in applications (thanks to its tight integration with LangChain), while providing logging and analytics support across prompt workflows.
* Experiment with prompts in its playground where you can modify text, variables, and model parameters, and promote the current state to a saved version.
* Run dataset-driven evaluations using automatic scoring or human review to choose the best-performing variant.
* Log prompts, responses, latencies, and errors in order to see which prompts underperform or fail on real traffic. Visualizations and filters help you analyze how small prompt or parameter changes affect behavior, which feeds back into the prompt management loop.


## Build Reliable LLM Applications with Full Traceability

Lilypad is a [context engineering platform](/blog/context-engineering-platform) that keeps a full record of what ran, what changed, and who changed it. Lilypad versions everything that matters to make it easier to implement [prompt engineering best practices](/blog/prompt-engineering-best-practices): code, inputs, outputs, and even annotations, so you get a full audit trail, reproducible results, and reliable deployments.
Expand Down