dsh-tool-advisor

Configuration and audit records

Setting	Default	Purpose
provider, model	Empty; configure in the UI	Use an existing DSH model route; a patch or environment variables can supply initial values
enabled	true	The UI's Enable advisor toggle, persisted in DSH's advisor settings
storageDir	$DSH_HOME/advisor-audit, or ~/.dsh/advisor-audit when DSH_HOME is unset	Local audit and recovery records
maxInputBytes	32768	Combined UTF-8 byte limit for system instructions and the complete request
maxOutputTokens	0	Zero omits the plugin token override and uses the DSH model service settings; an optional custom limit is 128–1,000,000 tokens
maxOutputBytes	0	Zero removes the plugin response-size cap; an optional custom cap is 1024–16,777,216 UTF-8 bytes
maxCallsPerTask	8	Persistent dispatch budget shared across processes
timeoutMs	120000	Maximum model-call wait time after approval, in milliseconds

Both output settings are persisted in the advisor settings namespace; UI values override installation patches. Upgrading preserves explicitly configured limits (including old defaults saved in patches/settings). To remove them, enable both output options and save. A zero token setting is never sent as maxTokens: 0: the adapter resolves its own budget, which the approval displays when available. An absent adapter budget is shown as service-controlled rather than unlimited model output. The default 120-second request timeout remains in effect.

Oversized input is rejected rather than silently truncated. Token limits and billing semantics are implemented by the provider. Approval displays the adapter's resolved call configuration without estimating cost. A request allows at most 20 preview rebuilds.

The audit directory must be owned by the current user with mode 0700; files use 0600, and symlink paths are rejected. Records include request snapshots processed by redaction rules, approval decisions, send markers, and final results. They exclude raw provider configurations, authentication headers, API-key environment values, remote error details, and model reasoning streams. Snapshots may still contain code and business information explicitly approved by the user.

Audit records are not deleted automatically: deleting them also removes the basis for duplicate prevention and task call limits. Apply a retention policy only after the relevant tasks will no longer be resumed and no requests are running. The main model's file and command tools must not be able to modify the audit directory; that isolation is part of the DSH deployment configuration.