Provider Registry

阅读简体中文版：zh_hans/PROVIDERS.md

This registry describes provider behavior that is wired into the current Ghosty codebase. It is intentionally conservative: shipped entries are limited to provider IDs, config keys, auth paths, base URLs, model resolution, and capability metadata that the code already knows about.

DeepSeek remains the default provider, but every entry in ProviderKind::ALL is a first-class selectable provider route. ALL is the catalog/picker surface — one identity per vendor. Dual-wire dialect kinds (*Anthropic, e.g. deepseek-anthropic) and the Model Studio plan variants stay on the enum for serde and provider_for_kind but are deliberately not catalog rows: a plan is mode/base_url and a dialect is wire = openai|anthropic on the primary provider config (crates/config/src/provider_kind.rs:221-226). Hosted routes, generic OpenAI-compatible endpoints, the OpenAI Codex/ChatGPT route, native Anthropic, and local runtimes all run the same terminal harness against the selected provider/model/base URL.

Beginner setup templates (crates/config/src/provider_templates.rs) cover OpenCode Zen, OpenCode Go, SenseNova, and Agnes. Zen/Go reuse the first-class routes below. SenseNova fills a named OpenAI-compatible table on https://token.sensenova.cn/v1 with default model deepseek-v4-flash. Agnes has no published URL in this repository, so it is catalogued as unpublished and does not invent a host. /provider P opens the list; S still fills SenseNova; T probes /models and records reachability only (a 2xx is not model-ready).

Sources to keep in sync:

• crates/config/src/lib.rs - shared provider IDs, defaults, env precedence.
• crates/tui/src/config.rs - TUI provider IDs, provider capability metadata, and provider-specific env handling.
• crates/agent/src/lib.rs - static ModelRegistry used by ghosty model list and ghosty model resolve.
• config.example.toml and docs/CONFIGURATION.md - user-facing config examples and environment variable reference.
• scripts/check-provider-registry.py - drift check for canonical provider IDs, live TUI provider IDs, TOML table names, static registry rows, and documented defaults.

Provider Selection

The canonical provider IDs are the 42 entries of ProviderKind::ALL (crates/config/src/provider_kind.rs), in that order:

deepseek, nvidia-nim, openai, atlascloud, wanjie-ark, volcengine, openrouter, orcarouter, xiaomi-mimo, novita, fireworks, siliconflow, arcee, siliconflow-CN, moonshot, sglang, vllm, ollama, ollama-cloud, huggingface, together, qianfan, openai-codex, anthropic, openmodel, zai, stepfun, minimax, deepinfra, sakana, longcat, opencode-go, opencode-zen, meta, xai, mistral, telecomjs, modelstudio-token-plan, google, antigravity, edenai, and custom.

deepseek-anthropic is not on this list — it is a wire dialect of deepseek, reached with wire = "anthropic", not a separate route to select.

Use any of these surfaces to select a provider:

• CLI: ghosty --provider <id>
• TUI: /provider <id> or the provider picker
• Env: GHOSTY_PROVIDER=<id>; DEEPSEEK_PROVIDER=<id> is the legacy alias
• Config: provider = "<id>"

deepseek-cn, deepseek_china, deepseekcn, and deepseek-china are accepted as legacy aliases for deepseek. They do not select a different official host; DeepSeek uses the same official API host worldwide.

deepseek_anthropic, deepseek-claude, and deepseek_claude select deepseek-anthropic, the opt-in DeepSeek route that speaks the Anthropic Messages API at https://api.deepseek.com/anthropic. It keeps the normal DeepSeek API key path but uses x-api-key plus anthropic-version: 2023-06-01 instead of Bearer auth. If the key already lives in official DeepSeek Harness (dsh) at $DSH_HOME/.credentials.yaml, grant read-only access with ghosty auth external-consent --provider deepseek --mode read-only. Ghosty never writes that file and only reads DEEPSEEK_API_KEY.

huggingface, hugging-face, hugging_face, and hf all select the Hugging Face Inference Providers route. This is the OpenAI-compatible router path for chat/inference, not Hub browsing, model-card inspection, uploads, or artifact export.

telecomjs, telecom-js, telecom_js, telecomjs-cn, and tokenhub all select the TelecomJS TokenHub route. Its authenticated /models catalog is key-scoped and remains isolated from every other provider's live snapshot.

Fresh shared config writes to ~/.ghosty/config.toml. Existing ~/.deepseek/config.toml files are still read for compatibility.

Wire Protocol Compatibility

Provider selection is explicit. A model string prefix such as deepseek-ai/..., deepseek/..., qwen/..., or arcee-ai/... is a provider-owned wire ID or catalog namespace hint under the selected provider. It is not a provider switch and must not be treated as proof that the route is DeepSeek, OpenRouter, or any other provider.

Set the route with provider = "<id>", GHOSTY_PROVIDER=<id>, or ghosty --provider <id>. Set the request model with GHOSTY_MODEL, a provider-specific model env var, top-level default_text_model, or [providers.<table>].model. Set the endpoint with GHOSTY_BASE_URL, a provider-specific base URL env var, or [providers.<table>].base_url. Set auth with ghosty auth set --provider <id>, [providers.<table>].api_key, or the listed provider env vars.

Provider ID	TOML table	Wire protocol	Auth env vars
deepseek	[providers.deepseek]	OpenAI Chat Completions	DEEPSEEK_API_KEY
deepseek-anthropic	[providers.deepseek_anthropic]	Anthropic Messages	DEEPSEEK_API_KEY
nvidia-nim	[providers.nvidia_nim]	OpenAI Chat Completions	NVIDIA_API_KEY, NVIDIA_NIM_API_KEY
openai	[providers.openai]	OpenAI Chat Completions	OPENAI_API_KEY
atlascloud	[providers.atlascloud]	OpenAI Chat Completions	ATLASCLOUD_API_KEY
wanjie-ark	[providers.wanjie_ark]	OpenAI Chat Completions	WANJIE_ARK_API_KEY, WANJIE_API_KEY, WANJIE_MAAS_API_KEY
volcengine	[providers.volcengine]	OpenAI Chat Completions	VOLCENGINE_API_KEY, VOLCENGINE_ARK_API_KEY, ARK_API_KEY
openrouter	[providers.openrouter]	OpenAI Chat Completions	OPENROUTER_API_KEY
xiaomi-mimo	[providers.xiaomi_mimo]	OpenAI Chat Completions	XIAOMI_MIMO_TOKEN_PLAN_API_KEY, MIMO_TOKEN_PLAN_API_KEY, XIAOMI_MIMO_API_KEY, XIAOMI_API_KEY, MIMO_API_KEY
novita	[providers.novita]	OpenAI Chat Completions	NOVITA_API_KEY
fireworks	[providers.fireworks]	OpenAI Chat Completions	FIREWORKS_API_KEY
siliconflow	[providers.siliconflow]	OpenAI Chat Completions	SILICONFLOW_API_KEY
arcee	[providers.arcee]	OpenAI Chat Completions	ARCEE_API_KEY
siliconflow-CN	[providers.siliconflow_cn]	OpenAI Chat Completions	SILICONFLOW_API_KEY
moonshot	[providers.moonshot]	OpenAI Chat Completions	MOONSHOT_API_KEY, KIMI_API_KEY
sglang	[providers.sglang]	OpenAI Chat Completions	SGLANG_API_KEY
vllm	[providers.vllm]	OpenAI Chat Completions	VLLM_API_KEY
ollama	[providers.ollama]	Local OpenAI-compatible Chat Completions	OLLAMA_API_KEY (optional; only for an authenticated local route)
ollama-cloud	[providers.ollama_cloud]	Hosted OpenAI-compatible Chat Completions	OLLAMA_CLOUD_API_KEY, OLLAMA_API_KEY
huggingface	[providers.huggingface]	OpenAI Chat Completions	HUGGINGFACE_API_KEY, HF_TOKEN
together	[providers.together]	OpenAI Chat Completions	TOGETHER_API_KEY
qianfan	[providers.qianfan]	OpenAI Chat Completions	QIANFAN_API_KEY, BAIDU_QIANFAN_API_KEY
openai-codex	[providers.openai_codex]	OpenAI Responses	OPENAI_CODEX_ACCESS_TOKEN, CODEX_ACCESS_TOKEN
anthropic	[providers.anthropic]	Anthropic Messages	ANTHROPIC_API_KEY
openmodel	[providers.openmodel]	Anthropic Messages	OPENMODEL_API_KEY
zai	[providers.zai]	OpenAI Chat Completions	ZAI_API_KEY, Z_AI_API_KEY
easybits	[providers.easybits]	OpenAI Chat Completions (DeepSeek reseller)	EASYBITS_API_KEY
stepfun	[providers.stepfun]	OpenAI Chat Completions	STEPFUN_API_KEY, STEP_API_KEY
minimax	[providers.minimax]	OpenAI Chat Completions	MINIMAX_API_KEY
deepinfra	[providers.deepinfra]	OpenAI Chat Completions	DEEPINFRA_API_KEY, DEEPINFRA_TOKEN
sakana	[providers.sakana]	OpenAI Chat Completions	FUGU_API_KEY, SAKANA_API_KEY
longcat	[providers.longcat]	OpenAI Chat Completions	LONGCAT_API_KEY
opencode-go	[providers.opencode_go]	OpenAI Chat Completions	OPENCODE_GO_API_KEY
opencode-zen	[providers.opencode_zen]	Model-aware: OpenAI Responses, Anthropic Messages, or OpenAI Chat Completions	OPENCODE_ZEN_API_KEY, OPENCODE_API_KEY
meta	[providers.meta]	OpenAI Chat Completions	META_MODEL_API_KEY, MODEL_API_KEY
telecomjs	[providers.telecomjs]	OpenAI Chat Completions	TELECOMJS_API_KEY
xai	[providers.xai]	OpenAI Chat Completions	XAI_API_KEY
mistral	[providers.mistral]	OpenAI Chat Completions	MISTRAL_API_KEY
google	[providers.google]	OpenAI Chat Completions (official Gemini OpenAI-compat route; captures and replays thought signatures on tool calls)	GOOGLE_API_KEY, GEMINI_API_KEY
antigravity	[providers.antigravity]	none — requests fail closed; credential import only	ANTIGRAVITY_API_KEY (key plane); AGY_ADC_AUTH (process env)
edenai	[providers.edenai]	OpenAI Chat Completions	EDENAI_API_KEY
modelstudio-token-plan	[providers.modelstudio_token_plan]	OpenAI Chat Completions	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY
modelstudio-token-plan-anthropic	[providers.modelstudio_token_plan_anthropic]	Anthropic Messages	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY
modelstudio-coding-plan	[providers.modelstudio_coding_plan]	OpenAI Chat Completions	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY
modelstudio-coding-plan-anthropic	[providers.modelstudio_coding_plan_anthropic]	Anthropic Messages	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY

Default base URLs and models for each route are listed in the shipped provider table below. The wire protocol values above are derived from crates/config/src/provider.rs: ChatCompletions is the default, openai-codex overrides to Responses; deepseek-anthropic, anthropic, and openmodel override to AnthropicMessages; and opencode-zen resolves the protocol from the selected model's curated offering.

Auth And Env Rules

For hosted providers, ghosty auth set --provider <id> saves an API key for that provider. API-key environment variables are fallback inputs after saved config and keyring credentials; an explicit process-level --api-key still wins for that launch.

