DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH
DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH
DeepSeek just released Harness, multiple steps improvement in coding agents, instead of releasing one hard-coded agent $DSH treats many of the components that make an agent useful as plugins.. that means developers can build, replace and compose capabilities instead of waiting for DeepSeek to implement the features they need everything in $DSH is literally a plugin
https://t.co/za7SV0bZul
CA: EQbtWcRQ8R6uZvgvaoAEEchRJJTdm1p2nuDNCht7pump
https://t.co/DCIbryfic3
DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH
DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH
DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH
or just buy solid teks
DeepSeek just released Harness, multiple steps improvement in coding agents, instead of releasing one hard-coded agent $DSH treats many of the components that make an agent useful as plugins.. that means developers can build, replace and compose capabilities instead of waiting for DeepSeek to implement the features they need everything in $DSH is literally a plugin
https://t.co/za7SV0bZul
CA: EQbtWcRQ8R6uZvgvaoAEEchRJJTdm1p2nuDNCht7pump
https://t.co/DCIbryfic3
DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH
DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH
@jscrypto4882 gm @jscrypto4882 there's this gem ct is super slow to catch up to $DSH
CA: EQbtWcRQ8R6uZvgvaoAEEchRJJTdm1p2nuDNCht7pump
https://t.co/cviZS6D1P7
DeepSeek just released something interesting
It’s called DeepSeek Harness (DSH), and the important part isn’t just what it can do out of the box.
It’s the architecture.
The easiest way to understand it is:
Model → Harness → Plugins
The model provides the reasoning.
The Harness gives that reasoning an environment to actually operate in: file editing, shell execution, search, planning, subagents, workflows, sessions, permissions and more.
And underneath it is Cordis, the plugin runtime that makes the system composable.
Instead of building one giant, hard-coded agent, DSH treats many of the components that make an agent useful as plugins.
That means developers can build, replace and compose capabilities instead of waiting for the core agent to implement everything.
The Harness comes with several runtime modes:
Standard Mode: the full coding-agent experience with tools, planning, skills, subagents and workflows.
Code Mode: lets the model orchestrate tool operations through generated TypeScript, making complex multi-step tool use programmable.
Minimal Mode: strips the agent down to persistent Bash + a file editor.
Creator Mode: exposes the runtime for experimenting with plugins and creating custom agent presets.
The session architecture is another interesting piece.
DSH records the agent's execution as an append-only trajectory: reasoning, tool calls, tool results, subagent activity and context changes.
Sessions can then be resumed, forked, searched and replayed.
So an agent run isn't just a chat that disappears when you're done. It's an inspectable execution history.
And the ecosystem is already being built around this.
DeepSeek has a "dsh-plugin" ecosystem where developers can create additional capabilities for the Harness.
It can also work with other providers and custom OpenAI-compatible endpoints, so the Harness isn't simply a UI wrapped around one DeepSeek model.
The bigger picture is what makes this interesting:
The model is the brain.
The Harness is the body.
Plugins are the extensibility layer.
DeepSeek isn't just giving developers another agent to use.
They're giving developers an environment for building custom agents.
It's still a developer preview and the architecture is evolving There's no runner for it yet so I'm deploying $DSH