langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[PR #1689] [MERGED] Add Lemonade Provider #2035

New Issue
Closed
opened 2026-02-16 11:15:56 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 11:15:56 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-official-plugins/pull/1689
Author: @danielholanda
Created: 9/9/2025
Status: ✅ Merged
Merged: 9/15/2025
Merged by: @crazywoola

Base: main ← Head: dholanda/lemonade

📝 Commits (10+)

📊 Changes

13 files changed (+770 additions, -0 deletions)

View changed files

➕ models/lemonade/.difyignore (+2 -0)
➕ models/lemonade/README.md (+12 -0)
➕ models/lemonade/_assets/icon.svg (+53 -0)
➕ models/lemonade/main.py (+6 -0)
➕ models/lemonade/manifest.yaml (+31 -0)
➕ models/lemonade/models/common_openai.py (+58 -0)
➕ models/lemonade/models/llm/llm.py (+297 -0)
➕ models/lemonade/models/rerank/rerank.py (+28 -0)
➕ models/lemonade/models/text_embedding/text_embedding.py (+29 -0)
➕ models/lemonade/provider/lemonade.py (+17 -0)
➕ models/lemonade/provider/lemonade.yaml (+89 -0)
➕ models/lemonade/pyproject.toml (+21 -0)
➕ models/lemonade/requirements.txt (+127 -0)

📄 Description

Intro

Hi there 👋, I'm Daniel, one of the core developers of Lemonade. Lemonade is an LLM server that enables the use of NPU and GPU acceleration available on both Windows and Linux. We are backed by AMD, recently crossed over 1,000 stars on our GitHub, and are now we are even available of Hugging Face.

I recently came across Dify and found it very exciting! Although I was able to get Lemonade to work through the OpenAI-compatible plugin, a custom plugin for Lemonade seemed more interesting, as we can significantly improve the user experience by providing better options and error-handling for our tool. I took an initial stab at it, and got a custom plugin to work really quickly!

image

Given that this is a model provider, I would love for it to become part of the dify-official-plugins. If we can get this type of native integration, we would also be happy to do some co-marketing with the Dify team (e.g., an AMD blog showing Dify+Lemonade).

Please let me know what you think and I will be happy to work with you to get this integration done.

PR Description

The current PR shows an initial integration that is fully functional (at least on my side). If we get alignment that this is something we want to pursue, I will be happy to also create some nice documentation to go along with it.

Related Issues or Context

This PR contains Changes to Non-Plugin

  • Documentation
  • Other

This PR contains Changes to Non-LLM Models Plugin

  • I have Run Comprehensive Tests Relevant to My Changes

This PR contains Changes to LLM Models Plugin

  • My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking)
  • My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node)
  • My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.)
  • My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.)
  • My Changes Affect Structured Output Format (JSON, XML, etc.)
  • My Changes Affect Token Consumption Metrics
  • My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.)
  • Other Changes (Add New Models, Fix Model Parameters etc.)

Version Control (Any Changes to the Plugin Will Require Bumping the Version)

  • I have Bumped Up the Version in Manifest.yaml (Top-Level Version Field, Not in Meta Section)

Dify Plugin SDK Version

  • I have Ensured dify_plugin>=0.3.0,<0.5.0 is in requirements.txt (SDK docs)

Environment Verification (If Any Code Changes)

Local Deployment Environment

  • Dify Version is: , I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration.