For base URL and model selection, prefer:

• GHOSTY_BASE_URL / GHOSTY_MODEL for the active provider.
• Provider-specific base URL/model env vars when listed below.
• DEEPSEEK_BASE_URL, DEEPSEEK_MODEL, and DEEPSEEK_DEFAULT_TEXT_MODEL as legacy aliases.

Non-local http:// base URLs are rejected unless DEEPSEEK_ALLOW_INSECURE_HTTP=1 is set. Loopback HTTP URLs are allowed for self-hosted runtimes.

Custom DeepSeek-Compatible Endpoints

Most custom DeepSeek-compatible deployments can use an existing provider ID. Do not create [providers.deepseek_custom]; the provider table names are fixed. Instead, choose the closest shipped route and override its endpoint/model:

• DeepSeek-compatible hosted API: keep provider = "deepseek" and set [providers.deepseek].base_url plus [providers.deepseek].model, or launch with DEEPSEEK_BASE_URL and DEEPSEEK_MODEL.
• Generic OpenAI-compatible gateway: use provider = "openai" with [providers.openai].base_url plus [providers.openai].model, or launch with OPENAI_BASE_URL and OPENAI_MODEL.
• Multiple named OpenAI-compatible gateways, or local routes you want to pin from an AgentProfile, can use a custom table such as [providers.lm-studio] kind = "openai-compatible" and select it with provider = "lm-studio" or a profile provider = "lm-studio".
• Local OpenAI-compatible runtimes: use provider = "vllm", "sglang", or "ollama" with the matching provider-specific base URL/model values.

Example user config for a DeepSeek-compatible host:

provider = "deepseek"

[providers.deepseek]
api_key = "YOUR_API_KEY"
base_url = "https://your-provider.example/v1"
model = "deepseek-ai/DeepSeek-V4-Pro"

Example user config for a generic gateway:

provider = "openai"

[providers.openai]
api_key = "YOUR_GATEWAY_API_KEY"
base_url = "https://gateway.example/v1"
model = "your-deepseek-compatible-model"

Alibaba Cloud Model Studio (Bailian / DashScope) is a first-class provider as of v0.9.4 with two plan profiles: Token Plan (Personal / Team) and Coding Plan. Both plans expose an OpenAI-compatible Chat Completions endpoint and an Anthropic-compatible Messages endpoint.

Token Plan (Personal and Team share the same AP-Southeast endpoint):

provider = "modelstudio-token-plan"

[providers.modelstudio_token_plan]
api_key = "YOUR_MODELSTUDIO_API_KEY"
# base_url defaults to https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1
model = "qwen3.8-max"   # or qwen3.8-max-preview | qwen3.7-plus | qwen3.7-max |
                        #    qwen3.6-flash | deepseek-v4-pro | deepseek-v4-flash-0731 |
                        #    glm-5.2

Coding Plan (separate international endpoint):

provider = "modelstudio-coding-plan"

[providers.modelstudio_coding_plan]
api_key = "YOUR_MODELSTUDIO_API_KEY"
# base_url defaults to https://coding-intl.dashscope.aliyuncs.com/v1
model = "qwen3.8-max"

Anthropic-compatible dialect — both plans also expose a native Anthropic Messages path. Select it with the -anthropic provider suffix:

provider = "modelstudio-token-plan-anthropic"

[providers.modelstudio_token_plan_anthropic]
api_key = "YOUR_MODELSTUDIO_API_KEY"
# base_url defaults to https://token-plan.ap-southeast-1.maas.aliyuncs.com/apps/anthropic
model = "qwen3.8-max"

Create or copy a Model Studio API key from the Bailian console. The API key is shared across all four provider IDs above; only the base URL and wire protocol differ.

Thinking / reasoning. Reasoning surfaces in the TUI's Thinking view on both dialects, per Model Studio's deep-thinking docs.

On the OpenAI-compatible routes the top-level controls are route- and model-specific, and Ghosty fails closed: they are sent only when the configured base_url is an official Alibaba Chat Completions host (*.maas.aliyuncs.com/compatible-mode/v1, including workspace-scoped hosts, or coding-intl.dashscope.aliyuncs.com/v1). A custom base_url on the same provider ID gets thinking, enable_thinking, preserve_thinking, and reasoning_effort stripped, so an arbitrary OpenAI-compatible gateway is never handed Alibaba's dialect. On a verified host:

• Hybrid models (qwen3.7-*, qwen3.6-*, deepseek-v4*, glm-*, kimi-k2.6*) get enable_thinking: false for off, true otherwise.
• Thinking-only models — qwen3.8-max (catalogued thinking: always_on), qwen3.8-max-preview (effort/budget options, no toggle), and kimi-k2.7-code — get no enable/disable switch at all. Sending one is at best ignored.
• preserve_thinking is sent for the models documented to accept it (qwen3.7-max/-plus, qwen3.6-max-preview/-plus/-flash, kimi-k2.6*, kimi-k2.7-code), so the next turn keeps the assistant's trace.
• reasoning_effort is sent only for the two families with a documented ladder — deepseek-v4* and glm-5/5.1/5.2 — mapped to high or max.

Reasoning streams back as delta.reasoning_content. It is replayed to the provider on later turns only for the preserve_thinking models above and the thinking-only models; deepseek-v3.1, deepseek-v3.2, and glm-* history stays stripped pending live confirmation that DashScope accepts reasoning_content in input messages. (deepseek-v4* replays regardless — the DeepSeek thinking-mode contract requires it on every provider.)

On the Anthropic-compatible routes, thinking uses the documented {"type":"enabled","budget_tokens":N} / {"type":"disabled"} shapes from the Anthropic-compatible Messages API, with budget_tokens derived from the effort level.

DeepSeek (deepseek-v4-pro, deepseek-v4-flash-0731) and GLM (glm-5.2) models served by Model Studio are provider-scoped and do not collide with the first-party DeepSeek or Zhipu/Z.ai routes. Model Studio publishes no glm-5.3 entry, so Ghosty does not offer one on this route. Pay-as-you-go workspace-id templating is not yet in the built-in provider; use a custom provider entry for that plan until a follow-up adds it.

Private gateways with broken or intercepted certificates should use SSL_CERT_FILE with a trusted CA bundle. The legacy insecure_skip_tls_verify = true key is still parsed so ghosty doctor can report stale configs, but provider clients reject it instead of skipping TLS certificate verification.

Keep provider, api_key, and base_url in user config or process environment. Project-local config overlays intentionally cannot set those keys, so a repository cannot silently redirect prompts or credentials to another endpoint.

Local Models (DS4, Ollama, vLLM, SGLang)

Self-hosted OpenAI-compatible runtimes are first-class routes and are keyless by default — set an API key only when your server requires one. Start your runner, then point Ghosty at it with --provider / /provider or a config table.

Runner	Default base URL	Default model	Base URL override
ollama	http://localhost:11434/v1	deepseek-v4-flash	OLLAMA_BASE_URL
vllm	http://localhost:8000/v1	deepseek-ai/DeepSeek-V4-Pro	VLLM_BASE_URL
sglang	http://localhost:30000/v1	deepseek-ai/DeepSeek-V4-Pro	SGLANG_BASE_URL

DS4 (DwarfStar)

DS4 serves DeepSeek V4 Flash and Pro locally through an OpenAI-compatible API. Start DS4, then open Ghosty's prefilled, keyless setup form:

./ds4-server --ctx 100000 --kv-disk-dir /tmp/ds4-kv --kv-disk-space-mb 8192
ghosty
# In Ghosty: /setup provider ds4

Review the prefilled route and press Enter to save it. The preset budgets a 100,000-token context to match that starter command and defaults to the Flash compatibility alias. Check the local route explicitly with ghosty doctor --probe-local.

DS4 loads the actual GGUF when the server starts. Its deepseek-v4-flash and deepseek-v4-pro API ids are compatibility aliases; changing /model does not swap the resident model. To run Pro, download the supported Pro weights and start ds4-server -m <pro.gguf> ... as described by DS4. Update context_window whenever the server's --ctx value changes.

The equivalent config is:

provider = "ds4"

[providers.ds4]
kind = "openai-compatible"
base_url = "http://127.0.0.1:8000/v1"
model = "deepseek-v4-flash"
auth_mode = "none"
context_window = 100000

Ghosty reuses its existing OpenAI-compatible transport and DeepSeek reasoning/tool-call shaping for DS4. It does not invent an API key, confuse an API alias with the loaded GGUF, or silently switch to a hosted DeepSeek route. The pinned DS4 agent-client contract documents Chat Completions at /v1, DeepSeek thinking replay, streamed usage, max_tokens, and no strict-tool mode; Ghosty follows those exact route facts instead of inheriting unsupported capabilities from a generic gateway. The primary sources for model-facing behavior are DeepSeek's official thinking-mode, tool-call, and Chat Completion contracts. The pinned DeepSeek Harness adapter is only a secondary implementation cross-check; it is not the API contract.

Ollama

ollama serve          # if not already running
ollama pull <model>   # e.g. deepseek-v4-flash, or any tag you prefer
ghosty --provider ollama --model <model>

Provider-hinted model names are sent as-is, so --model qwen3:8b works with any tag Ollama has pulled.

Ollama Cloud

Ollama Cloud is a separate hosted provider. It uses the authenticated OpenAI-compatible /v1/chat/completions route and defaults to gpt-oss:120b:

provider = "ollama-cloud"

[providers.ollama_cloud]
base_url = "https://ollama.com/v1"
model = "gpt-oss:120b"

Create a key in Ollama account settings, then run ghosty auth set --provider ollama-cloud. For ambient auth, OLLAMA_CLOUD_API_KEY wins over Ollama's official OLLAMA_API_KEY. OLLAMA_CLOUD_BASE_URL and OLLAMA_CLOUD_MODEL override the Cloud defaults; arbitrary provider-owned model IDs pass through unchanged. Local ollama remains a separate, keyless-by-default provider.

Compatibility is read-only and in memory: a released config that selected provider = "ollama" with the exact normalized [providers.ollama] base_url = "https://ollama.com/v1" tuple is treated as ollama-cloud at runtime. Only that exact tuple may fall back to the legacy ollama secret slot. Ghosty does not rewrite the config, copy or delete a secret, migrate neighboring paths, or make an explicit ollama-cloud route consume the legacy slot.

vLLM

vllm serve <model> --port 8000
# or: python -m vllm.entrypoints.openai.api_server --model <model> --port 8000
ghosty --provider vllm --model <model>

vLLM's OpenAI-compatible server listens on port 8000 by default, matching Ghosty's VLLM_BASE_URL.

SGLang

python -m sglang.launch_server --model-path <model> --port 30000
ghosty --provider sglang --model <model>

SGLang's default port 30000 matches Ghosty's SGLANG_BASE_URL.

Pinning a local route in config

provider = "ollama"       # or "vllm" / "sglang"

[providers.ollama]
model = "qwen3:8b"        # default is deepseek-v4-flash
# base_url defaults to http://localhost:11434/v1

Local models that print tool-call JSON without the wire markers: see When a Local Model Prints Tool JSON.

Credential Links

Provider setup surfaces use the same typed credential metadata as onboarding, /provider, /links, setup receipts, and doctor output. A missing URL is intentional: local, OAuth-only, and user-defined routes show their supported configuration path instead of guessing a vendor page.

