deepseekharness-acp-interactive

Configuration

State lives in the dsh home — $DSH_HOME, or the current user's default .dsh directory — where settings.yaml holds providers and model catalogs and .credentials.yaml holds credentials. Pi Agent Desktop and Zed ACP can therefore share provider profiles, model catalogs, and credential references without copying API keys into Zed or cordis.yml; a profile's apiKeyEnv must match a key under .credentials.yaml refs, and the two remain separate processes with isolated sessions. Changes to settings.yaml refresh the provider directory through the existing settings and LLM-registry update path, and the bundled dormant llm-pi-ai mount registers every route under llm-pi-ai.providers.

At startup, Windows registers the native pwsh tool while Linux and macOS register bash; the model never receives both tool dialects. Stdout carries JSON-RPC frames only.

An explicitly configured image-capable model must declare its input modalities; without them the DeepSeek adapter treats the entry as text-only and the bridge rejects image admission before queuing the prompt:

- id: deepseek-v4-flash-vision-exp
  inputModalities: [text, image]

Custom deployments may instead consume only the transport export and mount it in a dedicated ACP stdio composition, where provider and model select the initial route for new sessions without restricting the model selector:

- id: settings
  name: '@deepseek-ai/dsh-settings-file'

- id: credentials
  name: '@deepseek-ai/dsh-credentials-local'

- id: llm-pi-ai
  name: '@deepseek-ai/dsh-llm-pi-ai'

- id: acp-interactive
  name: 'dsh-acp-interactive'
  config:
    provider: deepseek-official
    model: deepseek-v4-pro