SaaS Environment

  • I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-official-plugins/pull/1689 **Author:** [@danielholanda](https://github.com/danielholanda) **Created:** 9/9/2025 **Status:** ✅ Merged **Merged:** 9/15/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `dholanda/lemonade` --- ### 📝 Commits (10+) - [`3e65bad`](https://github.com/langgenius/dify-official-plugins/commit/3e65bad5961f79ec82f1b58919183727cb4ca760) Initial implementation - [`c6f1f50`](https://github.com/langgenius/dify-official-plugins/commit/c6f1f50f6f016cab9f256433d9d0a1606f8c6daa) Add icon and fix description - [`c332078`](https://github.com/langgenius/dify-official-plugins/commit/c332078e442f7cba6eea94d3638573f9316af8e0) Remove api key - [`ccb7229`](https://github.com/langgenius/dify-official-plugins/commit/ccb722954c44c7014bacd67c68a5ef6c7c240f53) Remove unecessary parameters - [`57b8af8`](https://github.com/langgenius/dify-official-plugins/commit/57b8af88d52042014806ab5ef166908b65b74f25) suppress function calling options - [`b1b5004`](https://github.com/langgenius/dify-official-plugins/commit/b1b50041e5fdd411d54534e0d8969cc4548fa521) Fix verification issues - [`683e97f`](https://github.com/langgenius/dify-official-plugins/commit/683e97ff62eecb2cb45061aed8a04d9a1a9d814f) Health - [`e63d02f`](https://github.com/langgenius/dify-official-plugins/commit/e63d02faf86dfb116d951a3b873b65741fe072d3) Functional - [`d8cd4a8`](https://github.com/langgenius/dify-official-plugins/commit/d8cd4a86f24bab7858e40dc5cb127c4af41491b8) Good errors when server is not running - [`98c9d66`](https://github.com/langgenius/dify-official-plugins/commit/98c9d66740a842a83e2b8c991d33234c3a45697d) Add message when model not found ### 📊 Changes **13 files changed** (+770 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `models/lemonade/.difyignore` (+2 -0) ➕ `models/lemonade/README.md` (+12 -0) ➕ `models/lemonade/_assets/icon.svg` (+53 -0) ➕ `models/lemonade/main.py` (+6 -0) ➕ `models/lemonade/manifest.yaml` (+31 -0) ➕ `models/lemonade/models/common_openai.py` (+58 -0) ➕ `models/lemonade/models/llm/llm.py` (+297 -0) ➕ `models/lemonade/models/rerank/rerank.py` (+28 -0) ➕ `models/lemonade/models/text_embedding/text_embedding.py` (+29 -0) ➕ `models/lemonade/provider/lemonade.py` (+17 -0) ➕ `models/lemonade/provider/lemonade.yaml` (+89 -0) ➕ `models/lemonade/pyproject.toml` (+21 -0) ➕ `models/lemonade/requirements.txt` (+127 -0) </details> ### 📄 Description # Intro Hi there 👋, I'm Daniel, one of the core developers of Lemonade. Lemonade is an LLM server that enables the use of NPU and GPU acceleration available on both Windows and Linux. We are [backed by AMD](https://www.amd.com/en/developer/resources/technical-articles/unlocking-a-wave-of-llm-apps-on-ryzen-ai-through-lemonade-server.html), recently crossed over 1,000 stars on [our GitHub](https://github.com/lemonade-sdk/lemonade), and are now we are even [available of Hugging Face](https://www.linkedin.com/posts/danielholandanoronha_localllm-opensourceai-technology-activity-7363629526658011138-Mdhk). I recently came across Dify and found it very exciting! Although I was able to get Lemonade to work through the OpenAI-compatible plugin, a custom plugin for Lemonade seemed more interesting, as we can significantly improve the user experience by providing better options and error-handling for our tool. I took an initial stab at it, and got a custom plugin to work really quickly! <img width="1417" height="741" alt="image" src="https://github.com/user-attachments/assets/fc402669-98de-4da6-a26e-3bffee14c907" /> Given that this is a model provider, I would love for it to become part of the `dify-official-plugins`. If we can get this type of native integration, we would also be happy to do some co-marketing with the Dify team (e.g., an AMD blog showing Dify+Lemonade). Please let me know what you think and I will be happy to work with you to get this integration done. ## PR Description The current PR shows an initial integration that is fully functional (at least on my side). If we get alignment that this is something we want to pursue, I will be happy to also create some nice documentation to go along with it. ## Related Issues or Context <!-- ⚠️ NOTE: This repository is for Dify Official Plugins only. For community contributions, please submit to https://github.com/langgenius/dify-plugins instead. - Link Related Issues if Applicable: #issue_number - Or Provide Context about Why this Change is Needed --> ## This PR contains Changes to *Non-Plugin* <!-- Put an `x` in all the boxes that apply by replacing [ ] with [x] For example: - [x] Documentation --> - [ ] Documentation - [ ] Other ## This PR contains Changes to *Non-LLM Models Plugin* - [ ] I have Run Comprehensive Tests Relevant to My Changes <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> ## This PR contains Changes to *LLM Models Plugin* <!-- LLM Models Test Example: --> <!-- https://github.com/langgenius/dify-official-plugins/blob/main/.assets/test-examples/llm-plugin-tests/llm_test_example.md --> - [ ] My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Structured Output Format (JSON, XML, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Token Consumption Metrics <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> - [ ] Other Changes (Add New Models, Fix Model Parameters etc.) <!-- 📷 Include Screenshots/Videos Demonstrating the Fix, New Feature, or the Behavior Before/After Breaking Changes. --> ## Version Control (Any Changes to the Plugin Will Require Bumping the Version) - [ ] I have Bumped Up the Version in Manifest.yaml (Top-Level `Version` Field, Not in Meta Section) <!-- ⚠️ NOTE: Version Format: MAJOR.MINOR.PATCH - MAJOR (0.x.x): Reserved for Significant architectural changes or incompatible API modifications - MINOR (x.0.x): For New feature additions while maintaining backward compatibility - PATCH (x.x.0): For Backward-compatible bug fixes and minor improvements - Note: Each Version Component (MAJOR, MINOR, PATCH) Can Be 2 Digits, e.g., 10.11.22 --> ## Dify Plugin SDK Version - [x] I have Ensured `dify_plugin>=0.3.0,<0.5.0` is in requirements.txt ([SDK docs](https://github.com/langgenius/dify-plugin-sdks/blob/main/python/README.md)) ## Environment Verification (If Any Code Changes) <!-- ⚠️ NOTE: At Least One Environment Must Be Tested. --> ### Local Deployment Environment - [ ] Dify Version is: <!-- Specify Your Version (e.g., 1.2.0) -->, I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration. <!-- - Python Virtual Env Matching Manifest.yaml & requirements.txt - No Breaking Changes in Dify That May Affect the Testing Result --> ### SaaS Environment - [ ] I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration <!-- - Python Virtual Env Matching Manifest.yaml & requirements.txt --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 11:15:56 -05:00
yindo closed this issue 2026-02-16 11:15:56 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label pull-request
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-official-plugins#2035
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?