Skip to content

Rename PUTER_GLM5 -> PUTER_MIMO_V2_5, preserve legacy preference, and adjust model UI hints/strikeouts#117

Open
Android-PowerUser wants to merge 1 commit into
update-build-configuration-filesfrom
tausche-glm-5v-turbo-gegen-mimo-v2.5
Open

Rename PUTER_GLM5 -> PUTER_MIMO_V2_5, preserve legacy preference, and adjust model UI hints/strikeouts#117
Android-PowerUser wants to merge 1 commit into
update-build-configuration-filesfrom
tausche-glm-5v-turbo-gegen-mimo-v2.5

Conversation

@Android-PowerUser

Copy link
Copy Markdown
Owner

Motivation

  • Rename and update a Puter provider model entry to reflect the correct model identifier and display name and surface updated pricing/hint text in the UI.
  • Preserve backward compatibility for stored user preferences that referenced the old enum name.
  • Adjust which models are shown as strikethrough in the menu to reflect availability changes.

Description

  • Replaced the PUTER_GLM5 enum entry with PUTER_MIMO_V2_5 in ModelOption and updated its display name and model identifier to Mimo-V2.5 (Puter) / xiaomi/mimo-v2.5.
  • Added a compatibility mapping in loadModelPreference to remap stored preference string "PUTER_GLM5" to ModelOption.PUTER_MIMO_V2_5 to avoid breaking existing user selections.
  • Updated STRIKETHROUGH_MODELS in MenuScreen.kt to remove MISTRAL_LARGE_3 and add CLOUDFLARE_KIMI_K2_6.
  • Updated model hint text to remove the old PUTER_GLM5 hint and add a pricing hint for PUTER_MIMO_V2_5, and removed the MISTRAL_LARGE_3 hint from the list.

Testing

  • Ran ./gradlew build which completed successfully.
  • Ran unit tests with ./gradlew test and they passed.

Codex Task

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR successfully renames PUTER_GLM5 to PUTER_MIMO_V2_5 while maintaining backward compatibility. The implementation correctly preserves existing user preferences through the compatibility mapping in loadModelPreference. UI updates consistently reflect the new model name and adjusted strikethrough list. No defects found that block merge.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant