Cordis
The underlying runtime framework of DeepSeek Harness, designed specifically for AI agent scenarios. Its name derives from the Latin word for 'heart.' Cordis provides three core capabilities: reversible effects, reactive coordination, and real-time reconfiguration, supporting zero-downtime hot-swapping of plugins.
Core Facts
Timeline (last 90 days)
In Cordis, the pending state typically indicates that a service declared via inject has not yet appeared; when a service provider disappears, plugins that depend on it are first unloaded and then reloaded after the service recovers
In Cordis, each loaded instance has a fiber state that transitions among pending, loading, active, unloading, and disposed, and may also enter a failed state
Cordis is a general-purpose dependency injection and plugin container framework that matured in the Koishi ecosystem and was later adopted by DeepSeek Harness as its underlying runtime
The underlying layer of the Harness is handled by Cordis, which is responsible for loading dependencies, managing lifecycles, and reclaiming resources
Cordis's effect mechanism enables listeners, tool registrations, timers, connections, and child plugins to be automatically cleaned up upon unloading; hot reloading tears down the old instance first and then reinstalls the new instance according to dependency relationships
The core mechanisms of Cordis include dependency injection, lifecycle management, and the service locator pattern.
The core idea of the Cordis framework is 'reversible actions'—every operation has a corresponding inverse operation, achieving both temporal composability and spatial composability.
Creator mode lets the AI invoke the Cordis plugin development SDK during a conversation to generate plugin code, which is injected into the runtime after user confirmation and can be persisted, achieving 'prompt-to-deploy'.
The Cordis framework is derived from a same-named service-container library in the JavaScript ecosystem, originally used for the chatbot framework Koishi.
The underlying layer of DeepSeek Harness is powered by Cordis for shared context, which is responsible for service contributions, typed events, and reversible side effects
13 more timeline events
All Facts (20)
DeepSeek Harness is built on a framework called Cordis, constructed around spatiotemporal composability.
65%UnverifiedThe Cordis framework is derived from a same-named service-container library in the JavaScript ecosystem, originally used for the chatbot framework Koishi.
70%UnverifiedThe underlying layer of DeepSeek Harness is powered by Cordis for shared context, which is responsible for service contributions, typed events, and reversible side effects
70%UnverifiedIn Cordis, each loaded instance has a fiber state that transitions among pending, loading, active, unloading, and disposed, and may also enter a failed state
50%UnverifiedThe underlying layer of the Harness is handled by Cordis, which is responsible for loading dependencies, managing lifecycles, and reclaiming resources
50%UnverifiedCordis is a general-purpose dependency injection and plugin container framework that matured in the Koishi ecosystem and was later adopted by DeepSeek Harness as its underlying runtime
50%UnverifiedCordis's effect mechanism enables listeners, tool registrations, timers, connections, and child plugins to be automatically cleaned up upon unloading; hot reloading tears down the old instance first and then reinstalls the new instance according to dependency relationships
50%UnverifiedIn Cordis, the pending state typically indicates that a service declared via inject has not yet appeared; when a service provider disappears, plugins that depend on it are first unloaded and then reloaded after the service recovers
50%UnverifiedThe core mechanisms of Cordis include dependency injection, lifecycle management, and the service locator pattern.
50%UnverifiedCreator mode lets the AI invoke the Cordis plugin development SDK during a conversation to generate plugin code, which is injected into the runtime after user confirmation and can be persisted, achieving 'prompt-to-deploy'.
50%UnverifiedThe core idea of the Cordis framework is 'reversible actions'—every operation has a corresponding inverse operation, achieving both temporal composability and spatial composability.
50%UnverifiedDeepSeek Harness's framework is named Cordis and provides three capabilities: automatic cleanup, dependency reactivity, and live reconfiguration (supporting hot module replacement, HMR).
50%UnverifiedCordis possesses "spatiotemporal composability," meaning plugins can be freely assembled along the spatial dimension and can also be dynamically loaded and unloaded at runtime without restarting the process.
50%UnverifiedCordis is an Inversion of Control (IoC) container and plugin management framework for the JavaScript/TypeScript ecosystem, originally validated at scale within the Koishi chatbot framework.
50%UnverifiedThe Harness framework is built on top of the Cordis plugin system; the framework itself is only responsible for plugin loading and dependency management, and all functional components are pluggable Cordis plugins.
50%UnverifiedThe Cordis framework provides three core capabilities: Reversible Effects, Reactive Synergy, and Live Reconfiguration.
50%UnverifiedCordis's Live Reconfiguration capability supports Hot Module Replacement.
50%UnverifiedHarness目前的插件开关需要通过配置文件手动实现，在profiles/web目录下的cordis-patch.yaml文件中添加插件id并设置isDisabled为true
50%UnverifiedHarness使用的Cordis配置系统基于依赖注入和响应式编程理念，允许通过声明式配置管理组件间依赖关系
50%UnverifiedDSH 的核心组件 Cordis 是一种基于依赖注入和事件驱动的插件化框架，倡导「万物皆插件」理念
50%