dshplugin.devDeepSeek Harness Plugins
DSH Credentials Keychain plugin logo
DeepSeek Harness Plugin

DSH Credentials Keychain

0
Published by ShawnSiao

Planned OS-backed credential provider for DeepSeek Harness

Securitycredential-managerdeepseek-harnessdsh-pluginsecurity

Get this plugin

Review the source, then continue to the publisher.

Get this plugin
Share on X ↗

About this plugin

Source snapshot 8/13/2026

dsh-credentials-keychain

English | 简体中文

An OS-backed credential provider bundle for DeepSeek Harness.

Status: design and implementation planning. This repository does not yet contain an installable plugin.

Goal

Replace the default file-backed credentials row with a provider that keeps writable secrets in an operating-system credential store while preserving the existing ctx.credentials API used by model and web providers.

The first release should require no new secret-management workflow inside DeepSeek Harness: existing settings surfaces continue to call describe(), set(), and unset(), and consumers continue to resolve CredentialRef values per operation.

Planned user experience

Installation will use the normal profile bundle command:

dsh plugin --profile web add github:ShawnSiao/dsh-credentials-keychain

The bundle will replace the base profile's credentials row. Existing model settings remain the primary UI; no model-facing tool will expose or enumerate secret values.

Scope

  • Preserve inherited environment variables as the highest-precedence, read-only source for CI and one-off launches.
  • Store writable values in Windows Credential Manager, macOS Keychain, or Linux Secret Service.
  • Report only configured state, source, and writability to UI consumers.
  • Publish credentials/updated only after a committed write or removal.
  • Fail loudly when the selected backend is unavailable or its security guarantees do not satisfy configured policy.

Security stance

An OS credential store improves at-rest handling, but it is not automatically a hard boundary against every process running as the same user. The implementation will publish a platform capability matrix and will not claim stronger isolation than each backend can prove.

High-assurance options such as user-presence requirements or application-bound access will be separate, explicit modes. Silent fallback to plaintext files is out of scope.

See the implementation plan for architecture, phases, acceptance criteria, and open security decisions.

Compatibility baseline

Planning is based on DeepSeek Harness master commit 47f943859b and package version 0.1.0-rc.5 as observed on 2026-08-13. DeepSeek Harness is in developer preview; implementation work must recheck public APIs before each release.

License

MIT