Privacy settings

Privacy and GDPR notice

Nfero uses essential storage for language preferences and demo access controls. With your consent, Google Analytics and lightweight usage events help improve model demos and outbound subscription routing. Live demo prompts may be sent to configured Alibaba-hosted model endpoints.

Tool + model pairing

Cline with Alibaba Coding Plan and Token Plan

VS Code extension for code generation, debugging, file edits, terminal actions, and agentic developer workflows.

Cline provides a direct OpenAI Compatible setup inside VS Code. It is a practical route for developers who want Alibaba-hosted models without moving repository work out of their current editor.

Choose the right access route

Choose the right access route

Cline is one of the simplest UI-based integrations. The main risks are mixing plan credentials and forgetting Cline's model-specific message-format option for thinking models.

RecommendedCoding Plan for one VS Code user; Token Plan for Credits-based team access

Token Plan (Team Edition)

Best for assigned developers or teams using Cline regularly and wanting Credits-based access to the current Token Plan model pool.

Coding Plan

Best for an individual using Cline interactively with a fixed monthly model-call allowance.

Pay-as-you-go Model Studio API

Use for extension-driven automation that is not an assigned user's interactive coding session, and for application/backend calls.

Safe configuration pattern

Use Cline's OpenAI Compatible provider

The example is deliberately redacted. Replace placeholders only on your device and never paste a real API key into Nfero.

Before you start

  1. Install VS Code and the current Cline extension.
  2. Obtain the dedicated API key for the Alibaba subscription you selected.
  3. Choose an exact model ID from that plan's current allowlist.
  4. Store the key only in Cline's credential field; do not place it in workspace settings or source control.

Safe configuration pattern

Protocol
OpenAI-compatible
  1. Open Cline, choose Bring my own API key, and select OpenAI Compatible.
  2. Enter the Token Plan endpoint shown below, or the Coding Plan endpoint `https://coding-intl.dashscope.aliyuncs.com/v1`.
  3. Enter the matching dedicated key and an exact supported model ID.
  4. For a thinking model or a related 400 error, open MODEL CONFIGURATION and enable the R1 messages format option described by Alibaba.
text
API Provider: OpenAI Compatible
Base URL: https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1
API key: YOUR_TOKEN_PLAN_API_KEY
Model ID: qwen3.7-plus

Verify the connection

  • Open a small test workspace and ask Cline to explain one file without editing it.
  • Confirm the provider still reads OpenAI Compatible after restarting VS Code.
  • Check the selected model ID character-for-character.
  • Review plan usage after the first task to confirm the intended subscription was used.

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.

Text generationReasoningVisual understanding
Best pairing angle

Strong current default for coding, reasoning, and repository assistance.

Text generationReasoning
Best pairing angle

Long-context alternative for larger workspaces and multi-file tasks.

Text generationReasoningVisual understanding
Best pairing angle

Efficient Token Plan option for quick explanations and smaller edits.

Common problems

Common problems

What you see

401 Incorrect API key provided

Likely cause

The key does not match the base URL, or a pay-as-you-go key was entered for a plan endpoint.

What to do

Choose one access route and replace both values together. For pay-as-you-go, also match the key's region to the endpoint.

What you see

400 InternalError.Algo.InvalidParameter

Likely cause

The selected thinking model requires the alternate message format in Cline.

What to do

Open MODEL CONFIGURATION and enable R1 messages format as described in Alibaba's Cline guide.

What you see

Model not found or not supported

Likely cause

The model ID is misspelled or is not in the selected plan's exact-string allowlist.

What to do

Copy the model ID from the current official plan page instead of inferring a version or alias.

What you see

Long task consumes more calls than expected

Likely cause

Agentic edits can involve repeated file reads, tool calls, and model turns.

What to do

Start with a narrow folder, give a precise task, review the plan usage, and split large changes into smaller sessions.

Important restrictions

  • Use the dedicated API key and base URL from the same Alibaba billing plan. Coding Plan, Token Plan, and general Model Studio credentials are not interchangeable.
  • Plan keys are for the assigned user in an interactive coding or agent tool. Do not share them, commit them to a repository, or expose them in screenshots.
  • Do not use a Coding Plan or Token Plan key for automated scripts, batch jobs, application backends, public services, or other non-interactive API workloads. Use pay-as-you-go Model Studio API access for those workloads.
  • Model availability is an exact-string allowlist and can change. Confirm the model ID in the current Alibaba plan documentation before editing a working configuration.