mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
The native adapter's route was named deepseek, colliding with pi-ai's catalog provider of the same name, so the two DeepSeek paths could never be mounted side by side. The web settings page needs both configurable at once. Compositions, fixtures, goldens, scaffolding defaults, and docs all move together (pre-release, no shim); TUI/session-query-spill/ missing-credential goldens re-recorded through their keyless refresh modes because provider-name length shifts box padding and spill truncation points.
19 lines
741 B
YAML
19 lines
741 B
YAML
# Keyless dynamic-configuration composition: the base settings and credentials
|
|
# providers see only the isolated run home, no API key exists anywhere, and
|
|
# the deepseek-official route still registers — so the prompt fails with the actionable
|
|
# MISSING_CREDENTIAL guidance this snapshot pins as first-run UX.
|
|
- id: base
|
|
name: '@cordisjs/plugin-include'
|
|
config:
|
|
path: ./cordis.yml
|
|
patches:
|
|
- id: llm-deepseek
|
|
name: '@deepseek-ai/dsh-llm-deepseek'
|
|
disabled: true
|
|
- insert:
|
|
# The endpoint is never dialed: credential resolution fails first.
|
|
- id: llm-deepseek-keyless
|
|
name: '@deepseek-ai/dsh-llm-deepseek'
|
|
config:
|
|
baseURL: 'http://127.0.0.1:9'
|