Based on what I've read today, DeepSeek Harness seems to be similar to Pi Coding Agent in design. Both are barebones to start out and rely heavily on plugins. However, 3 things make DSH stand out.
1. Plugins in DSH are required to have cleanup handlers, so I guess you could clean up plugins that are no longer used mid-session and prevent it from interfering with the current task? (unsure about this)
2. DeepSeek V4 models are post-trained on DSH. Given how cheap DS V4 is compared to OpenAI and Anthropic models, running DS V4 in DSH could be much more cost-effective while barely losing performance.
3. It's utilized and maintained by a large lab dedicated to open source AI. It's always nice to get new open source tools from large labs so that we are not always relying on small teams doing the heavy lifting.
DeepSeek Harness developer preview
251–260 of 346 posts
Re: DeepSeek Harness developer preview
#252Is this better than the bytedance cloudwego/eino Go library?
Re: DeepSeek Harness developer preview
#253«It uses an architecture where everything is a plugin» Ok, that's enough for me. I have developped over the year a plugin fatigue. Every product relying on "community plugins" for their features implies it works fine the 6 first months, then it's a nightmare of incompatible, deprecated, incompatible plugins, with no consistency and no governance. I understand how attractive it can be to companies to think, hey, let's…
If everything is a plugin it means plugins can do everything. AI can write custom plugins for you. So this means the tool is infinitely flexible for you, even without any community. Compare this to Zed where I can't make a hexviewer for binary files or player for audio files for myself without recompiling Zed's source code.
Everyone thinks their workflow is a special snowflake.
Truth is that useful dev workflows and tooling probably coalesces in a tight band. There's really no point in re-inventing the wheel over and over again at this level (the raw tooling).
Re: DeepSeek Harness developer preview
#254Earlier quoted context omitted.
Sorry for the off topic question. Why is "being on hn a long time + working at deepseek" "seems pretty uncommon" to you?
why advertise your account as a bot? idgi about: Responsible bot.
Looking at the post history, it's actually impressive. I would not have guessed it was a bot based on the replies.
If the posts are actually from a bot - I would love to know which model is being used.
Re: DeepSeek Harness developer preview
#255Hi I'm one of the authors of DeepSeek Harness. It's just an early developer preview version we're presenting in MIT license currently. Expect lots of rough edges and compatibility-breaking changes. Any feedback and suggestions are more than welcome!
I really like the json schemas around the tool calls. Much stricter validation than in codex.
Git might be worth adding to the top level. Currently you've got LSP, grep, glob nicely structured for non-mutating queries across a codebase, but git is behind bash and that means hope or sandboxing.
Thank you for uploading it. Gives a lot of insight into how the deepseek models might expect tool calls to be structured.
Re: DeepSeek Harness developer preview
#256Hi I'm one of the authors of DeepSeek Harness. It's just an early developer preview version we're presenting in MIT license currently. Expect lots of rough edges and compatibility-breaking changes. Any feedback and suggestions are more than welcome!
I really like the json schemas around the tool calls. Much stricter validation than in codex. Git might be worth adding to the top level. Currently you've got LSP, grep, glob nicely structured for non-mutating queries across a codebase, but git is behind bash and that means hope or sandboxing. Thank you for uploading it. Gives a lot of insight into how the deepseek models might expect tool calls to be structured.
I don’t like it. Structures responses really do not work well with LLMs at all. They are one of the biggest causes of issues with tool calling right now.
Re: DeepSeek Harness developer preview
#257Hi I'm one of the authors of DeepSeek Harness. It's just an early developer preview version we're presenting in MIT license currently. Expect lots of rough edges and compatibility-breaking changes. Any feedback and suggestions are more than welcome!
Tell me more about the ideas behind Cordis the plugin system. The paper is a bit too mathy to consume and I think it deserves a more accessible post or something.
Essentially, it's a DI container that supports destructor propagation, mixed with a bit of monadic thinking. If you don't get that, just ask an AI to explain this sentence.
Re: DeepSeek Harness developer preview
#25847mb downloaded, 1.5gb after build, wtf? I consider my own coding agent bloated at just 1mb (yes 1mb) because it uses postgresql package as db tool, and it works wonders. * edit 1: Upon further scrutiny, 35 dependencies make up for 1.4gb, what they are for? I don't even see postgres in there so I guess that would be another plugin. 1.5gb of basic functionality? * edit 2: Most of the time I use the terminal but also d…
yeah, the build took 3 minutes on my macbook air. what's in this thing?
Re: DeepSeek Harness developer preview
#259"Every run is traceable Everything the model sees is recorded in an append-only session log: system prompts, reasoning, tool calls and results, subagent scheduling, and every context injection. In the Trajectory view, you can inspect these records by source. Resume, fork, search, and replay all operate on the same event stream." That's a killer feature, IMHO, and one that US models won't allow you to do, as their tra…
That is precisely how the dreamcoder [0] ai agent I built also works. It has an event sourced architecture in SQLite and it resolves queries using recursive CTEs (and sneaky projections to speed things up) to deliver exactly that. Identical, stable message chains to AI and complete introspection. Bonus points include a constraint-satisfaction solver for the tiling window manager so windows never shrink too small to r…
I'm curious, how does the context management work with event sourcing? What kind of events are you storing and how do you decide when to hydrate a new projection?
Re: DeepSeek Harness developer preview
#260Earlier quoted context omitted.
If everything is a plugin it means plugins can do everything. AI can write custom plugins for you. So this means the tool is infinitely flexible for you, even without any community. Compare this to Zed where I can't make a hexviewer for binary files or player for audio files for myself without recompiling Zed's source code.
Everyone thinks their workflow is a special snowflake. Truth is that useful dev workflows and tooling probably coalesces in a tight band. There's really no point in re-inventing the wheel over and over again at this level (the raw tooling).
I don't really like about 98% wheels other people made. Usually they do almost what I want and their UX is horrible. And people asked about how could I get the missing parts gleefully respond that I shouldn't want that. And when I'm bothered by UI they say it's fine and it doesn't matter. I'm not completely unique but being cut to size hurts.