Provider ID	Credential or console link
deepseek, deepseek-anthropic	DeepSeek API keys
nvidia-nim	NVIDIA NIM API keys
openai	OpenAI API keys
atlascloud	Atlas Cloud API keys
wanjie-ark	Wanjie MaaS APIKEY docs
volcengine	Volcengine Ark API keys
openrouter	OpenRouter keys
xiaomi-mimo	Xiaomi MiMo Token Plan
novita	Novita key management
fireworks	Fireworks API keys
siliconflow	SiliconFlow global API keys
siliconflow-CN	SiliconFlow China API keys
arcee	Arcee API key guide
moonshot	Kimi API platform keys or Kimi Code membership console
zai	Z.ai model API
stepfun	StepFun Open Platform
minimax, minimax-anthropic	MiniMax interface keys
huggingface	Hugging Face tokens
deepinfra	DeepInfra API keys
together	Together API keys
qianfan	Baidu Cloud access keys
anthropic	Anthropic API keys
openmodel	OpenModel console (authentication guide)
openai-codex	Run codex login, then explicitly grant Ghosty read-only access to that exact credential file; no Ghosty API key is stored.
sglang, vllm	Local OpenAI-compatible endpoints are keyless by default; configure a key only when the server requires one.
ollama	Local Ollama is keyless by default; configure a key only when the local server requires one.
ollama-cloud	Create an Ollama API key, save it with ghosty auth set --provider ollama-cloud, or set OLLAMA_CLOUD_API_KEY / OLLAMA_API_KEY in that precedence order.
sakana	Sakana AI API keys (get started)
longcat	Meituan LongCat platform
opencode-go	OpenCode Go
opencode-zen	OpenCode Zen
meta	Meta Model API
telecomjs	TelecomJS TokenHub
xai	xAI Console for an API key, Ghosty-owned device login, or explicitly consented read-only Grok CLI credentials.
mistral	Mistral Console (la Plateforme)
google	Google AI Studio — Ghosty uses the official Gemini OpenAI-compatible endpoint and never reads Google OAuth files.
antigravity	Sign in with the official agy CLI (1.1.13). Ghosty can read that login's OAuth token read-only from the exact pinned state.vscdb after ghosty auth external-consent; it never writes or refreshes the file. An ANTIGRAVITY_API_KEY or the process's AGY_ADC_AUTH wins over the file. The cloud-code wire protocol is not implemented: requests fail closed with an actionable message — use google for Gemini models.
edenai	Eden AI API keys
modelstudio-token-plan, modelstudio-token-plan-anthropic, modelstudio-coding-plan, modelstudio-coding-plan-anthropic	Alibaba Cloud Model Studio (Bailian console) — create or copy a Model Studio API key.
custom	Set the named provider's base_url and api_key_env or api_key; no canonical vendor credential page exists.

For Kimi, the official quickstart directs users to sign in, open API Keys, create and copy a key, and keep it secret. Ghosty links straight to that console and accepts the copied key. It never probes or impersonates kimi_cli/kimi_code_cli; first-class Kimi OAuth remains blocked on a vendor-registered Ghosty identity.

External CLI credential consent

Credential files owned by another CLI are disabled by default. Without an explicit grant, provider discovery, setup, routing, auth status, and doctor do not stat, read, refresh, contact an identity provider for, or rewrite Codex, Grok, Kimi, or future external credential files.

Ghosty currently supports exact-path, provider-scoped read-only grants for the Codex CLI and Grok CLI:

codex login
ghosty auth external-consent --provider openai-codex --mode read-only

grok login
ghosty auth external-consent --provider xai --mode read-only

ghosty auth status --provider openai-codex
ghosty auth external-revoke --provider openai-codex

Pass --path /absolute/path/to/auth.json when the external CLI uses a custom location. Consent persists the provider, external owner, exact absolute path, and consent schema version. Later environment-variable changes do not redirect that authority to a different file. Read-only grants never refresh, contact an identity/discovery service, or rewrite the external file; normal requests to the explicitly selected provider may use its token. An expired token fails with login guidance. Doctor reports structural consent/config state without opening credential files and is always non-mutating.

managed is reserved for a future provider-specific preservation adapter. v0.9.1 rejects it before file or network I/O because no reviewed adapter can yet preserve every unknown external schema field safely. Ghosty-started xAI device login instead atomically activates a Ghosty-owned generation named $GHOSTY_HOME/credentials/xai-auth-<generation>.json, stores only that validated basename in config, and revokes any Grok-file grant. Superseded generations are cleaned only after the new config pointer commits. Kimi remains API-key-only; external consent for Kimi is rejected.

The official DeepSeek Harness (dsh) is a third read-only credential owner: ghosty auth external-consent --provider deepseek --mode read-only grants exact-path read access to DEEPSEEK_API_KEY in $DSH_HOME/.credentials.yaml (or ~/.dsh/.credentials.yaml), which Ghosty never writes, refreshes, or loads into the process environment. This is separate from the DSH harness integration (ghosty integrations dsh …, see INTEGRATIONS_DSH.md), which never touches credentials in either direction: it pins Ghosty's route identity into a --patch overlay and lets DSH resolve its own keys.

Shipped Providers

