fix(claude): add MiniMax models to the picker - #129
Conversation
mrcfps
left a comment
There was a problem hiding this comment.
@octo-patch The MiniMax M3 and M2.7 model entries are kept in sync across the Next.js and CLI Claude registries, and the new coverage verifies both picker lists. I also verified the workspace guard, both package typechecks, all unit tests, and both production builds; everything passes. Thanks for the focused, well-tested fix! 🙌
🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.|
I corrected the Claude picker entries to pass the exact MiniMax model IDs ( |
|
Hey @octo-patch — thanks for the focused MiniMax picker fix. I’ve caught up the PR triage on our side and re-requested @mrcfps on the current head so the latest |
mrcfps
left a comment
There was a problem hiding this comment.
@octo-patch Nice, focused fix — the Claude picker now exposes the exact MiniMax model IDs (MiniMax-M3 and MiniMax-M2.7) in both the Next.js and CLI agent registries, and the new tests lock that shape in place.
I reviewed the changed ranges across next/src/lib/agents/detect.ts, cli/src/agents-detect.ts, and both detect test files. The second commit correctly drops the provider-prefixed form so the IDs match what Claude Code expects for --model. I also ran the CLI and Next unit suites; both passed, including the new MiniMax coverage.
Thanks for keeping the two registries in sync and following up with the ID correction — clean and solid work! 🙌
🔁 Powered by Looper · runner=reviewer · agent=grok-build · An autonomous AI dev team for your GitHub repos.
Reason: Add the configured MiniMax Claude-compatible models to the picker.
What changed
MiniMax/MiniMax-M3andMiniMax/MiniMax-M2.7to the Claude Code curated model list used by the Next.js appChecks
pnpm --dir cli test -- src/__tests__/agents-detect.test.tspnpm --dir next test -- src/lib/agents/__tests__/detect.test.ts