deepseek-harness/packages/credentials
2026-08-21 19:48:58 +08:00
..
authorization release(dsh): 0.1.1-rc.2 2026-08-21 19:48:58 +08:00
credentials release(dsh): 0.1.1-rc.2 2026-08-21 19:48:58 +08:00
credentials-local release(dsh): 0.1.1-rc.2 2026-08-21 19:48:58 +08:00
README.i18n.yaml Merge remote-tracking branch 'origin/master' into codex/localized-chinese-doc-links 2026-08-20 19:15:33 +08:00
README.md feat(authorization): obtain a credential by asking the human 2026-08-20 17:58:38 +08:00
README.zh.md Merge remote-tracking branch 'origin/master' into codex/localized-chinese-doc-links 2026-08-20 19:15:33 +08:00

credentials/ — credentials and authorization

English | 中文

The credential capability family separates reference resolution from its provider, and separates both from obtaining a credential that has to be asked for:

Package Role ctx key
credentials/ Credential-reference and credential-record seam ctx.credentials
credentials-local/ Environment and local-file provider registers ctx.credentials
authorization/ Plugin-owned flows that obtain a credential by asking a human ctx.authorization

Configuration carries references, not secret values. Consumers resolve those references at their operation boundary; the child READMEs own mutation, precedence, and storage semantics. An authorization flow writes a credential record and is keyed by it, so the two seams meet at the record and nowhere else.

The subsystem reference — CredentialRef, per-operation resolution, UI-safe CredentialInfo, provider layers — is docs/subsystems/credentials.md.