Provider ID	TOML table	Auth env	Base URL env and default	Default or static models	Notes
deepseek	[providers.deepseek]	DEEPSEEK_API_KEY	GHOSTY_BASE_URL / DEEPSEEK_BASE_URL; default https://api.deepseek.com/beta	deepseek-v4-pro, deepseek-v4-flash, experimental deepseek-v4-flash-vision-exp; vision aliases flash-vision, deepseek-v4flashvisionexp; compatibility aliases deepseek-chat, deepseek-reasoner	First-class default. The live Pro backend is labeled DeepSeek-V4-Pro-0813; the callable API ID remains deepseek-v4-pro. Beta URL enables strict tool mode, chat prefix completion, and FIM completion. The documented V4 routes can use provider-native web search through a separate bounded Responses request; compatible custom endpoints do not inherit that capability. Set https://api.deepseek.com or /v1 explicitly to opt out of beta-only features. Reasoning effort maps to the documented wire ladder low/high/max plus the thinking toggle: off sends thinking: {"type":"disabled"}, low sends reasoning_effort: "low", medium rounds up to "high" (the wire has no medium), and high/max pass through. The experimental vision ID was observed in the authenticated /models roster on 2026-08-21 and is advertised as image-input capable on the direct Chat Completions route only. Its limits, reasoning, and tool-call flags provisionally inherit Flash; pricing remains unknown, and no funded image round trip was made during this release work.
deepseek-anthropic	[providers.deepseek_anthropic]	DEEPSEEK_API_KEY	DEEPSEEK_ANTHROPIC_BASE_URL; default https://api.deepseek.com/anthropic	deepseek-v4-pro, deepseek-v4-flash; compatibility aliases deepseek-chat, deepseek-reasoner	Opt-in DeepSeek route for the Anthropic Messages wire protocol. Uses /v1/messages, x-api-key, and anthropic-version: 2023-06-01. Keep provider = "deepseek" for the default Chat Completions path.
nvidia-nim	[providers.nvidia_nim]	NVIDIA_API_KEY, NVIDIA_NIM_API_KEY	NVIDIA_NIM_BASE_URL, NIM_BASE_URL, NVIDIA_BASE_URL; default https://integrate.api.nvidia.com/v1	deepseek-ai/deepseek-v4-pro, deepseek-ai/deepseek-v4-flash	Hosted DeepSeek V4 through NVIDIA NIM. NVIDIA_NIM_MODEL is accepted by the TUI config path.
openai	[providers.openai]	OPENAI_API_KEY	OPENAI_BASE_URL; default https://api.openai.com/v1	gpt-5.6 (default), gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna	Generic OpenAI-compatible route whose built-in endpoint and fallback catalog are native to OpenAI. The GPT-5.6 family uses OpenAI's documented 1.05M context, 128K max output, and reasoning levels. Custom gateways remain free to select an explicit gateway-owned model. OPENAI_MODEL is accepted.
atlascloud	[providers.atlascloud]	ATLASCLOUD_API_KEY	ATLASCLOUD_BASE_URL; default https://api.atlascloud.ai/v1	Default deepseek-ai/deepseek-v4-flash; explicit vendor/model-id values pass through when AtlasCloud is selected	OpenAI-compatible hosted route. ATLASCLOUD_MODEL is accepted by the TUI config path, the static ModelRegistry keeps DeepSeek V4 fallback rows, and provider-hinted CLI model IDs are sent to AtlasCloud exactly as requested. Use Atlas Cloud's own catalog or Coding Plan page for the current provider-owned model list and pricing.
wanjie-ark	[providers.wanjie_ark]	WANJIE_ARK_API_KEY, WANJIE_API_KEY, WANJIE_MAAS_API_KEY	WANJIE_ARK_BASE_URL, WANJIE_BASE_URL, WANJIE_MAAS_BASE_URL; default https://maas-openapi.wanjiedata.com/api/v1	deepseek-reasoner	OpenAI-compatible hosted route. WANJIE_ARK_MODEL, WANJIE_MODEL, and WANJIE_MAAS_MODEL are accepted.
volcengine	[providers.volcengine]	VOLCENGINE_API_KEY, VOLCENGINE_ARK_API_KEY, ARK_API_KEY	VOLCENGINE_BASE_URL, VOLCENGINE_ARK_BASE_URL, ARK_BASE_URL; default https://ark.cn-beijing.volces.com/api/coding/v3	DeepSeek-V4-Pro, DeepSeek-V4-Flash	Volcengine/Volcano Engine Ark OpenAI-compatible coding endpoint. VOLCENGINE_MODEL and VOLCENGINE_ARK_MODEL are accepted.
openrouter	[providers.openrouter]	OPENROUTER_API_KEY	OPENROUTER_BASE_URL; default https://openrouter.ai/api/v1	deepseek/deepseek-v4-pro, deepseek/deepseek-v4-flash; recent large IDs include arcee-ai/trinity-large-thinking, minimax/minimax-m3, xiaomi/mimo-v2.5-pro, qwen/qwen3.6-flash, qwen/qwen3.6-35b-a3b, qwen/qwen3.6-max-preview, qwen/qwen3.6-27b, qwen/qwen3.6-plus, google/gemma-4-31b-it, z-ai/glm-5.1, z-ai/glm-5.2, moonshotai/kimi-k2.7-code, moonshotai/kimi-k2.6	Additive open-model routing layer. It does not replace DeepSeek; it lets users route supported model IDs through OpenRouter when they choose it.
orcarouter	[providers.orcarouter]	ORCAROUTER_API_KEY	ORCAROUTER_BASE_URL; default https://api.orcarouter.ai/v1	deepseek/deepseek-v4-pro, deepseek/deepseek-v4-flash; router alias orcarouter/auto; recent large IDs mirror the OpenRouter namespaced catalog	OrcaRouter OpenAI-compatible aggregation gateway. Shares the namespaced vendor/model wire-model format and DeepSeek model set with OpenRouter, so the OpenRouter base-URL and model-normalization rules apply. ORCAROUTER_MODEL is accepted. Provider aliases: orcarouter, orca_router, orca.
xiaomi-mimo	[providers.xiaomi_mimo]	XIAOMI_MIMO_TOKEN_PLAN_API_KEY, MIMO_TOKEN_PLAN_API_KEY, XIAOMI_MIMO_API_KEY, XIAOMI_API_KEY, MIMO_API_KEY	XIAOMI_MIMO_BASE_URL, MIMO_BASE_URL, XIAOMI_MIMO_MODE, MIMO_MODE; default https://token-plan-sgp.xiaomimimo.com/v1	Chat: mimo-v2.5-pro, mimo-v2.5-pro-ultraspeed, mimo-v2.5; speech/TTS: mimo-v2.5-tts, mimo-v2.5-tts-voicedesign, mimo-v2.5-tts-voiceclone, mimo-v2-tts	Xiaomi MiMo OpenAI-compatible chat completions route. mimo-v2.5-pro and mimo-v2.5 can use the documented provider-native web-search plugin; ultraspeed, speech/TTS, and custom-compatible routes do not inherit it. Token Plan keys (tp-...) use api-key auth and the token-plan endpoint by default; pay-as-you-go mode uses standard API keys (sk-...) and https://api.xiaomimimo.com/v1. It sends max_completion_tokens and uses MiMo's thinking field for reasoning control. Token Plan cost/usage is credit/quota based; Ghosty shows it as unknown until Xiaomi exposes a reliable balance API. ghosty speech / tts uses the TTS models.
novita	[providers.novita]	NOVITA_API_KEY	NOVITA_BASE_URL; default https://api.novita.ai/openai/v1	deepseek/deepseek-v4-pro, deepseek/deepseek-v4-flash	OpenAI-compatible hosted route for DeepSeek model IDs. Use config or GHOSTY_MODEL / DEEPSEEK_MODEL for model overrides.
fireworks	[providers.fireworks]	FIREWORKS_API_KEY	FIREWORKS_BASE_URL; default https://api.fireworks.ai/inference/v1	accounts/fireworks/models/deepseek-v4-pro	OpenAI-compatible hosted route. Use config or GHOSTY_MODEL / DEEPSEEK_MODEL for model overrides.
siliconflow	[providers.siliconflow]	SILICONFLOW_API_KEY	SILICONFLOW_BASE_URL; default https://api.siliconflow.com/v1	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	OpenAI-compatible hosted route. Official docs use the .com endpoint. SILICONFLOW_MODEL is accepted. Reasoning aliases deepseek-reasoner and deepseek-r1 map to Pro; deepseek-chat and deepseek-v3 map to Flash.
siliconflow-CN	[providers.siliconflow_cn]	SILICONFLOW_API_KEY	SILICONFLOW_BASE_URL; default https://api.siliconflow.cn/v1	Uses the SiliconFlow model set	China regional SiliconFlow route. Falls back to [providers.siliconflow] for api_key / base_url / model when unset. Select it with provider = "siliconflow-CN" or GHOSTY_PROVIDER=siliconflow-CN.
arcee	[providers.arcee]	ARCEE_API_KEY	ARCEE_BASE_URL; default https://api.arcee.ai/api/v1	trinity-large-thinking, trinity-large-preview	Arcee AI direct OpenAI-compatible route, tracked as 256K-context BF16 serving. ARCEE_MODEL is accepted. OpenRouter's arcee-ai/trinity-large-thinking remains the OpenRouter namespaced model ID; direct Arcee uses the bare trinity-large-thinking ID.
moonshot	[providers.moonshot]	MOONSHOT_API_KEY, KIMI_API_KEY	MOONSHOT_BASE_URL, KIMI_BASE_URL; default https://api.moonshot.ai/v1	Direct Moonshot: kimi-k3, kimi-k2.7-code, kimi-k2.7-code-highspeed, kimi-k2.6; Kimi Code membership: k3, kimi-for-coding, kimi-for-coding-highspeed at https://api.kimi.com/coding/v1	Moonshot/Kimi route. kimi and kimi-k2 aliases select kimi-k2.7-code; MOONSHOT_MODEL, KIMI_MODEL_NAME, and KIMI_MODEL are accepted. Kimi thinking streams through reasoning_content; Ghosty keeps it in Thinking cells and replays it for thinking/tool-call continuity. For direct K3, use exact base_url = "https://api.moonshot.ai/v1" and model = "kimi-k3"; it is always-thinking and receives top-level `reasoning_effort = "low"
antigravity	[providers.antigravity]	ANTIGRAVITY_API_KEY	ANTIGRAVITY_BASE_URL; default https://cloudcode-pa.googleapis.com/v1internal	none advertised — requests fail closed until the cloud-code wire protocol exists	Antigravity (agy 1.1.13) credential plane: consent-gated read-only import of the official CLI's state.vscdb OAuth token (antigravityUnifiedStateSync.oauthToken), pinned to the exact per-OS app-profile path. The store is opened read-only through the secure no-follow boundary with an inode recheck; Ghosty never writes, refreshes, or re-authenticates. Precedence: ANTIGRAVITY_API_KEY > process AGY_ADC_AUTH > consented file. Not an embed of any other harness. No live calls made in this environment.
google	[providers.google]	GOOGLE_API_KEY, GEMINI_API_KEY	GOOGLE_BASE_URL, GEMINI_BASE_URL; default https://generativelanguage.googleapis.com/v1beta/openai/	gemini-3.1-pro-preview (default); /model also lists gemini-3-pro-preview, gemini-3.7-flash, gemini-3.6-flash, gemini-3.5-flash, gemini-3.5-flash-lite, gemini-2.5-pro, gemini-2.5-flash	Google Gemini as its own backend on the official OpenAI-compatible Chat Completions route. Thinking models capture extra_content.google.thought_signature on tool calls and replay it with the assistant tool-call messages; replaying a tool call whose signature was not captured fails closed with an actionable error instead of letting the tool loop break. gemini-2.5-flash-lite ships thinking off and degrades with a warning instead. Reasoning effort maps onto the documented google.thinking_config.thinking_level (low/high). The dialect binds to the exact official base URL: a google row pointed at another gateway gets plain OpenAI semantics and no signature requirements. Ghosty never reads Google OAuth files; only an AI Studio API key is used. Not live-tested against the real endpoint in this environment.
zai	[providers.zai]	ZAI_API_KEY, Z_AI_API_KEY	ZAI_BASE_URL, Z_AI_BASE_URL; default https://api.z.ai/api/coding/paas/v4; general APIs https://api.z.ai/api/paas/v4 and https://open.bigmodel.cn/api/paas/v4	GLM-5.3 default; /model also lists GLM-5.3-Flash, GLM-5.2, GLM-5.1, and GLM-5-Turbo	Z.AI GLM Coding Plan route. The two general API products expose structured provider-native web search (search-prime globally, search_std in China); Coding Plan and compatible custom endpoints do not inherit it. GLM-5.3 is the default and a first-class picker row (model = "GLM-5.3" or ZAI_MODEL=GLM-5.3); GLM-5.3-Flash is the 1M multimodal fast sibling (model = "GLM-5.3-Flash"). An explicit GLM-5.2 selection keeps its own id. Limits and reasoning options for 5.3 are inherited from GLM-5.2 until Z.ai publishes distinct 5.3 metadata; 5.3 carries no price. Flash ships the published $0.15/$0.50 list. A live call can still 429 with entitlement code 1311 on accounts that are not provisioned for 5.3.
stepfun	[providers.stepfun]	STEPFUN_API_KEY, STEP_API_KEY	STEPFUN_BASE_URL, STEP_BASE_URL; default https://api.stepfun.ai/v1; Coding Plan endpoint https://api.stepfun.ai/step_plan/v1	step-3.7-flash	StepFun / StepFlash direct OpenAI-compatible route. /provider setup asks which billing route the key belongs to — pay-as-you-go or Step Plan — validates the key against the chosen endpoint, and writes the answer to [providers.stepfun].base_url only. A base URL that is neither recognized route is left alone and the question is skipped. You can also set [providers.stepfun].base_url or STEP_BASE_URL to the Coding Plan URL by hand. Offline accounting labels recognized routes as stepfun-payg or stepfun-plan without persisting the raw endpoint, and only the standard PAYG route receives token pricing. STEPFUN_MODEL and STEP_MODEL are accepted.
minimax	[providers.minimax]	MINIMAX_API_KEY	MINIMAX_BASE_URL; default https://api.minimax.io/v1; China https://api.minimaxi.com/v1	MiniMax-M3, MiniMax-M2.7, MiniMax-M2.7-highspeed, MiniMax-M2.5, MiniMax-M2.5-highspeed, MiniMax-M2.1, MiniMax-M2.1-highspeed, MiniMax-M2	MiniMax direct OpenAI-compatible route. Ghosty sends reasoning_split = true so MiniMax thinking arrives separately from answer text. Both MiniMax dialects sell pay-as-you-go and Token Plan over the same endpoints and the same key, so billing is classified from the credential product, never from the endpoint or from a default. mode = "token-plan" in [providers.minimax]/[providers.minimax_anthropic], or a Token Plan key shaped sk-cp…, bills as MiniMax Token Plan quota with no dollar estimates; an explicit pay-as-you-go mode (pay-as-you-go/payg/metered) wins over key shape. The key's product prefix is only visible when the key is in config, bound by api_key_env, or exported as MINIMAX_API_KEY on an official endpoint — a key saved through ghosty auth set (secret store / OS keyring) is deliberately not read to classify billing. With no explicit mode and no visible product marker the route reports cost: unknown rather than assuming pay-as-you-go, so a Token Plan account is never charged invented dollars. Custom/gateway endpoints also fail closed with cost: unknown. Official M3 input modalities are text, image, and video; M2.7 is text-only.
minimax-anthropic	[providers.minimax_anthropic]	MINIMAX_API_KEY	MINIMAX_ANTHROPIC_BASE_URL; default https://api.minimax.io/anthropic; China https://api.minimaxi.com/anthropic	MiniMax-M3, MiniMax-M2.7	MiniMax direct Anthropic-compatible Messages route. Keep the /anthropic suffix because Ghosty appends /v1/messages; the route uses x-api-key. M3 supports adaptive or disabled thinking. M2.7 always keeps thinking enabled.
sglang	[providers.sglang]	Optional SGLANG_API_KEY	SGLANG_BASE_URL; default http://localhost:30000/v1	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	Self-hosted OpenAI-compatible route. Localhost deployments commonly omit auth. SGLANG_MODEL is accepted.
vllm	[providers.vllm]	Optional VLLM_API_KEY	VLLM_BASE_URL; default http://localhost:8000/v1	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	Self-hosted vLLM OpenAI-compatible route. Localhost deployments commonly omit auth. VLLM_MODEL is accepted.
ollama	[providers.ollama]	Local optional OLLAMA_API_KEY	OLLAMA_BASE_URL; default http://localhost:11434/v1	deepseek-v4-flash; provider-hinted custom tags pass through	Local Ollama is keyless by default. OLLAMA_MODEL is accepted.
ollama-cloud	[providers.ollama_cloud]	OLLAMA_CLOUD_API_KEY, then OLLAMA_API_KEY	OLLAMA_CLOUD_BASE_URL; default https://ollama.com/v1	gpt-oss:120b; arbitrary provider-owned IDs pass through	Hosted OpenAI-compatible /v1/chat/completions route. Save credentials under ollama-cloud; the exact released ollama + Cloud URL tuple has bounded read-only in-memory compatibility with its legacy table and secret slot. OLLAMA_CLOUD_MODEL is accepted.
huggingface	[providers.huggingface]	HUGGINGFACE_API_KEY, HF_TOKEN	HUGGINGFACE_BASE_URL, HF_BASE_URL; default https://router.huggingface.co/v1	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	Hugging Face Inference Providers OpenAI-compatible router route. Accepted aliases: huggingface, hugging-face, hugging_face, hf. Org-prefixed model IDs pass through. HUGGINGFACE_MODEL and HF_MODEL are accepted. Hub browsing/export are separate future features.
deepinfra	[providers.deepinfra]	DEEPINFRA_API_KEY, DEEPINFRA_TOKEN	DEEPINFRA_BASE_URL; default https://api.deepinfra.com/v1/openai	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	DeepInfra OpenAI-compatible route. Drop-in replacement for OpenAI SDK.
together	[providers.together]	TOGETHER_API_KEY	TOGETHER_BASE_URL; default https://api.together.xyz/v1	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash, thinkingmachines/inkling	Together AI OpenAI-compatible route. TOGETHER_MODEL is accepted. Model aliases deepseek-v4-pro and deepseek-v4-flash normalize to Together's org-prefixed IDs; inkling and together-inkling normalize to Together's published lowercase Inkling wire ID. Inkling uses the exact none/minimal/low/medium/high/max reasoning vocabulary from Thinking Machines' official model repository. Together's launch post currently says Inkling is live with 1M context, while its model detail page says coming soon with 256K context and publishes no price. Until Together's active /models endpoint and the Models.dev catalog resolve that conflict, Inkling is not seeded into Ghosty's offline picker and no route-specific context or cost is inferred.
qianfan	[providers.qianfan]	QIANFAN_API_KEY, BAIDU_QIANFAN_API_KEY	QIANFAN_BASE_URL, BAIDU_QIANFAN_BASE_URL; default https://api.baiduqianfan.ai/v1	ernie-4.0-turbo-8k; provider-scoped custom Qianfan service/model IDs pass through	Baidu Qianfan OpenAI-compatible route. Requests use Bearer auth and Chat Completions payloads. QIANFAN_MODEL and BAIDU_QIANFAN_MODEL are accepted; aliases baidu-qianfan, baidu_qianfan, and baidu resolve to this provider. Tool/function calling is model-scoped in Qianfan docs, so Ghosty preserves the selected wire model and leaves live capability proof to follow-up route/capability work.
openai-codex	[providers.openai_codex]	Process token via OPENAI_CODEX_ACCESS_TOKEN/CODEX_ACCESS_TOKEN, or exact-path read-only consent after codex login	OPENAI_CODEX_BASE_URL/CODEX_BASE_URL; default https://chatgpt.com/backend-api	gpt-5.5	Experimental. Talks to the OpenAI Responses API at /codex/responses. Codex CLI files are disabled by default; ghosty auth external-consent --provider openai-codex --mode read-only grants access to one exact file. Ghosty never refreshes or rewrites that external file, and expired tokens fail closed. OPENAI_CODEX_MODEL/CODEX_MODEL and OPENAI_CODEX_ACCOUNT_ID/CODEX_ACCOUNT_ID are accepted. Ghosty budgets this route with the 400K Codex-family effective context window even when the public API model table lists a larger native gpt-5.5 window.
anthropic	[providers.anthropic]	ANTHROPIC_API_KEY	ANTHROPIC_BASE_URL; default https://api.anthropic.com	claude-opus-4-8, claude-sonnet-4-6 (default), claude-haiku-4-5	Native Anthropic Messages API route (/v1/messages, x-api-key + anthropic-version: 2023-06-01) — not OpenAI-compatible. Prompt caching via cache_control breakpoints, adaptive thinking + output_config.effort, signed thinking blocks replayed verbatim, cache telemetry normalized per #2961. ANTHROPIC_MODEL is accepted.
openmodel	[providers.openmodel]	OPENMODEL_API_KEY	OPENMODEL_BASE_URL; default https://api.openmodel.ai	deepseek-v4-flash; provider-scoped custom model IDs pass through	OpenModel Anthropic-compatible Messages route. Uses /v1/messages, Bearer auth, and anthropic-version: 2023-06-01; OpenModel selects DeepSeek, DashScope, Xiaomi, Claude, and other routes by model id. OPENMODEL_MODEL is accepted.
sakana	[providers.sakana]	FUGU_API_KEY, SAKANA_API_KEY	SAKANA_BASE_URL; default https://api.sakana.ai/v1	fugu (default), fugu-ultra-20260615	Sakana AI Fugu OpenAI-compatible route. Standard Chat Completions wire protocol; streaming supported. fugu-ultra-20260615 is the heavy/reasoning variant. Env var aliases: FUGU_API_KEY (primary), SAKANA_API_KEY; provider aliases: sakana-ai, sakana_ai, fugu.
longcat	[providers.longcat]	LONGCAT_API_KEY	LONGCAT_BASE_URL; default https://api.longcat.chat/openai/v1	LongCat-2.0 (default)	Meituan LongCat curated model gateway. OpenAI-compatible Chat Completions wire protocol. Sign up at https://longcat.chat/platform for an API key. Provider aliases: long-cat, meituan-longcat, meituan.
opencode-go	[providers.opencode_go]	OPENCODE_GO_API_KEY	OPENCODE_GO_BASE_URL; default https://opencode.ai/zen/go/v1	deepseek-v4-pro (default), grok-4.5, glm-5.2, glm-5.1, kimi-k3, kimi-k2.7-code, kimi-k2.6, deepseek-v4-flash, mimo-v2.5, mimo-v2.5-pro	OpenCode Go subscription route using OpenAI-compatible Chat Completions. OPENCODE_GO_MODEL is accepted. Ghosty uses bare wire IDs; familiar opencode-go/<model-id> input aliases normalize to the bare ID. Go models documented only on the Anthropic /messages endpoint are deliberately not advertised by this route until Ghosty supports per-model wire selection. Billing surfaces show the Go allowance instead of token-price estimates.
opencode-zen	[providers.opencode_zen]	OPENCODE_ZEN_API_KEY, fallback OPENCODE_API_KEY	OPENCODE_ZEN_BASE_URL; default https://opencode.ai/zen/v1	gpt-5.5 (default); current documented GPT, Claude, Qwen, DeepSeek, MiniMax, GLM, Kimi, Grok, and free-model IDs	OpenCode Zen model-aware gateway. OPENCODE_ZEN_MODEL is accepted, and official opencode/<model-id> selectors normalize to bare wire IDs. GPT rows use /responses; Claude and Qwen rows use /messages; DeepSeek, MiniMax, GLM, Kimi, Grok, and the listed free rows use /chat/completions. Responses and Chat Completions authenticate with Bearer Authorization, while Anthropic Messages uses x-api-key; none of these routes use ChatGPT/Codex OAuth guidance or headers. Gemini currently fails closed because its model-specific Google wire protocol is not implemented. Unknown models also fail closed until their protocol is present in the curated catalog.
meta	[providers.meta]	META_MODEL_API_KEY, MODEL_API_KEY	META_MODEL_API_BASE_URL, MODEL_API_BASE_URL; default https://api.meta.ai/v1	muse-spark-1.2 (default)	Meta Model API public-preview route using OpenAI-compatible Chat Completions. Muse Spark 1.2 keeps its wire ID, tool support, 1M context, 32K output metadata, and none through xhigh reasoning effort. META_MODEL_API_MODEL and MODEL_API_MODEL are accepted. Provider aliases: meta-ai, meta_model_api, muse, muse-spark.
telecomjs	[providers.telecomjs]	TELECOMJS_API_KEY	TELECOMJS_BASE_URL; default https://aigw.telecomjs.com/v1	deepseek-v4-pro conservative fallback; authenticated /models rows when a key is configured	TelecomJS TokenHub OpenAI-compatible Chat Completions route. Live catalogs are isolated by provider and key fingerprint, stale rows survive transient refresh failures, and unsupported reasoning request fields are omitted. TELECOMJS_MODEL is accepted. Provider aliases: telecom-js, telecom_js, telecomjs-cn, tokenhub.
mistral	[providers.mistral]	MISTRAL_API_KEY	MISTRAL_BASE_URL; default https://api.mistral.ai/v1	mistral-code-latest (default; codestral-latest accepted as alias), mistral-medium-latest (aliases: mistral-medium-3-5), mistral-small-latest (aliases: mistral-small-2603), mistral-large-latest	Mistral AI (la Plateforme) OpenAI-compatible Chat route. On the documented first-party HTTPS /v1 hosts, Medium and Small send adjustable reasoning_effort (none or high only), parse Mistral's polymorphic thinking/text blocks, and replay stored thinking in that same wire shape. Deprecated native Magistral IDs remain explicit-configuration compatibility routes: they are always-reasoning and never receive the adjustable effort field. Code and Large are non-reasoning. A custom MISTRAL_BASE_URL keeps generic Chat semantics unless it is one of the documented first-party hosts. MISTRAL_MODEL is accepted. Provider aliases: mistral-ai, mistralai, la-plateforme.
edenai	[providers.edenai]	EDENAI_API_KEY	EDENAI_BASE_URL; default https://api.edenai.run/v3; EU https://api.eu.edenai.run/v3	deepseek/deepseek-v4-pro (default); live /models catalog of provider/model ids	Eden AI OpenAI-compatible aggregation gateway. Catalog rows remain provider-scoped; generic reasoning controls are omitted because supported fields depend on the selected upstream family. EDENAI_MODEL is accepted. The default deepseek/deepseek-v4-pro is listed on the global catalog only; on the EU endpoint set EDENAI_MODEL (or model) to a row from the EU /models list, for example qwen/deepseek-v4-pro. Provider aliases: eden-ai, eden_ai.
xai	[providers.xai]	XAI_API_KEY, Ghosty-owned device OAuth, or explicit read-only Grok CLI consent	XAI_BASE_URL; default https://api.x.ai/v1	grok-4.6 (default), grok-4.5, grok-4.3, grok-build, grok-composer-2.5-fast, grok-4.20-0309-reasoning, grok-4.20-0309-non-reasoning	xAI/Grok OpenAI-compatible Chat Completions route. Grok 4.6 has a 500K context window, text/image input, function calls, structured output, server-side web search, and low/medium/high/xhigh reasoning (default high). Its standard rates double when the prompt reaches 200K tokens; the same 2x long-context rule applies to grok-4.5 (500K context, $2.00 / $0.30 cached / $6.00) and grok-4.3 (1M context, $1.25 / $0.20 cached / $2.50) per their model pages. There is no documented latest/fast alias and no published numeric output limit. API-key (default): Bearer token from console.x.ai via XAI_API_KEY / keyring / api_key. OAuth: ghosty auth xai-device uses SSH-friendly device login and Ghosty-owned storage, which may refresh itself. Existing Grok CLI credentials require ghosty auth external-consent --provider xai --mode read-only; the granted external file is never refreshed or rewritten. OAuth may return HTTP 403 on some SuperGrok tiers — keep API-key as the reliable fallback. XAI_MODEL is accepted. Provider aliases: x-ai, x_ai, grok.
modelstudio-token-plan	[providers.modelstudio_token_plan]	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY	MODELSTUDIO_TOKEN_PLAN_BASE_URL; default https://token-plan.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1	qwen3.8-max (default), qwen3.8-max-preview, qwen3.7-plus, qwen3.7-max, qwen3.6-flash, deepseek-v4-pro, deepseek-v4-flash-0731, glm-5.2	Alibaba Cloud Model Studio Token Plan OpenAI-compatible Chat Completions route. Token Plan Personal and Team share this endpoint. qwen3.8-max, qwen3.7-plus, and qwen3.7-max can use provider-native web search through the Token Plan Responses Harness; the preview, Coding Plan, and Anthropic routes do not inherit that capability. All listed models are reasoning-capable text/coding models. DeepSeek and GLM entries are provider-scoped and do not collide with first-party routes. MODELSTUDIO_TOKEN_PLAN_MODEL is accepted. Provider aliases: modelstudio-token-plan, alibaba-token-plan, dashscope-token-plan.
modelstudio-token-plan-anthropic	[providers.modelstudio_token_plan_anthropic]	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY	default https://token-plan.ap-southeast-1.maas.aliyuncs.com/apps/anthropic	Same model catalog as modelstudio-token-plan	Token Plan Anthropic-compatible Messages route (/apps/anthropic). Same API key as the OpenAI dialect. Provider aliases: modelstudio-token-plan-anthropic, alibaba-token-plan-anthropic.
modelstudio-coding-plan	[providers.modelstudio_coding_plan]	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY	MODELSTUDIO_CODING_PLAN_BASE_URL; default https://coding-intl.dashscope.aliyuncs.com/v1	qwen3.8-max (default); same catalog as Token Plan	Alibaba Cloud Model Studio Coding Plan OpenAI-compatible Chat Completions route. MODELSTUDIO_CODING_PLAN_MODEL is accepted. Provider aliases: modelstudio-coding-plan, alibaba-coding-plan, dashscope-coding-plan.
modelstudio-coding-plan-anthropic	[providers.modelstudio_coding_plan_anthropic]	MODELSTUDIO_API_KEY, DASHSCOPE_API_KEY	default https://coding-intl.dashscope.aliyuncs.com/apps/anthropic	Same model catalog as modelstudio-coding-plan	Coding Plan Anthropic-compatible Messages route (/apps/anthropic). Provider aliases: modelstudio-coding-plan-anthropic, alibaba-coding-plan-anthropic.

