Skip to main content
These settings are in the Advanced settings card of a model’s add or edit form on the AI providers page.

Reasoning / Extended Thinking

The add-model form exposes a Thinking / Reasoning toggle (Off / Low / Medium / High / Custom) under Advanced settings. The available options mirror what the model can actually do:
  • A model that can’t reason is locked to Off with a note.
  • A model that only reasons at certain levels (e.g. GPT-5’s medium/high) disables the invalid ones.
  • A reasoning-by-default model gets Medium as a sensible starting point.

Preset levels

When you pick Low / Medium / High, Kodus translates the level to each provider’s native format automatically:
Always-reasoning variants (Kimi k2p7-code/k3, GLM-5.3) reason unconditionally and can’t be turned Off. Test rejects an Off setting on them.

Custom JSON override

Picking Custom in the Thinking / Reasoning toggle reveals a JSON textarea. Paste the provider options directly — Kodus auto-wraps them under the active provider’s namespace. You don’t need to know the Vercel AI SDK routing rules. Use this when:
  • You need a specific budgetTokens value for Claude (instead of the preset effort mapping)
  • You want to enable/disable thinking on a per-model basis for OpenAI-compatible providers
  • You want fields beyond reasoning — caching, service tier, safety settings, user tagging, etc. The override is merged into providerOptions, so any adapter field passes through
  • The provider ships a new field Kodus hasn’t wrapped yet

Examples (paste directly — no namespace needed)

Override Claude’s thinking budget to exactly 20,000 tokens (Claude 4.7 and later reject budgetTokens; use effort there):
Enable prompt caching (non-reasoning example):

Going manual with namespaces (power users)

If your JSON already starts with a known namespace key at the top level — any key from the mapping table below — Kodus leaves it untouched. Useful if you want to mix multiple provider namespaces or be explicit:
Under the hood, these are the namespace mappings Kodus uses:

Gotchas

  • A valid JSON object only. Missing commas, trailing commas or a non-object value are rejected when you save.
  • Precedence: the JSON override fully replaces the effort-preset’s namespace block — if you override anthropic.thinking but forget anthropic.effort, that field won’t be sent. OpenRouter routing (Pin providers / Allow fallbacks) is the one exception: it deep-merges with your override under openrouter.
  • Unknown provider = no wrap. If your BYOK provider isn’t in the namespace table above, Kodus passes the JSON through as-is.

Temperature

Temperature lives under Advanced settings, and the field adapts to the model’s rules — set by the provider, not guessed by the form:
Test validates the temperature you set against these rules and returns an error before saving, so you never persist a value the model won’t honor.

Concurrency and rate limits

The maxConcurrentRequests field (Max concurrent requests, under Advanced settings) caps how many inflight requests Kodus sends to your provider in parallel. Most of the time, the default is fine — but subscription plans with strict concurrency caps need it set explicitly.

Values to set

When to tune it

Raise it

  • You have a high-tier recharge on Moonshot/OpenRouter and want higher throughput on big PRs
  • Reviews feel serialized on multi-file PRs and you’re not seeing 429s

Lower it

  • You see 429 or Too much concurrency errors in review logs
  • Your provider warns about rate limits on the dashboard
  • You want to conserve Coding Plan window (5h/weekly) across more PRs
Concurrency vs. RPM vs. TPM. maxConcurrentRequests only caps parallel inflight requests. Many providers also enforce separate RPM (requests per minute) and TPM (tokens per minute) limits. If you’re hitting RPM/TPM while concurrency looks fine, the fix is usually to upgrade your tier or spread load across time — not to change maxConcurrentRequests.
Fallback interaction. When a task’s model keeps failing with 429s and Kody fails over to the Fallback model, the fallback’s own maxConcurrentRequests applies. Setting a generous fallback on a different provider is a good way to absorb bursts when your main model is on a tight subscription.