Configuration

All knobs have schema defaults; override only the keys you want in your profile layer ($DSH_HOME/profiles//cordis.patch.yml). Full samples in examples/patches/.

Key	Type	Default	Description
`agentName`	string	`dsh`	`initialize.agentInfo.name` shown to clients
`provider`	string	-	pin the model for ACP sessions (must be set with `model`)
`model`	string	-	pin the model for ACP sessions (must be set with `provider`)
`token`	string	-	extra ACP bearer credential for web-mounted mode; otherwise DSH Web's login cookie is required. Standalone `serve` takes `--token`
`offerAlwaysPermissions`	boolean	`true`	include `allow_always` / `reject_always` options in permission requests
`flushOnTurnEnd`	boolean	`true`	flush session persistence after every completed turn
`hostControl`	boolean	`true`	expose `dsh/remote/*` host methods
`hostControlDeny`	string[]	`[]`	block endpoints such as `settings/`, `workspace/delete`, or ``

- id: acp-server
  config:
    agentName: my-dsh
    provider: liepin        # pin (or omit both to follow the live default)
    model: glm-5-3

Behavior follows the harness config conventions: the schema validates at plugin load (wrong types or a half-set provider/model pin fail loudly with the exact key), missing keys fall back to defaults (a patch layer replaces the whole config value, the schema refills the rest), and an unset provider/model follows the profile's agent-default-model - read per session, so in-GUI model switches apply to new ACP sessions too.

Model credentials come from the usual dsh places ($DSH_HOME settings / provider API-key envs), shared with the web UI - no second setup.

dsh-acp-server

インストール

ドキュメント

Configuration