OpenCode Zen protocol catalog

Zen Responses and Chat Completions requests authenticate with Bearer Authorization; Zen Anthropic Messages requests use x-api-key. None of these routes add ChatGPT/Codex OAuth headers.

The bundled Zen transport snapshot follows the official endpoint table and is intentionally explicit:

• Responses: gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna, gpt-5.5, gpt-5.5-pro, gpt-5.4, gpt-5.4-pro, gpt-5.4-mini, gpt-5.4-nano, gpt-5.3-codex, gpt-5.3-codex-spark, gpt-5.2, gpt-5.2-codex, gpt-5.1, gpt-5.1-codex, gpt-5.1-codex-max, gpt-5.1-codex-mini, gpt-5, gpt-5-codex, gpt-5-nano.
• Anthropic Messages: claude-fable-5, claude-opus-4-8, claude-opus-4-7, claude-opus-4-6, claude-opus-4-5, claude-sonnet-5, claude-sonnet-4-6, claude-sonnet-4-5, claude-haiku-4-5, qwen3.7-max, qwen3.7-plus, qwen3.6-plus, qwen3.5-plus.
• Chat Completions: deepseek-v4-pro, deepseek-v4-flash, minimax-m3, minimax-m2.7, minimax-m2.5, glm-5.2, glm-5.1, glm-5, kimi-k2.5, kimi-k2.6, kimi-k2.7-code, grok-4.5, grok-build-0.1, big-pickle, mimo-v2.5-free, north-mini-code-free, nemotron-3-ultra-free, deepseek-v4-flash-free.

