[PR #1902] [MERGED] feat(openrouter): add verbosity parameter support for GPT-5 models #2139

Closed
opened 2026-02-16 11:16:11 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-official-plugins/pull/1902
Author: @QIN2DIM
Created: 10/20/2025
Status: Merged
Merged: 10/21/2025
Merged by: @crazywoola

Base: mainHead: openrouter-verbosity-params


📝 Commits (3)

  • 46e7803 feat(openrouter): add verbosity parameter support for GPT-5 models
  • 9371590 refactor(llm): remove debug print from model parameters
  • 010d3a1 feat(llm): add support for verbosity parameters in OpenRouter model

📊 Changes

5 files changed (+89 additions, -19 deletions)

View changed files

📝 models/openrouter/manifest.yaml (+1 -1)
📝 models/openrouter/models/llm/gpt-5-mini.yaml (+13 -0)
📝 models/openrouter/models/llm/gpt-5-nano.yaml (+13 -0)
📝 models/openrouter/models/llm/gpt-5.yaml (+13 -0)
📝 models/openrouter/models/llm/llm.py (+49 -18)

📄 Description

Related Issues or Context

Summary

Added a new verbosity parameter to control the detail level and length of model responses across all GPT-5 variants (gpt-5, gpt-5-mini, gpt-5-nano). The parameter accepts values: low, medium, high, with medium as default.

  • Implemented in manifest.yaml and model configuration files
  • Added parameter validation and transformation logic in llm.py
  • Included internationalized labels and help text in both Chinese and English
  • Updated version to 0.0.24 to reflect new feature addition

https://openrouter.ai/docs/api-reference/parameters#verbosity

low medium high
verbosity_low verbosity_medium verbosity_high
image

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/1902 **Author:** [@QIN2DIM](https://github.com/QIN2DIM) **Created:** 10/20/2025 **Status:** ✅ Merged **Merged:** 10/21/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `openrouter-verbosity-params` --- ### 📝 Commits (3) - [`46e7803`](https://github.com/langgenius/dify-official-plugins/commit/46e78030a78d929e4dd573572ff3d55444da1a54) feat(openrouter): add verbosity parameter support for GPT-5 models - [`9371590`](https://github.com/langgenius/dify-official-plugins/commit/93715900b4dde16c6b1a354f6814738429dc0f34) refactor(llm): remove debug print from model parameters - [`010d3a1`](https://github.com/langgenius/dify-official-plugins/commit/010d3a1c1b3ac8edf895c76a4db54999ec791d38) feat(llm): add support for verbosity parameters in OpenRouter model ### 📊 Changes **5 files changed** (+89 additions, -19 deletions) <details> <summary>View changed files</summary> 📝 `models/openrouter/manifest.yaml` (+1 -1) 📝 `models/openrouter/models/llm/gpt-5-mini.yaml` (+13 -0) 📝 `models/openrouter/models/llm/gpt-5-nano.yaml` (+13 -0) 📝 `models/openrouter/models/llm/gpt-5.yaml` (+13 -0) 📝 `models/openrouter/models/llm/llm.py` (+49 -18) </details> ### 📄 Description ## 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 --> ### Summary Added a new `verbosity` parameter to control the detail level and length of model responses across all GPT-5 variants (gpt-5, gpt-5-mini, gpt-5-nano). The parameter accepts values: low, medium, high, with medium as default. - Implemented in manifest.yaml and model configuration files - Added parameter validation and transformation logic in llm.py - Included internationalized labels and help text in both Chinese and English - Updated version to 0.0.24 to reflect new feature addition https://openrouter.ai/docs/api-reference/parameters#verbosity | low | medium | high | | ---- | ------ | ---- | | <img width="609" height="642" alt="verbosity_low" src="https://github.com/user-attachments/assets/87d1c3f2-cf07-4f5c-aabf-4db1101e5f66" />| <img width="606" height="1276" alt="verbosity_medium" src="https://github.com/user-attachments/assets/b9aaedb1-628a-4100-8a2c-ed9aa0f25f89" /> | <img width="610" height="1812" alt="verbosity_high" src="https://github.com/user-attachments/assets/332d16fa-7e07-4d0a-ab65-77771ceb09dc" /> | <img width="366" height="207" alt="image" src="https://github.com/user-attachments/assets/579bb1c5-cb1b-429e-b1fc-f442408511a2" /> ## 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* - [x] 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. --> - [x] 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) - [x] 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 - [x] 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 - [x] 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:16:11 -05:00
yindo closed this issue 2026-02-16 11:16:11 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#2139