Tianyi Cui
356453d6cb
Adapter schemas now carry only credential references, but the Models join, onboarding readiness, shipped overlays, SDK scaffolding, fixtures, and active decision prose still treated a redacted literal apiKey as a supported compatibility state. That residue made an unsupported field look contractual and pinned Schemastery silent-dropping as behavior. Delete those branches and examples, and let compositions and scaffolds use adapter-owned reference and environment resolution. Do not add a tombstone validator or change generic unknown-key behavior: literal adapter credentials have no migration contract to preserve.
Examples
English | 中文
Runnable demonstrations of the main DeepSeek Harness interfaces and extension points. Each child directory owns its configuration, prerequisites, commands, and detailed behavior.
mcp-memory
Optional overlays that connect supported third-party memory servers through the generic MCP client. See the memory example reference.
headless-agent
A non-interactive agent that accepts one task, runs it, and emits a selected machine-readable or human-readable output format. See the headless example reference.
jsonrpc-agent
An unattended coding agent driven through the Python SDK and JSON-RPC. See the JSON-RPC example reference.
web-cordis
A self-referential agent that can inspect and change its in-memory Cordis plugin tree. See the web-cordis example reference.
acp-agent
An Agent Client Protocol automation server for programmatic clients, with session, permission, and cancellation support. See the ACP example reference.