feat(provider): add deepseek provider for the DeepSeek pay-per-use API

[ferminquant]

Feature request: add deepseek provider for the DeepSeek pay-per-use API

Summary

Add a new clawpatch provider named deepseek that calls the DeepSeek
OpenAI-compatible chat completions endpoint directly via fetch(). This
unblocks clawpatch users who have a DeepSeek API key (pay-per-use billing at
https://platform.deepseek.com) when their default provider (codex) is
unavailable or rate-limited, or when they prefer to use DeepSeek for reviews.

Motivation

• The current codex default requires a local Codex CLI. Users who do
  not have Codex installed or authenticated have to fall back to acpx
  (which routes through openclaw) or to one of the other local CLI
  providers.
• DeepSeek exposes an OpenAI-compatible chat completions API at
  https://api.deepseek.com/v1/chat/completions on pay-per-use billing
  (no subscription, top up at https://platform.deepseek.com). This is a
  clean fit for clawpatch's per-call provider contract.
• clawpatch today supports 10 providers (codex, acpx, claude, cursor,
  grok, minimax, opencode, pi, mock, mock-fail). Adding
  deepseek covers a different distribution and is a real maintenance
  burden shared with maintainers.

Surface

Operation	Supported
map	yes
review	yes
revalidate	yes
fix	no (chat-completions API has no filesystem access; mirrors minimax contract)
doctor (check)	yes

Configuration

Env var	Required	Default	Purpose
DEEPSEEK_API_KEY	yes	—	Pay-per-use API key from https://platform.deepseek.com
DEEPSEEK_BASE_URL	no	https://api.deepseek.com/v1	Override the endpoint
DEEPSEEK_MODEL	no	deepseek-v4-flash	Default model
CLAWPATCH_DEEPSEEK_TIMEOUT_MS	no	300000	Per-call timeout
CLAWPATCH_PROVIDER_TIMEOUT_MS	no	300000	Fallback timeout

Endpoints

• POST /chat/completions — review, revalidate, map
• GET /models — connectivity check (used by check())

Live usage

A locally-patched implementation on the author's machine (not in the
upstream tarball) has been running against the real
https://api.deepseek.com/v1/chat/completions endpoint for ~7 days across
100+ features reviewed in ferminquant/budget, completing in 50–85s per
feature. A TypeScript port mirroring the merged minimax provider shape is
planned as a follow-up PR.

Labels

• enhancement — new feature
• help wanted — community contribution welcome
• impact:auth-provider — touches the auth/credentials surface
• documentation — README provider list + docs/providers.md need updates

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 14, 2026, 12:45 PM ET / 16:45 UTC.

Summary
Keep open: current main and v0.6.0 do not implement a deepseek provider, GitHub search found no canonical PR or duplicate, and adding a first-party provider/API-key surface needs maintainer product approval before implementation.

Reproducibility: not applicable. this is a new provider request, not a broken existing behavior report. Current-main source confirms deepseek is not a supported provider name today.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
The implementation shape is clear, but core provider inclusion and API-key surface expansion need maintainer approval before queuing a fix PR.

Review details

Best possible solution:

Maintainers should decide whether DeepSeek belongs as a core provider; if accepted, implement it as a MiniMax-style HTTP provider with safe credential/base-url handling, unsupported fix, focused provider tests, docs, and live smoke evidence.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a new provider request, not a broken existing behavior report. Current-main source confirms deepseek is not a supported provider name today.

Is this the best way to solve the issue?

Unclear: a MiniMax-style HTTP adapter is a plausible narrow implementation, but the best solution depends on maintainer approval for adding DeepSeek as another first-party provider surface.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Adding DeepSeek would broaden the core auth/provider surface with new API-key, endpoint, model-default, timeout, and HTTP error-handling behavior.
• The issue includes useful live-usage context, but no upstream TypeScript PR exists yet to review or validate against current provider tests.
• No VISION.md is present, so product fit for another first-party provider needs maintainer judgment rather than an explicit roadmap anchor.

Codex review notes: model internal, reasoning high; reviewed against 8a939cc6f85e.

Label changes

Label changes:

• remove clawsweeper:fix-shape-clear: Current issue advisory state no longer selects this label.

Label justifications:

• P2: This is a normal-priority provider capability request with bounded but real user-facing value.
• impact:auth-provider: The requested provider would add provider routing, model selection, endpoint configuration, and API-key handling for DeepSeek.

Evidence reviewed

What I checked:

• Repository policy read: AGENTS.md was present and read fully; its provider testing and secret-handling guidance applies to any eventual provider implementation. (AGENTS.md:1, 8a939cc6f85e)
• DeepSeek absent from provider registry: providerByName dispatches the supported providers and falls through to unsupported provider; the current list has no deepseek branch. (src/provider.ts:269, 8a939cc6f85e)
• Closest current implementation pattern is MiniMax: The existing MiniMax provider uses an HTTP chat-completions-style adapter, API-key env handling, base URL validation, model defaults, and explicit unsupported fix; this is the nearest source pattern for the requested DeepSeek provider. (src/provider.ts:457, 8a939cc6f85e)
• Supported provider docs omit DeepSeek: README and provider docs list current provider names including minimax, but no deepseek entry. (README.md:125, 8a939cc6f85e)
• Repository-wide DeepSeek search returned no source hits: Case-varied search for DEEPSEEK, DeepSeek, and deepseek found no matches in the checkout. (8a939cc6f85e)
• Release/current-main provenance: Latest release tag v0.6.0 contains MiniMax but no DeepSeek; the only current-main diff after v0.6.0 is a changelog opener, not provider code or docs. (CHANGELOG.md:3, 8a939cc6f85e)

Likely related people:

• steipete: GitHub commit metadata shows steipete authored the landed MiniMax provider commit, which is the closest implementation pattern for this DeepSeek request. (role: adjacent HTTP-provider contributor; confidence: high; commits: 3e024670aa06, 17dacf6c0f1e, 05fba5cfe778; files: src/provider.ts, src/provider.test.ts, README.md)
• ferminquant: The MiniMax provider commit is co-authored by ferminquant, and this issue explicitly proposes a DeepSeek port mirroring that provider shape. (role: prior adjacent provider contributor; confidence: medium; commits: 3e024670aa06; files: src/provider.ts, src/provider.test.ts, README.md)
• aurokin: GitHub commit metadata shows aurokin authored recent Claude and Cursor provider additions in the same provider registry and test surface. (role: provider registry contributor; confidence: medium; commits: 755186db3c63, 7cb059a6bc66; files: src/provider.ts, src/provider.test.ts, docs/providers.md)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[clawsweeper]

🦞🔧
ClawSweeper is automatically building this issue.

The issue review finished and no active implementation pull request was found.

Automatic implementation progress:

• State: Blocked
• Detail: The automatic implementation worker stopped before all deterministic gates completed. Open the workflow run for the exact blocker.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/27504258994
• Updated: 2026-06-14T16:01:51.032Z
• Opt out: add clawsweeper:manual-only or clawsweeper:human-review.

Result: implementation skipped.

• Reason: no planned fix actions
• Worker: https://github.com/openclaw/clawsweeper/actions/runs/27504258994
• Updated: 2026-06-14T16:01:46.889Z

[steipete]

Closing as out of scope. Clawpatch now supports coding harnesses and agent CLIs only; direct model inference API integrations are intentionally excluded.

The policy and removal are documented in VISION.md and landed through #137. Provider support should be added to a coding harness or ACP adapter first, then consumed by Clawpatch through that harness.