Tabbit
ResourcesBlogModels
Tabbit LogoTabbit

Tabbit — The AI Browser that Works for You

Topics

  • Best Browsers 2026: Rankings and Top Lists
  • AI Browser Guides and Resources
  • Browser Comparisons: Head-to-Head Guides
  • Browser Reviews and Explainers
  • Browser Alternatives
  • Browser Directory: Guides by Browser
  • Agentic Browser Resources
  • Browser Downloads and Install Guides
  • Browser Productivity Resources
  • SillyTavern Model Guides and Presets

Popular Guides

  • Best Browsers 2026: Top 10 Ranked & Compared
  • Best Free AI Browsers 2026: Plans & Prices Compared
  • Rabbit Browser: What It Is & Why Tabbit Is Better
  • Firefox vs Chrome 2026: Privacy, RAM & Speed Compared
  • Best Lightweight Browsers 2026: 7 Tested for RAM & Speed
  • AI Browser List 2026: 10 Browsers Compared
  • Neobrowser: Norton Neo, Download & Alternatives
  • Edge vs Chrome 2026: Speed, RAM & Battery Tested
  • Best Internet Browser for Android 2026
  • Best AI Browser 2026: Top 9 Tested & Ranked

Events

  • Tabbit Skill Competition
  • KPOP SBTI Fandom Personality Test
  • Tabbit Campus Creator Program
  • fifi's Picks: AI Skills for Research Papers
  • User Survey

About

  • Tabbit Blog
  • Press & Media
English
简体中文English
Showcases & prompts
MediaQwen4-Max

QwenCloud Token Plan: Qwen4-Max Codex Configuration

Original source

QwenCloud official documentation

AuthorNot specified

Tabbit curation2026-11-17

Read original

One-sentence takeaway

Codex can call the generally available qwen4-max model through QwenCloud Token Plan's Responses-compatible endpoint. Configure a Token Plan-specific API key, then verify connectivity with a read-only smoke test command.

Use cases

  • Suitable tasks: Using QwenCloud Token Plan's Qwen4-Max for coding and inference in Codex CLI

  • Unsuitable tasks: Using an API key for pay-as-you-go billing or another plan; keys are not interchangeable across plans

  • Applicable model version: qwen4-max; do not use qwen4-max-preview

  • Applicable client, agent, or API: Codex CLI, QwenCloud Token Plan Responses API

  • Recommended reasoning level and parameters: reasoning_effort=high and thinking_budget=131072 by default; consider xhigh for complex tasks, subject to the levels available in Codex

Ready-to-use content

Add the following to ~/.codex/config.toml (Windows: %USERPROFILE%\.codex\config.toml):

model_provider = "Token_Plan"
model = "qwen4-max"

[model_providers.Token_Plan]
name = "Token_Plan"
base_url = "https://token-plan.maas.qwencloudapi.com/compatible-mode/v1"
env_key = "OPENAI_API_KEY"
wire_api = "responses"

The initial model value in the official Quick Start is auto. This configuration specifies qwen4-max, which is listed in the official model catalog, to pin usage to this model. You can also configure the model catalog as described in the official instructions, then switch models with codex -m qwen4-max. If model metadata is not configured, Codex may report that metadata was not found; the official documentation says this does not prevent calls to the model specified in config.toml.

Securely set the Token Plan Personal API key as an environment variable. Do not put the real key in a configuration file, repository, or command history:

read -s OPENAI_API_KEY
export OPENAI_API_KEY

Run a read-only smoke test from a directory that contains no sensitive project files:

cd /tmp
codex exec --sandbox read-only -m qwen4-max "只回复 OK;不要调用工具或访问文件。"

QwenCloud's official verification example is codex exec "Hello". The command above adapts it by explicitly specifying the model and adding --sandbox read-only to restrict local command execution. This is a safety adaptation, not a command copied verbatim from QwenCloud's documentation. It sends one model request, so first create or view a Personal API key in the corresponding Token Plan.