Gemini entries are excluded because the official table assigns them Google's model-specific protocol. A catalog miss never falls back to another Zen wire shape, including when a custom Zen base URL is configured.

Hugging Face Provider vs MCP vs Hub

Ghosty's huggingface provider ID is only the OpenAI-compatible chat inference route through Hugging Face Inference Providers. It is selected with /provider huggingface, GHOSTY_PROVIDER=huggingface, or provider = "huggingface".

Hugging Face MCP is a separate external-tool route. Configure it through the MCP config described in docs/MCP.md, preferably using the settings-generated snippet from https://huggingface.co/settings/mcp. In the TUI, /hf mcp status checks whether the Hugging Face MCP server appears in the resolved MCP config, /hf mcp setup prints the settings workflow and a placeholder-only shape, and /hf concepts explains the provider/MCP/Hub distinction.

Hub publishing or repository management remains explicit user action through Hub-native tooling such as huggingface_hub or git. The /hf helper does not upload to Hugging Face and does not perform direct Hugging Face Hub HTTP search.

Xiaomi MiMo Notes

xiaomi-mimo defaults to mimo-v2.5-pro for long-context reasoning and coding work. The chat picker also exposes mimo-v2.5-pro-ultraspeed and the latest Omni model mimo-v2.5. Xiaomi MiMo TTS is available through ghosty --provider xiaomi-mimo speech "text" --model tts (or the tts alias). In Act and Operate, the provider-specific speech / tts tools are available through deferred discovery when the Xiaomi MiMo route is configured.

/provider xiaomi-mimo ultraspeed and /provider xiaomi-mimo pro-ultraspeed both select mimo-v2.5-pro-ultraspeed. Speech aliases such as tts, voice-design, and voice-clone are separate from normal chat defaults.

Token Plan keys default to the Singapore endpoint https://token-plan-sgp.xiaomimimo.com/v1. If your MiMo account is provisioned for the China region, set base_url = "https://token-plan-cn.xiaomimimo.com/v1" explicitly in [providers.xiaomi_mimo] or set mode = "token-plan-cn". Europe Token Plan accounts can set base_url = "https://token-plan-ams.xiaomimimo.com/v1" or use mode = "token-plan-ams"; mode = "pay-as-you-go" selects the standard API endpoint and standard MiMo key family. Xiaomi Token Plan docs and console expose credit/quota semantics, but Ghosty does not currently have a documented balance endpoint to poll, so cost display remains unknown rather than reusing token-price estimates from another provider.

Voice-design and voice-clone shorthands map to mimo-v2.5-tts-voicedesign and mimo-v2.5-tts-voiceclone. Xiaomi's current image-understanding guide includes mimo-v2.5 for image input. Ghosty exposes image analysis through the separate [vision_model] / image_analyze path; set that model to mimo-v2.5 when using MiMo for vision.

OpenRouter-Compatible Base URLs

OpenRouter-compatible gateways should usually stay on the openrouter provider with a provider-scoped base_url override instead of moving through the generic openai route. That keeps OpenRouter-style reasoning, streaming, cache usage, and namespaced wire model parsing attached to the selected route:

provider = "openrouter"

[providers.openrouter]
api_key = "sk-..."
base_url = "https://openrouter-compatible.example/v1"
model = "deepseek/deepseek-v4-pro"

Ghosty preserves the deepseek/ wire-model prefix under the OpenRouter provider scope; it does not infer a switch to the direct DeepSeek provider from that model string. Cache fields such as prompt_cache_hit_tokens, prompt_cache_miss_tokens, and prompt_tokens_details.cached_tokens are parsed when the upstream gateway sends them. If a key/account type omits those fields, Ghosty treats them as absent for that response rather than as a different provider route.

