feat: allow manual endpoint type configuration and add qwen3.5-plus support

[uuuyuqi]

AgentScope-Java Version

1.0.10-SNAPSHOT

Description

Allow manual endpoint type configuration and add qwen3.5-plus support.

Closes #817

Checklist

Please check the following items before code is ready to be reviewed.

• Code has been formatted with mvn spotless:apply
• All tests are passing (mvn test)
• Javadoc comments are complete and follow project conventions
• Related documentation has been updated (e.g. links, examples, etc.)
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @uuuyuqi, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the DashScope integration by providing more control over endpoint selection and adding support for new models. It introduces an EndpointType enum to allow manual configuration of the API endpoint (text or multimodal) and ensures that models like qwen3.5-plus can be correctly routed to the multimodal API when required. The changes also maintain backward compatibility, ensuring existing configurations continue to work as expected.

Highlights

• Endpoint Type Configuration: Introduced the ability to manually configure the endpoint type for DashScope models, allowing developers to explicitly select the text generation or multimodal API.
• Qwen3.5-plus Support: Added specific support for the qwen3.5-plus model, ensuring it can be correctly routed to the multimodal API when needed.
• Backward Compatibility: Maintained backward compatibility by providing a constructor that defaults to automatic API type detection based on the model name.

Changelog

• DashScopeChatModel.java
  • Added a constructor to allow specifying the endpoint type explicitly.
  • Modified the existing constructor to call the new constructor with a null endpoint type for backward compatibility.
  • Updated the doStream method to use the endpoint type when determining whether to use the multimodal API.
  • Updated the builder class to include an endpointType field and a method to set it.
  • Added documentation to explain how to use the endpointType parameter.
• DashScopeHttpClient.java
  • Modified the call and stream methods to use the endpoint type when selecting the API endpoint.
  • Added a selectEndpoint method that takes an EndpointType parameter.
  • Added an isMultimodalModel method to check if a model is a multimodal model.
  • Added a requiresMultimodalApi method that takes an EndpointType parameter.
  • Updated the requiresMultimodalApi method to use the isMultimodalModel method.
• DashScopeRequest.java
  • Added @JsonIgnore annotation to the endpointType field to prevent it from being serialized to JSON.
  • Initialized endpointType to EndpointType.AUTO in the default constructor.
  • Added getter and setter methods for the endpointType property.
  • Added endpointType to the builder class.
• EndpointType.java
  • Added a new EndpointType enum with values AUTO, TEXT, and MULTIMODAL.

Activity

• The pull request introduces the ability to manually configure the endpoint type for DashScope models.
• It adds support for the qwen3.5-plus model.
• The code has been formatted with mvn spotless:apply.
• All tests are passing (mvn test).
• Javadoc comments are complete and follow project conventions.
• Related documentation has been updated.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request successfully introduces the EndpointType enum, allowing for explicit configuration of DashScope API endpoint types. This enhances flexibility by enabling manual override of the automatic model name-based detection, which is particularly useful for models like qwen3.5-plus that might not fit existing auto-detection patterns. The changes are well-integrated across DashScopeRequest, DashScopeChatModel, and DashScopeHttpClient, with clear documentation and appropriate handling of default values. The introduction of the isMultimodalModel helper method also improves code organization and maintainability.

[codecov]

Codecov Report

❌ Patch coverage is 90.74074% with 5 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...a/io/agentscope/core/model/DashScopeChatModel.java	70.00%	3 Missing ⚠️
.../io/agentscope/core/model/DashScopeHttpClient.java	92.59%	0 Missing and 2 partials ⚠️

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

This PR introduces manual endpoint type configuration for DashScope models and adds support for the qwen3.5-plus model to resolve multimodal API routing issues reported in #817. Previously, qwen3.5-plus users encountered "url error" when attempting multimodal calls because the model name didn't match the auto-detection patterns (qvq prefix or -vl pattern). The solution adds both explicit endpoint control via a new EndpointType enum and automatic detection for qwen3.5-plus models.

Changes:

• Added EndpointType enum (AUTO, TEXT, MULTIMODAL) to allow explicit API endpoint selection
• Extended auto-detection logic to recognize qwen3.5-plus as a multimodal model
• Updated DashScopeChatModel, DashScopeHttpClient, and DashScopeRequest to support endpoint type configuration while maintaining backward compatibility

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
EndpointType.java	New enum defining three endpoint types with comprehensive documentation
DashScopeHttpClient.java	Updated endpoint selection logic to support explicit type override; added qwen3.5-plus pattern detection
DashScopeChatModel.java	Added endpointType field with builder support and backward-compatible constructor overloading
DashScopeRequest.java	Added JsonIgnore endpointType field with proper default initialization
DashScopeHttpClientTest.java	Comprehensive test coverage for new endpoint type routing and qwen3.5-plus detection
DashScopeChatModelTest.java	Tests for builder and constructor patterns with endpointType parameter

[LearningGp]

There are other multimodal models, such as qwen3-asr-flash. Should we consider accounting for them as well?

[LearningGp]

LGTM

[chickenlj]

Fixed #825