Skip to content

Community

Cordis composition kernel powering DeepSeek Harness plugins

  • Load & unload
  • Service wiring
  • Composable plugins

Treat every community package as software you might need to reverse. Lab in Creative, document disposers, and keep Cordis upstream bookmarked beside deepseek-harness.

  • cordiverse/cordis upstream
  • Disposers required
  • Creative for labs

Cordis

Kernel

github.com/cordiverse/cordis

Load

Lifecycle

Register → wire → dispose

Creative

Lab mode

Inspect wiring safely

Guide

Authors

Plugin checklist on-site

Why DeepSeek Harness talks about Cordis

If every tool lived inside a single binary, “everything is a plugin” would be marketing. Cordis makes registration and disposal first-class, which is how skins, providers, and tools coexist without forever monkey-patching a monolith. Upstream project: github.com/cordiverse/cordis.

DSH architecture describes how services and session state sit on that kernel. This page stays focused on composability habits: load what you need, unload what you do not, and never stack twenty topic hits onto Standard on day one. Spatiotemporal composability means a plugin arrives with a lifecycle — register, wire dependencies, dispose — so Creative labs can inspect wiring without pretending the session is production.

Prefer the curated directory for rewritten cards; use the dsh-plugin topic when you need breadth — and still check maintainers. Authors: the plugin guide expects honest docs about secrets, filesystem scope, and uninstall steps. Operators who only want a running UI can skim this spoke after install and return when a community package misbehaves.

Why Cordis habits matter

Unload must be boring

If you cannot reverse an add, you do not control the session. Disposers are not optional polish.

Dependencies are first-class

Cordis wires services; broken dependency graphs feel like “random” tool failures.

Creative is the lab

Official materials describe Creative for runtime inspection and in-memory experiments — [modes](/en/modes/).

Publish as dsh-plugin

Ship a separate package with the topic tag rather than stuffing demos into core — [contribute](/en/contribute/).

Operate Cordis-aware

  1. 1

    Stabilize core DSH

    Install via [install](/en/install/), confirm Web UI, keep modes careful.

  2. 2

    Read architecture + guide

    Map services on [architecture](/en/dsh/architecture/); follow [plugin guide](/en/plugins/guide/) for add/remove.

  3. 3

    Lab in Creative

    Use [modes](/en/modes/) Creative on a disposable folder. Do not point at Friday’s deploy tree.

  4. 4

    Document before Standard

    When an experiment works, write uninstall steps, then consider curated listing via [contribute](/en/contribute/).

Go deeper

Spatiotemporal composition framework and plugin service model underneath DSH.

Load, unload, and dependency discipline

Stacking firehose topic hits onto Standard is how previews feel haunted. Start from curated cards on plugins/directory. When a dependency graph breaks, tool failures look random — unload last-added packages first, then check process health on troubleshoot. Document filesystem scope before you recommend a package to teammates.

Creative mode as a lab

Author presets and skins in Creative; promote to Standard only when unload is documented. Product entry: overview. Chapter walkthroughs for operators: tutorials. Never point Creative at Friday’s deploy folder or a tree that holds payroll secrets.

Cordis vs Agent Loop

Cordis composes plugins; the Agent Loop drives tool calls. They collaborate — neither replaces the other. See architecture for the runtime map and github when you need to read how DSH mounts Cordis in source.

Practical next steps

Operators keep Creative isolated and add packages one at a time. Authors read Cordis upstream plus the plugin guide before tagging dsh-plugin. Hub: DSH resources. Site FAQ: FAQ. Package identity if launch fails: npm. Web UI checklist: web-ui-guide.

FAQ

Is Cordis part of DeepSeek Harness or separate?

Cordis is its own project used as the composition kernel. Follow github.com/cordiverse/cordis for Cordis APIs; DSH specifics stay in deepseek-harness and the architecture map.

Which mode is safest for Cordis experiments?

Creative, per modes, on a disposable workspace. Keep payroll repositories out of the lab.

Where do I learn to write a plugin?

Start with the plugin guide, then contribute for publish norms.

Does Cordis replace the Agent Loop?

No. Cordis composes plugins; the Agent Loop drives tool calls. See architecture.

Is this Cordis page DeepSeek product HQ?

No. harness-ds.com rewrites operator guidance. Cordis lives at cordiverse; DSH product framing is on deepseek.com/harness — FAQ.

Composability only helps if unload is boring. Lab in Creative, publish with the plugin guide, and keep Cordis upstream bookmarked beside deepseek-harness.

From Cordis to practice

Read architecture, follow the plugin guide, or return to the DSH overview after you grasp the kernel.