OrcaRouter (https://api.orcarouter.ai/v1) is a dedicated named route (OrcaRouter) that speaks the same OpenAI Chat Completions wire protocol and serves the same namespaced vendor/model catalog. It does not need an OpenRouter-compatible base_url override: select provider = "orcarouter" and its namespaced wire models (for example deepseek/deepseek-v4-pro or its own orcarouter/auto router) pass through verbatim, exactly as they do on the OpenRouter provider scope.

Recent OpenRouter Large Models

OpenRouter completions and static registry rows include the April 2026 onward large models verified through OpenRouter's model metadata: arcee-ai/trinity-large-thinking, qwen/qwen3.6-flash, qwen/qwen3.6-35b-a3b, qwen/qwen3.6-max-preview, qwen/qwen3.6-27b, qwen/qwen3.6-plus, minimax/minimax-m3, xiaomi/mimo-v2.5-pro, xiaomi/mimo-v2.5, moonshotai/kimi-k2.7-code, moonshotai/kimi-k2.6, z-ai/glm-5.1, z-ai/glm-5.2, z-ai/glm-5-turbo, tencent/hy3-preview, google/gemma-4-31b-it, google/gemma-4-26b-a4b-it, and nvidia/nemotron-3-nano-omni-30b-a3b-reasoning:free. minimax/minimax-m3 was added from OpenRouter's May 31, 2026 listing as a 1M context multimodal model for coding, tool use, and long-horizon agentic work. GLM-5.3 is now the default direct Z.AI Coding Plan model; GLM-5.2 / z-ai/glm-5.2 remain available (explicit selections keep their own id), GLM-5.1 / z-ai/glm-5.1 remain available as the smaller model, GLM-5.3-Flash / z-ai/glm-5.3-flash is the faster/explore sibling of GLM-5.3, and GLM-5-Turbo / z-ai/glm-5-turbo remains the faster sibling of GLM-5.2. GLM-5.3 / z-ai/glm-5.3 and GLM-5.3-Flash / z-ai/glm-5.3-flash are first-class picker ids on the Z.ai and OpenRouter routes (/model after /provider zai, or model = "GLM-5.3-Flash"). Limits and reasoning options for 5.3 are inherited from GLM-5.2 until Z.ai publishes distinct 5.3 metadata, and 5.3 carries no price. Flash ships the published $0.15/$0.50 list. A live call can still 429 with entitlement code 1311 on accounts that are not provisioned for 5.3.

EasyBits Notes

EasyBits.cloud is a DeepSeek reseller — same API, same models, same reasoning behavior. Since 0.0.15 easybits is a first-class ProviderKind (no longer an alias to deepseek): the base URL defaults to https://www.easybits.cloud/api/v2/llm/v1, the credential lives in [providers.easybits], and the model catalog, effort ladder and endpoint roster are shared with DeepSeek. In the route resolver EasyBits is classified as a reseller (pass-through), not a strict direct provider. One EasyBits key (eb_sk_live_...) serves both the LLM provider and the EasyBits MCP server.

Setup:

ghosty auth set --provider easybits --api-key eb_sk_live_...

On a fresh install this also makes easybits the active provider. On an existing config it only stores the key; switch with /provider (session) and /model save-default (persist).

provider = "easybits"

[providers.easybits]
base_url = "https://www.easybits.cloud/api/v2/llm/v1"   # optional; this is the default
# model  = "deepseek-v4-pro"                             # or deepseek-v4-flash

Tool budget. DeepSeek's API caps requests at 128 tools and counts every advertised tool (it ignores defer_loading). EasyBits exposes core (65) and sandbox (47); with Ghosty's ~36 built-ins only one group fits at a time. Ghosty warns before sending an oversized request. For boxes and S3/DB in the same turn, connect only ?tools=sandbox over MCP and call the REST API for the rest — see TALLER.md.

Footgun — env overrides config. GHOSTY_PROVIDER / legacy DEEPSEEK_PROVIDER override provider = "easybits" from the config file. A stray export DEEPSEEK_PROVIDER=deepseek silently flips the active provider; unset DEEPSEEK_PROVIDER GHOSTY_PROVIDER or open a fresh shell.

Static Model Registry

ghosty model list and ghosty model resolve use the static registry in crates/agent/src/lib.rs. This is not the same as live /models discovery. Use /models or ghosty models to fetch model IDs from the active API endpoint when the endpoint supports model listing.

Provider	Static registry entries	Tool calls	Registry reasoning flag
deepseek	deepseek-v4-pro, deepseek-v4-flash, deepseek-v4-flash-vision-exp	yes	yes
nvidia-nim	deepseek-ai/deepseek-v4-pro, deepseek-ai/deepseek-v4-flash	yes	yes
openai	deepseek-v4-pro, deepseek-v4-flash, gpt-5.6, gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna	yes	yes
atlascloud	deepseek-ai/deepseek-v4-flash, deepseek-ai/deepseek-v4-pro	yes	yes
wanjie-ark	deepseek-reasoner	yes	yes
volcengine	DeepSeek-V4-Pro, DeepSeek-V4-Flash	yes	yes
openrouter	deepseek/deepseek-v4-pro, deepseek/deepseek-v4-flash, arcee-ai/trinity-large-thinking, minimax/minimax-m3, minimax/minimax-m2.7, xiaomi/mimo-v2.5-pro, xiaomi/mimo-v2.5, qwen/qwen3.6-flash, qwen/qwen3.6-35b-a3b, qwen/qwen3.6-max-preview, qwen/qwen3.6-27b, qwen/qwen3.6-plus, qwen/qwen3.7-max, moonshotai/kimi-k2.7-code, moonshotai/kimi-k2.6, z-ai/glm-5.1, z-ai/glm-5.2, z-ai/glm-5.3, z-ai/glm-5.3-flash, z-ai/glm-5-turbo, tencent/hy3-preview, google/gemma-4-31b-it, google/gemma-4-26b-a4b-it, nvidia/nemotron-3-nano-omni-30b-a3b-reasoning:free, nvidia/nemotron-3-ultra-550b-a55b	yes	yes
orcarouter	deepseek/deepseek-v4-pro, deepseek/deepseek-v4-flash, orcarouter/auto	yes	yes
xiaomi-mimo	mimo-v2.5-pro, mimo-v2.5-pro-ultraspeed, mimo-v2.5; speech/TTS IDs are selected through ghosty speech / tts	yes	yes for chat models; no for speech/TTS models
novita	deepseek/deepseek-v4-pro, deepseek/deepseek-v4-flash	yes	yes
fireworks	accounts/fireworks/models/deepseek-v4-pro	yes	yes
siliconflow	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	yes	yes
arcee	trinity-large-thinking, trinity-large-preview; provider-hinted custom model IDs pass through	yes	yes for trinity-large-thinking; no for trinity-large-preview
moonshot	kimi-k2.7-code, kimi-k2.6	yes	yes
zai	GLM-5.3, GLM-5.3-Flash, GLM-5.2, GLM-5.1, GLM-5-Turbo; provider-hinted custom model IDs pass through	yes	yes
stepfun	step-3.7-flash	yes	no
minimax	MiniMax-M3, MiniMax-M2.7, MiniMax-M2.7-highspeed, MiniMax-M2.5, MiniMax-M2.5-highspeed, MiniMax-M2.1, MiniMax-M2.1-highspeed, MiniMax-M2	yes	yes
minimax-anthropic	MiniMax-M3, MiniMax-M2.7	yes	yes
sglang	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	yes	yes
vllm	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	yes	yes
ollama	deepseek-v4-flash; custom tags pass through when provider hint is ollama	yes	no
ollama-cloud	gpt-oss:120b; arbitrary provider-owned model IDs pass through	yes	yes
huggingface	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	yes	no
deepinfra	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash	yes	yes
together	deepseek-ai/DeepSeek-V4-Pro, deepseek-ai/DeepSeek-V4-Flash, thinkingmachines/inkling	yes	yes
openai-codex	gpt-5.5	yes	yes
anthropic	claude-opus-5, claude-opus-4-8, claude-sonnet-5, claude-sonnet-4-6, claude-fable-5, claude-haiku-4-5	yes	yes except claude-haiku-4-5
openmodel	deepseek-v4-flash; provider-scoped custom model IDs pass through	yes	model-dependent
sakana	fugu, fugu-ultra-20260615	yes	yes for fugu-ultra-20260615
longcat	LongCat-2.0	yes	yes
opencode-go	deepseek-v4-pro, grok-4.5, glm-5.2, glm-5.1, kimi-k3, kimi-k2.7-code, kimi-k2.6, deepseek-v4-flash, mimo-v2.5, mimo-v2.5-pro	yes	yes
meta	muse-spark-1.2	yes	yes
xai	grok-4.6, grok-4.5, grok-4.3, grok-build, grok-composer-2.5-fast, grok-4.20-0309-reasoning, grok-4.20-0309-non-reasoning	yes	yes for grok-4.6, grok-4.5, grok-4.3, grok-build, and grok-4.20-0309-reasoning
google	gemini-3.1-pro-preview, gemini-3-pro-preview, gemini-3.7-flash, gemini-3.6-flash, gemini-3.5-flash, gemini-3.5-flash-lite, gemini-2.5-pro, gemini-2.5-flash	yes	yes except gemini-3.5-flash-lite
mistral	mistral-code-latest, mistral-medium-latest, mistral-small-latest, mistral-large-latest	yes	yes for Medium and Small (reasoning_effort none or high on exact first-party routes); deprecated native Magistral remains an always-on explicit compatibility ID; no for Code and Large
modelstudio-token-plan, modelstudio-coding-plan	qwen3.8-max, qwen3.8-max-preview, qwen3.7-plus, qwen3.7-max, qwen3.6-flash, deepseek-v4-pro, deepseek-v4-flash-0731, glm-5.2	yes	yes

AtlasCloud keeps the same default model as the config layer and adds provider-scoped aliases for the Pro and Flash rows. Other AtlasCloud model IDs should still be selected through ATLASCLOUD_MODEL, config, or live model listing when available.

Capability Metadata

ghosty doctor --json exposes the capability object. It is static metadata, not a live API probe. Current fields are:

resolved_provider, resolved_model, context_window, max_output, thinking_supported, cache_telemetry_supported, and request_payload_mode.

When configuration cannot be loaded or validated, doctor --json exits nonzero and prints a bounded, secret-redacted JSON error envelope with status = "error" and error.kind = "config_validation" instead of emitting misleading route or capability metadata.

Most shipped providers use the Chat Completions request payload mode. Native Messages routes, including minimax-anthropic, use /v1/messages, and openai-codex uses Responses.

For OpenAI-compatible gateways or self-hosted runtimes whose real window differs from the static table, set [providers.<name>] context_window = N. The configured value becomes the route-effective context window for prompts, context-pressure checks, compaction, and output-cap budgeting.

max_output is optional and truthful: it is null (and omitted from the capability struct on the wire) when the route publishes no output maximum we can stand behind — the Kimi Code membership kimi-for-coding family is the canonical example, since the membership catalog owns their limits. An unknown output ceiling is never backfilled with a placeholder, and it applies no compatibility clamp to a turn's requested max_tokens; only a concrete route/offering maximum narrows the request. A model the catalogue simply has no row for is a different fact — absence is not permission, so an uncatalogued id keeps a conservative ceiling. The "Max output metadata" column below reads unknown wherever no documented maximum exists.

The exact Kimi Code membership roster contains k3, k3-256k, kimi-for-coding, and kimi-for-coding-highspeed. The two K3 ids share the same reasoning and fixed-sampling contract; k3-256k stays at 262,144 tokens, while bare k3 can use an entitled 1M override.

Provider/model class	Context window	Max output metadata	Thinking support	Cache telemetry	FIM endpoint
DeepSeek V4 (deepseek-v4-pro, deepseek-v4-flash)	1,000,000	384,000	yes	yes	DeepSeek beta only
DeepSeek V4 Flash Vision experimental (deepseek-v4-flash-vision-exp)	1,000,000 inherited from Flash	384,000 inherited from Flash	yes, inherited	yes, inherited	not claimed; Chat Completions route only
DeepSeek compatibility aliases (deepseek-chat, deepseek-reasoner)	1,000,000	384,000	yes	yes	DeepSeek beta only
NVIDIA NIM V4 registry models	1,000,000	384,000	yes	yes	not documented in code
Volcengine Ark V4 model IDs	1,000,000	384,000	yes	yes	not documented in code
OpenRouter, Novita, Fireworks, SiliconFlow, SGLang, and vLLM V4 model IDs	1,000,000	384,000	yes	no	not documented in code
Xiaomi MiMo mimo-v2.5-pro, mimo-v2.5-pro-ultraspeed, mimo-v2.5	1,000,000	131,072	yes	no	not documented in code
OpenRouter Qwen 3.6 Flash / Plus	1,000,000	65,536	yes	no	not documented in code
OpenRouter Qwen 3.6 35B / 27B	262,144	262,140	yes	no	not documented in code
OpenRouter Qwen 3.6 Max Preview	262,144	65,536	yes	no	not documented in code
OpenAI API gpt-5.5	1,050,000	128,000	yes	no	not documented in code
OpenAI API gpt-5.6, gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna	1,050,000	128,000	yes	no	not documented in code
Anthropic API claude-opus-5, claude-opus-4-8, claude-sonnet-5, claude-sonnet-4-6, claude-fable-5	1,000,000	128,000	yes	yes	not documented in code
Google Gemini API gemini-3.7-flash, gemini-3.6-flash, gemini-3.5-flash, gemini-3.5-flash-lite, gemini-3.1-pro-preview, gemini-2.5-pro, gemini-2.5-flash	1,048,576	65,536	model-dependent	no	not documented in code
Meta Model API muse-spark-1.2	1,000,000	32,000	yes	no	not documented in code
OpenAI Codex / ChatGPT route (openai-codex)	400,000 effective	128,000	yes	no	route uses Responses payload at /codex/responses
OpenModel default/custom model IDs	200,000 fallback unless model metadata or config overrides it	64,000 fallback	model-dependent	no	route uses Messages payload at /v1/messages
Wanjie Ark reasoner / r1 model IDs	128,000	unknown (no documented maximum)	yes	no	not documented in code
Direct Arcee API trinity-large-thinking	262,144	262,144	yes	no	not documented in code
Direct Arcee API trinity-large-preview	262,144	unknown (no documented maximum)	no in doctor capability metadata	no	not documented in code
Direct Moonshot kimi-k3	1,048,576	1,048,576 documented maximum; 131,072 provider default	yes	no	exact route uses max_completion_tokens and omits fixed sampling fields (K3 quickstart)
Kimi Code membership k3	262,144 safe baseline; 1,048,576 with an explicit entitled-plan override	131,072 conservative default ceiling; membership maximum is not published	yes	no	exact https://api.kimi.com/coding/v1 route
Kimi Code membership k3-256k	262,144 fixed	131,072 conservative default ceiling; membership maximum is not published	yes	no	exact https://api.kimi.com/coding/v1 route
Direct Moonshot/Kimi K2.7/K2.6 (kimi-k2.7-code, kimi-k2.7-code-highspeed, kimi-k2.6)	262,144	32,768	yes	no	provider-reported bundled catalog
Kimi Code membership kimi-for-coding, kimi-for-coding-highspeed	262,144	unknown — the membership catalog owns these limits and no client-side ceiling is claimed	yes	no	exact https://api.kimi.com/coding/v1 route
Direct Z.AI GLM-5.3 (default)	1,000,000	131,072	yes	no	live on the GLM Coding Plan; limits inherited from GLM-5.2 until Z.ai publishes distinct 5.3 numbers; no USD price
Direct Z.AI GLM-5.3-Flash	1,000,000	131,072	yes	no	natively multimodal; $0.15/$0.50 list (2026-08-26); faster/explore sibling of GLM-5.3
Direct Z.AI GLM-5.2	1,000,000	131,072	yes	no	not documented in code
Direct Z.AI GLM-5.1	202,752	131,072	yes	no	not documented in code
Direct Z.AI GLM-5-Turbo	202,752	131,072	yes	no	faster/explore sub-agent sibling
Direct MiniMax MiniMax-M3	1,000,000	524,288	yes	no	not documented in code
Direct MiniMax M2.x models	204,800	unknown until MiniMax output metadata is promoted	yes	no	not documented in code
MiniMax Messages route (MiniMax-M3, MiniMax-M2.7)	model-specific values above	model-specific values above	yes	no	route uses /anthropic/v1/messages
Generic openai and AtlasCloud	128,000	unknown (no documented maximum)	no in doctor capability metadata	no	not documented in code
Ollama	8,192	unknown (no documented maximum)	no	no	not documented in code
Hugging Face Inference Providers V4 model IDs	131,072	unknown (no documented maximum)	yes	no	not documented in code
Other recognized DeepSeek model IDs	128,000 unless the model name carries an explicit Nk hint	unknown (no documented maximum)	no unless V4/reasoner logic matches	DeepSeek/NIM only	DeepSeek beta only

MiniMax M3 uses input-length and service tiers. Ghosty omits service_tier, so requests use the standard tier and cost estimates select the correct standard rate from total input usage. Priority rates are listed to keep the official tier structure visible. Prices are USD per million tokens.

Model / service tier	Input length	Input	Output	Cache read	Cache write
MiniMax-M3 standard	up to 512,000 input tokens	$0.30	$1.20	$0.06	not published
MiniMax-M3 standard	over 512,000 input tokens	$0.60	$2.40	$0.12	not published
MiniMax-M3 priority	up to 512,000 input tokens	$0.45	$1.80	$0.09	not published
MiniMax-M3 priority	over 512,000 input tokens	$0.90	$3.60	$0.18	not published
MiniMax-M2.7 standard	all supported inputs	$0.30	$1.20	$0.06	$0.375

These values come from the MiniMax pay-as-you-go pricing guide. M3 thinking is adaptive or disabled; the OpenAI-compatible API defaults to adaptive and the Anthropic-compatible API defaults to disabled. M2.7 thinking cannot be disabled. Ghosty sends explicit controls when the user selects a reasoning mode.

Tool-call support is tracked separately by the static ModelRegistry and by the endpoint's ability to accept OpenAI-compatible tools payloads. A custom OpenAI-compatible or local endpoint can still reject tool calls even if Ghosty can send the schema.

Hugging Face Inference Providers Notes

The shipped Hugging Face route targets the OpenAI-compatible Inference Providers router at https://router.huggingface.co/v1. Configure auth with HUGGINGFACE_API_KEY first, or HF_TOKEN as a fallback. Configure the endpoint with HUGGINGFACE_BASE_URL first, or HF_BASE_URL as a fallback; configure the model with HUGGINGFACE_MODEL first, or HF_MODEL as a fallback.

This route does not imply Hub browsing, model-card metadata, dataset access, Jobs, uploads, or export. Those remain explicit Model Lab work items so provider auth and artifact movement stay separate.

When a Local Model Prints Tool JSON

Ghosty only executes tools when the provider returns Chat Completions tool_calls or streamed delta.tool_calls. If a local model prints text such as {"name":"File","arguments":{"action":"search_content",...}} in the assistant message, that is ordinary model output, not an executable tool request.

For OpenAI-compatible or local runtimes, check:

• The endpoint accepts the tools array in /v1/chat/completions requests.
• The selected model or chat template is configured for function/tool calls.
• The server returns tool_calls in the response rather than plain JSON text.
• The compatibility layer does not strip tools before forwarding the request.
• If in doubt, test a small File read or search_content action against a known tool-calling model before debugging Ghosty's tool registry.

Changing provider, base_url, or model can select a route that supports the OpenAI-compatible payload shape, but Ghosty cannot convert arbitrary JSON text into a trusted tool call after the model has emitted it as prose.

DeepSeek will retire deepseek-chat and deepseek-reasoner on 2026-07-24 at 15:59 UTC. Ghosty migrates either name to deepseek-v4-flash before a request reaches DeepSeek's first-party OpenAI or Anthropic endpoint. If no reasoning tier was configured, deepseek-chat also migrates to off and deepseek-reasoner to high, preserving their former non-thinking / thinking intent; an explicit reasoning_effort remains authoritative. The mapping is deliberately not global: Wanjie Ark, aggregators, self-hosted runtimes, and custom endpoints continue to own their model ids.

Reasoning Effort

/reasoning <effort> (and the reasoning_effort config key) is translated to each provider's wire dialect by the client before the request is sent. off disables thinking where the route supports it. Both exact K3 routes map off to their lowest supported tier, low, and the model is never switched to satisfy off — but they do so for different reasons:

• Kimi Code membership K3 (exact https://api.kimi.com/coding/v1 with model = "k3" or model = "k3-256k") — the membership roster declares K3 always-thinking, so off cannot be honored without changing what the model is. The clamp preserves the fixed K3 identity.
• Direct Moonshot K3 (exact https://api.moonshot.ai/v1 with model = "kimi-k3") — this clamp is defensive, not a documented contract. The direct platform publishes no off state for K3, and Ghosty will not assert a fixed-thinking guarantee it cannot verify for a given key's entitlement, so the requested off is normalized to the lowest tier with the live entitlement left unknown.

Normal dispatched auto uses Ghosty's auto-reasoning selector and sends a concrete tier; only an omitted reasoning setting leaves the provider default in control. Providers marked "omitted" receive no reasoning fields at all for that tier.

Provider	off	low/medium/high	max/xhigh
deepseek, deepseek-cn, siliconflow, siliconflow-CN, sglang, volcengine, atlascloud	thinking: {type: disabled}	reasoning_effort: "high" + thinking: {type: enabled}	reasoning_effort: "max" + thinking: {type: enabled}
openrouter, novita, other together models	thinking: {type: disabled}	reasoning_effort pass-through + thinking: {type: enabled}	reasoning_effort: "xhigh" + thinking: {type: enabled}
together + thinkingmachines/inkling	reasoning_effort: "none"	exact minimal/low/medium/high reasoning_effort	reasoning_effort: "max"
Direct Moonshot kimi-k3 at exact https://api.moonshot.ai/v1	top-level reasoning_effort: "low" (effective normalization)	top-level reasoning_effort: "low" / "high" (medium becomes high)	top-level reasoning_effort: "max"
Kimi Code membership k3, k3-256k at exact https://api.kimi.com/coding/v1	thinking: {type: enabled, effort: "low"} (effective normalization)	`thinking: {type: enabled, effort: "low"	"high"}`
Other moonshot routes	thinking: {type: disabled}	thinking: {type: enabled}	thinking: {type: enabled}
ollama	think: false	think: true	think: true
ollama-cloud	reasoning_effort: "none"	exact low/medium/high reasoning_effort	reasoning_effort: "max"
xiaomi-mimo	thinking: {type: disabled}	thinking: {type: enabled}	thinking: {type: enabled}
First-party minimax MiniMax-M3	reasoning_split: true + thinking: {type: disabled}	reasoning_split: true + thinking: {type: adaptive}; effective tier granularity unavailable	reasoning_split: true + thinking: {type: adaptive}; effective tier granularity unavailable
First-party Z.ai GLM-5.2	thinking: {type: disabled}; no reasoning_effort	enabled thinking; only effective high adds reasoning_effort: "high"	enabled thinking + reasoning_effort: "max"
First-party Z.ai GLM-5.3	thinking: {type: disabled}; no reasoning_effort	enabled thinking; only effective high adds reasoning_effort: "high"	enabled thinking + reasoning_effort: "max"
First-party Z.ai GLM-5.3-Flash	thinking: {type: disabled}; no reasoning_effort	enabled thinking; only effective high adds reasoning_effort: "high"	enabled thinking + reasoning_effort: "max"
First-party Z.ai GLM-5-Turbo	thinking: {type: disabled}	enabled thinking; effort granularity unavailable	enabled thinking; effort granularity unavailable
Compatible gateways configured as zai	omitted; effective unavailable	omitted; effective unavailable	omitted; effective unavailable
nvidia-nim	chat_template_kwargs.thinking: false	chat_template_kwargs: thinking: true + reasoning_effort: "high"	chat_template_kwargs: thinking: true + reasoning_effort: "max"
vllm	chat_template_kwargs.enable_thinking: false	chat_template_kwargs.enable_thinking: true + reasoning_effort low/medium/high	chat_template_kwargs.enable_thinking: true + reasoning_effort: "high" (vLLM has no max tier)
arcee, huggingface	omitted	reasoning_effort pass-through	reasoning_effort: "high"
fireworks	omitted	reasoning_effort: "high"	reasoning_effort: "max"
openai, wanjie-ark, telecomjs	omitted	omitted	omitted
openmodel	Anthropic Messages adapter handles thinking/output configuration	Anthropic Messages adapter handles thinking/output configuration	Anthropic Messages adapter handles thinking/output configuration
openai-codex	Responses API reasoning field (handled by the Responses bridge)	Responses API reasoning field	Responses API reasoning field

AtlasCloud serves DeepSeek models, so it speaks the DeepSeek reasoning dialect, including the max tier (#3024).

On the exact MiniMax OpenAI-compatible Chat endpoints, MiniMax-M3 uses max_completion_tokens. Other MiniMax models and compatible gateways retain max_tokens; the MiniMax Anthropic endpoints use the separate Messages adapter.

Drift Check

Run this before changing provider IDs, provider TOML tables, static model registry rows, or provider default strings:

python3 scripts/check-provider-registry.py

The check fails when:

• docs/PROVIDERS.md omits a canonical ProviderKind::as_str() ID.
• crates/tui/src/config.rs ApiProvider::as_str() diverges from ProviderKind::as_str() except for the explicit deepseek-cn legacy alias.
• The shipped-provider table omits or adds a [providers.*] TOML table.
• The static model registry table drifts from providers used by crates/agent/src/lib.rs.
• A provider default model or base URL constant in crates/tui/src/config.rs is no longer mentioned here.

Planned, Not Shipped Yet

These items belong to the v0.8.48+ provider-abstraction milestone or related provider docs work, but they are not native shipped behavior in this checkout:

• A unified Provider trait in ghosty-agent that owns env precedence, secret resolution, base URL normalization, auth-header construction, and provider metadata. Those responsibilities are still split across crates/config, crates/secrets, and crates/tui/src/client.rs.
• Hugging Face model passport metadata in the picker, including license, base model, context length, chat template, tool-call support, reasoning support, and gated/private status.