Token Plan (Team Edition)
Only consider it for a clearly interactive assigned-user workflow that Alibaba permits; do not assume CI or shared review bots qualify.
Tool + model pairing
Open Code Review with Alibaba Model Studio API
Alibaba open-source AI code review CLI for reviewing git diffs, scanning files, and producing structured line-level comments.
Open Code Review is an Alibaba open-source review CLI. Treat repository review automation as a Model Studio API integration unless the exact use remains an assigned user's permitted interactive coding session.
Choose the right access route
Choose the right access route
For pull-request automation, CI, scheduled reviews, or shared repository services, use a general pay-as-you-go Model Studio API key—not a Coding Plan or Token Plan key.
RecommendedPay-as-you-go Model Studio API for review automation
Coding Plan
Do not use it for automated review scripts, CI, application backends, or batch calls.
Pay-as-you-go Model Studio API
Correct route for CI, pull-request automation, scheduled scans, and shared review services.
Safe configuration pattern
Use a general Model Studio provider for automated reviews
The example is deliberately redacted. Replace placeholders only on your device and never paste a real API key into Nfero.
Before you start
- Define whether the review is a local interactive tool session or automation/CI.
- For automation, create a general Model Studio API key in the same region as its endpoint.
- Store the key in a secret manager or CI secret rather than repository configuration.
- Review repository permissions and test on a non-sensitive change first.
Safe configuration pattern
- Protocol
- OpenAI-compatible Model Studio API
- Create a general Model Studio key for the deployment region.
- Use the region-specific general endpoint, not a Coding Plan or Token Plan endpoint.
- Configure the provider locally or in a protected CI secret.
- Restrict repository permissions and validate review output before publishing comments.
Verify the connection
- Confirm the endpoint does not contain `coding-intl` or `token-plan`.
- Run the review against a disposable branch or sample diff.
- Verify secrets are masked in logs.
- Set billing alerts before enabling scheduled or pull-request-triggered runs.
Model pairings
Recommended starting models
Use this tool to run interactive coding, reasoning, review, and documentation tasks with each model. Confirm final model availability and exact plan support in Alibaba Cloud before production use.
Qwenqwen3.7-plus
Text generationReasoningVisual understanding
Best pairing angle
Strong general reasoning route; confirm pay-as-you-go availability in your selected region.
Qwenqwen3.7-max
Text generationReasoning
Best pairing angle
Long-context option for larger diffs and repository context.
Common problems
Common problems
What you see
401 or invalid API key
Likely cause
The general API key and regional Model Studio endpoint do not match.
What to do
Create or select the key in the same region/workspace as the endpoint.
What you see
Review automation stops after plan-policy enforcement
Likely cause
A plan key was used for a non-interactive workflow.
What to do
Move the integration to a general Model Studio API key and pay-as-you-go endpoint.
Important restrictions
- Do not place Alibaba API keys in a repository, pull-request comment, build log, or Nfero.
- Use least-privilege repository permissions and require human review before automatically changing code.
- Coding Plan and Token Plan credentials are not a substitute for production or automated API access.