langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Integrate LangSmith Prompt SDK for better management, version control, and tracking of prompts. #6619

New Issue
Closed
opened 2026-02-21 18:16:35 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:16:35 -05:00
Owner
Copy Link
Copy Source

Originally created by @nickjfrench on GitHub (Nov 7, 2024).

Originally assigned to: @ZhouhaoJiang on GitHub.

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

LangSmith has great functionality to test Prompts within it's platform based off traces from Dify. I'd love to be able to take the prompt I've been version tracking in LangSmith and automatically use it in Dify and viceversa.
E.g. I update it on LangSmith, Dify uses it straight away in the next user call.
This would allow me to better track all prompts I'm using within the Dify platform.

LangSmith has an SDK api for push and pulling of prompts within their system.
https://docs.smith.langchain.com/prompt_engineering/how_to_guides/prompts/manage_prompts_programatically

2. Additional context or comments

Maybe to integrate this within Dify, some version of LangSmiths prompt library would be useful that has syncing capabilities with LangSmith.

Also I don't think it's worth competing LangSmith on this feature, but instead integrating with it.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @nickjfrench on GitHub (Nov 7, 2024). Originally assigned to: @ZhouhaoJiang on GitHub. ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. LangSmith has great functionality to test Prompts within it's platform based off traces from Dify. I'd love to be able to take the prompt I've been version tracking in LangSmith and automatically use it in Dify and viceversa. E.g. I update it on LangSmith, Dify uses it straight away in the next user call. This would allow me to better track all prompts I'm using within the Dify platform. LangSmith has an SDK api for push and pulling of prompts within their system. https://docs.smith.langchain.com/prompt_engineering/how_to_guides/prompts/manage_prompts_programatically ### 2. Additional context or comments Maybe to integrate this within Dify, some version of LangSmiths prompt library would be useful that has syncing capabilities with LangSmith. Also I don't think it's worth competing LangSmith on this feature, but instead integrating with it. ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:16:35 -05:00
yindo closed this issue 2026-02-21 18:16:35 -05:00
yindo commented 2026-02-21 18:16:35 -05:00
Author
Owner
Copy Link
Copy Source

@ZhouhaoJiang commented on GitHub (Nov 8, 2024):

@nickjfrench Hello, thank you for your suggestion. However, Dify is already integrated with LLM operations platforms such as Langfuse and Langsmith to expand its third-party capabilities. I reviewed Langsmith’s documentation on prompt engineering, but it doesn’t align with our current needs or development direction. Dify is compatible with various models, and integrating third-party prompt engineering features would not be consistent with our product vision. Dify itself already supports custom prompts, which provides the flexibility we need.

@ZhouhaoJiang commented on GitHub (Nov 8, 2024): @nickjfrench Hello, thank you for your suggestion. However, Dify is already integrated with LLM operations platforms such as Langfuse and Langsmith to expand its third-party capabilities. I reviewed Langsmith’s documentation on prompt engineering, but it doesn’t align with our current needs or development direction. Dify is compatible with various models, and integrating third-party prompt engineering features would not be consistent with our product vision. Dify itself already supports custom prompts, which provides the flexibility we need.
yindo commented 2026-02-21 18:16:35 -05:00
Author
Owner
Copy Link
Copy Source

@nickjfrench commented on GitHub (Nov 8, 2024):

I understand, thanks for looking into it

@nickjfrench commented on GitHub (Nov 8, 2024): I understand, thanks for looking into it
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6619
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?