简体中文

On this page

DeepSeek Provider

Docs home · Provider guide · Configuration · OpenAI-compatible · Anthropic · Gemini · 简体中文

Use the DeepSeek provider when you want Sigil's default Quick Setup path, DeepSeek chat models, and DeepSeek-specific FIM or endpoint settings.

Minimal Setup

For temporary local use, set the API key before launch:

export SIGIL_API_KEY="sk-..."
sigil

For repeatable config, use:

[agent]
provider = "deepseek"
model = "deepseek-v4-flash"
tool_timeout_secs = 30

[model_request]
request_timeout_secs = 120
stream_idle_timeout_secs = 180

[providers.deepseek]
base_url = "https://api.deepseek.com"
beta_base_url = "https://api.deepseek.com/beta"
anthropic_base_url = "https://api.deepseek.com/anthropic"
fim_model = "deepseek-v4-pro"
# Prefer SIGIL_API_KEY. If written here, the key is stored as plaintext.
# api_key = "sk-..."
user_id_strategy = "stable_per_end_user"
strict_tools_mode = "auto"

A shorter template is available at deepseek-basic.toml.

Authentication

Sigil resolves DeepSeek authentication in this order:

SIGIL_API_KEY
[providers.deepseek].api_key

Prefer SIGIL_API_KEY for local shells and CI. If you save api_key through /config, it is written as plaintext to sigil.toml; keep that file private and out of commits.

Common Fields

Field	Purpose
`fim_model`	Model used for DeepSeek FIM-related flows when available.
`base_url`	Main DeepSeek API endpoint.
`beta_base_url`	DeepSeek beta endpoint for features that require it.
`anthropic_base_url`	DeepSeek Anthropic-compatible endpoint when a build uses that route.
`strict_tools_mode`	DeepSeek-specific tool strictness behavior. Use `auto` unless you need a known override.
`user_id_strategy`	How Sigil provides a stable user identifier to the provider.

The TUI /config surface focuses on high-frequency fields such as model, api_key, base_url, and fim_model. Lower-frequency DeepSeek fields remain file or environment configuration.

Environment Overrides

Variable	Overrides
`SIGIL_BASE_URL`	`[providers.deepseek].base_url`
`SIGIL_BETA_BASE_URL`	`[providers.deepseek].beta_base_url`
`SIGIL_ANTHROPIC_BASE_URL`	`[providers.deepseek].anthropic_base_url`
`SIGIL_FIM_MODEL`	`[providers.deepseek].fim_model`
`SIGIL_USER_ID_STRATEGY`	`[providers.deepseek].user_id_strategy`
`SIGIL_STRICT_TOOLS_MODE`	`[providers.deepseek].strict_tools_mode`

The authentication variable SIGIL_API_KEY is documented in Authentication above.

Image attachments are not enabled for the DeepSeek provider in V1 because its current Sigil chat contract is text/tool based. Attached-image requests fail before provider transport. Use an explicitly supported provider from Image Attachments.

Verify

Run:

sigil doctor

Check that the report shows deepseek, the expected model, and the intended API key source. The report never prints the key value.

Common Problems

Symptom	Check
Sigil asks for setup again	Confirm the expected `sigil.toml` is found by the config resolution order.
Authentication fails	Confirm `SIGIL_API_KEY` is set in the shell that launches `sigil`.
Wrong model is used	Check `[agent].model` and any role-specific task model override.
Slow or interrupted responses	Check network access and consider `[model_request].stream_idle_timeout_secs`.
FIM behavior is unavailable	Confirm `fim_model` is configured and supported by the selected endpoint.