Repository navigation
feat(cli): default Smart Topology to Meshy T2.5 - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Smart Topology requests without
--ai-modelcurrently run Meshy T2. This change makesimage-to-3dandtext-to-3dpreview explicitly requestmeshy-t2.5, aligning the CLI with 3D Agent. The canonical API model ID staysmeshy-t2.5.T2.5 uses the API's default 15,000 triangles and accepts up to 30,000. Explicit
--ai-model meshy-t2remains available with its 10,000-triangle CLI default. Conditional defaults are applied after JSON and flags merge, preserving explicit selections and flag precedence. Help, usage documentation and the bundled skill describe the new default.Validation: all 639 tests pass (
env -u NO_COLOR pnpm test);pnpm typecheckandpnpm buildpass. Integration tests cover both commands, raw JSON, explicit T2 selections, flag precedence, model-specific polycount limits and unchanged standard-generation defaults. Both command help outputs were checked.