Skip to main content

Extended Thinking Mode

Control model reasoning depth with the cross-provider --thinking flag. Native Claude launches also accept a session-scoped --effort override when you want Claude’s own effort control without rewriting saved settings.
Available since v7.38.0 - Extended context window support with --1m flag for 1M token context.

Overview

Extended thinking allocates compute tokens for step-by-step reasoning before generating responses. Models “think out loud” internally to solve complex problems through systematic analysis. Use for: Complex architecture, multi-step reasoning, debugging obscure issues, mathematical proofs, strategic planning.

Priority Order

Thinking settings are resolved in this order (highest wins):
  1. --thinking CLI flag
  2. CCS_THINKING environment variable
  3. config.yaml thinking section

Native Claude --effort

When a launch stays on native Claude, CCS also accepts Claude’s effort flag directly:
Behavior:
  • accepted values: low, medium, high, xhigh, max
  • CCS validates the value before spawn and normalizes case
  • the flag stays session-scoped; CCS does not rewrite ~/.claude/settings.json or ~/.ccs/config.yaml
  • CLIProxy-backed thinking flows still treat --effort as the CCS alias for --thinking
Use --thinking when you want portable CCS semantics across providers. Use --effort when you specifically want a native Claude one-session override.

CCS_THINKING Environment Variable

Override thinking per-session without changing config:
Accepted values:
  • Named levels: minimal, low, medium, high, xhigh, max, auto
  • Off values: off, none, disabled, 0 (all equivalent — disable thinking)
  • Integer budget: 0100000

Two Modes

Budget Mode (Token Count)

Specify exact token budget for thinking phase.

Level Mode (Named Levels)

Use predefined levels for simplified control.
Level mappings: minimal=512, low=1024, medium=8192, high=24576, xhigh=32768, max=adaptive ceiling

Provider Support Matrix

  • Type: budget (numeric) vs. levels (named presets)
  • Dynamic: Supports auto mode (model decides dynamically)
Claude Opus 5 uses adaptive, level-only thinking. Select low, medium, high, xhigh, or max; manual numeric thinking budgets are rejected. Opus 5 also supports --1m for a 1M-token context window.

Usage

Custom Budgets

Named Levels

Cross-Type Compatibility

CCS automatically converts between budgets and levels.

Auto-Capping Behavior

CCS validates values and auto-adjusts invalid inputs.

Budget Clamping

Level Capping

Fuzzy Matching

Cost Implications

Higher budgets = more tokens = higher cost.
  • low (1K): Minimal cost, fast
  • medium (8K): Moderate cost, balanced
  • high (24K): Higher cost, deep analysis
  • xhigh (32K): Maximum cost, maximum depth
  • Custom (32K-128K): Very high cost, provider/model dependent
Best practices: Use auto for optimization, reserve high budgets for complex problems, start with low/medium for routine tasks.

Troubleshooting

Model Doesn’t Support Thinking

Error: Model gemini-claude-sonnet-4-5 does not support extended thinking Solution: Use thinking-enabled variants (e.g., gemini-claude-sonnet-4-5-thinking) or switch to a supported reasoning-first profile such as ccs km when you need Kimi API reasoning. Legacy ccs glmt remains compatibility-only.

Budget Exceeds Maximum

Warning: Thinking budget 200000 exceeds maximum. Clamped to 128000. Solution: Use budget within range or switch to model with higher limit.

Level Not Supported

Warning: Level "xhigh" not valid for gpt-5-mini. Mapped to "high". Solution: CCS auto-maps to closest valid level. Check support matrix.

Dynamic Thinking Unavailable

Warning: Model does not support dynamic/auto thinking Solution: Specify explicit level or budget. Check “Dynamic” column in matrix.

ccs config thinking Command

Manage thinking configuration interactively or via flags:

Dashboard Thinking Settings

The CCS Dashboard includes a Thinking settings panel with:
  • Mode selector — auto / off / manual
  • Persistent Override panel — set a global level that overrides tier defaults
  • Tier defaults — configure opus/sonnet/haiku default levels
  • Provider Overrides section — per-provider tier level customization

Extended Context Window

Available since v7.38.0
Enable 1M token context window for supported models using the --1m flag.

Usage

How It Works

The --1m flag appends [1m] suffix to model names, routing to extended context variants:

Provider Support

Auto-Enabled:
  • Native Gemini models (always use 1M context by default)
Opt-In:
  • Claude models via Gemini proxy
  • Antigravity models
  • Codex models
Not Supported:
  • Settings-based profiles (GLM, KM, custom APIs)
  • Local models (Ollama)

Best Practices

When to use --1m:
  • Large codebase analysis
  • Multi-file refactoring
  • Documentation generation across many files
  • Complex architectural planning
When NOT to use:
  • Simple queries (wastes quota)
  • Short prompts (no benefit)
  • Rate-limited scenarios (uses more quota faster)

Cost Implications

Extended context consumes quota faster. Use selectively for tasks requiring large context windows.

Disable Extended Context

Useful when:
  • Quota conservation needed
  • Faster response time preferred
  • Task doesn’t require large context