Configuration itemValue
PlanToken Plan Personal
Base URLhttps://token-plan.maas.qwencloudapi.com/compatible-mode/v1
API protocolResponses (wire_api = "responses")
API key environment variableOPENAI_API_KEY
Model IDqwen4-max
Context window1,000,000 tokens
Maximum output131,072 tokens in non-thinking mode; 262,144 tokens for thinking and the final answer combined

Test or workflow steps

  1. Create or view an API key on the QwenCloud Token Plan Personal page.

  2. Securely set the key as OPENAI_API_KEY and add the Codex configuration above.

  3. Run the read-only smoke test from /tmp; receiving OK indicates that the basic request succeeded. Do not use a Token Plan key with a pay-as-you-go endpoint.

Original evidence and data

  • The Quick Start on the official Codex page specifies the Token_Plan provider, Token Plan base URL, OPENAI_API_KEY, and wire_api = "responses", and verifies the setup with codex exec "Hello".

  • The model catalog on the same page lists the generally available qwen4-max model, the default reasoning level high, support for low / high / xhigh, and a 1,000,000-token context window. The preview model is listed separately as qwen4-max-preview.

  • The page states that Qwen4-Max uses thinking_budget=131072 by default, with a maximum output of 131,072 tokens in non-thinking mode and up to 262,144 tokens for thinking and the final answer combined.

  • The official FAQ says API keys for Token Plan Personal, Team, and pay-as-you-go are not interchangeable. Codex 0.94.0 and later no longer support wire_api = "chat".

Scope and limitations

  • This configuration applies only to QwenCloud Token Plan Personal. Team requires a key assigned to the team; pay-as-you-go requires that plan's own configuration and key.

  • The generally available model is qwen4-max. The preview model qwen4-max-preview and its dedicated metadata are not covered by this configuration.

  • The configuration and smoke test command are for Codex CLI. If your Codex version reports wire_api as an unknown field, follow the official FAQ and remove that field. If it reports that wire_api = "chat" is unsupported, confirm that the configuration uses responses.

  • The smoke test uses a read-only sandbox but still sends the prompt to the cloud and consumes plan quota. No request was made with a real key for this article.

Reproduction notes

On 2026-11-17, the QwenCloud official Codex documentation was opened and checked using the CLI installed in Tabbit. The configuration fields, endpoint, environment variable, and model metadata come from the page. Local codex exec --help was used to confirm that the --sandbox read-only option is available. No real API key was configured or used, and no online smoke test was run.

Curated by Tabbit

Prompts and showcases are summarized from public sources and Tabbit editorial notes. Check the original licensing and intended use before copying it.

Qwen4-Max

Use in Tabbit

Qwen4-Max

Related showcases & prompts

MediaOfficial Alibaba Cloud Model Studio documentation2026-11-16

Alibaba Cloud Model Studio: Qwen4-Max OpenAI Chat Completions Configuration

MediaQwenCloud official documentation

QwenCloud: Configure Claude Code to Use the GA Version of Qwen4-Max

MediaOfficial QwenCloud and OpenCode documentation

QwenCloud: Configure the Output Limit for GA Qwen4-Max in OpenCode

MediaOfficial QwenCloud documentation

QwenCloud: Explicit Cache Reuse Configuration for Qwen4-Max

Qwen4-Max

Related reviews

MediaQwen official blog2026-11-16

Qwen4-Max: Official Launch Benchmarks and Work360

MediaAtomic Agent Blog2026-11-16

Atomic Agent: Qwen 4 Max Reasoning Levels Tested on a Single-Agent Task

MediaPlotly Blog2026-11-16

Plotly: Qwen4 Max Data Analytics Benchmark and Chart Evaluation

MediaVals AI2026-11-15

Vals AI: Qwen4 Max Industry Task Index, Component Scores, and Cost