Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DeepSeek Harness developer preview

deepseek.com

Post reply on HN
Print view View original

191–200 of 346 posts

Re: DeepSeek Harness developer preview

#191

Post by purav0788 »

vhantz wrote: post #143

There is such a clear lack of innovation drive in this field. Every lab just copies what the other does. One of the most baffling things to me is how the once-upon-a-time good developer instinct to make everything reusable, testable, and deterministic is just getting lost into a sea of markdown begging a language model to please act a certain way. For example this repository has a "skill" definition that consists in…

They built the whole thing in 2 months with 2 developers. They are not gonna think about every feature with any reasonable thought/effort behind it.

Re: DeepSeek Harness developer preview

#192

Post by ef2k »

What's buried under the lede: this harness is using Cordis v4 (the paper that dropped today). Cordis has already been used for four years in a different project called Koishi that uses v3. Cordis itself is a way of hot loading and unloading plugins without restarting a running process. The cool part is that when it unloads it can revert any state and side effects it created, cleaning up its connections, memory allocations, registered handlers, etc. and it can also deactivate any dependencies it relied on without disturbing other plugins.

Re: DeepSeek Harness developer preview

#193

Post by ziofill »

ef2k wrote: post #192

What's buried under the lede: this harness is using Cordis v4 (the paper that dropped today). Cordis has already been used for four years in a different project called Koishi that uses v3. Cordis itself is a way of hot loading and unloading plugins without restarting a running process. The cool part is that when it unloads it can revert any state and side effects it created, cleaning up its connections, memory alloca…

Sounds very cool! What do you mean by “revert side effects it created”?

Re: DeepSeek Harness developer preview

#194

Post by [deleted] »

ef2k wrote: post #192

What's buried under the lede: this harness is using Cordis v4 (the paper that dropped today). Cordis has already been used for four years in a different project called Koishi that uses v3. Cordis itself is a way of hot loading and unloading plugins without restarting a running process. The cool part is that when it unloads it can revert any state and side effects it created, cleaning up its connections, memory alloca…

[deleted]

Re: DeepSeek Harness developer preview

#195

Post by iambenm »

vhantz wrote: post #143

There is such a clear lack of innovation drive in this field. Every lab just copies what the other does. One of the most baffling things to me is how the once-upon-a-time good developer instinct to make everything reusable, testable, and deterministic is just getting lost into a sea of markdown begging a language model to please act a certain way. For example this repository has a "skill" definition that consists in…

First, cloning a repo doesn't bring the hooks with it - so it's not just as simple as saying "use git hooks".

Second, if the repo had hooks and instructions for the LLM or user to blindly install/enable the hooks, we'd instead be complaining about security risks and what might happen if the repo is compromised at some point in the future.

Third, sometimes you don't want to mechanically enforce things via git hooks because it impacts your use when what you're really trying to codify and enforce are the LLM's actions. In that case you can enforce mechanically via hooks at the harness level.

And finally, git hooks are a great solution for upstream repositories to enforce quality and protect branches. But it means that the upstream is the one running the checks. It makes the upstream a potential bottleneck - better to have the leaf nodes run the checks locally and fix any issues before pushing it upstream rather than push upstream, wait for results, make changes, push upstream, wait for results, make changes.

Re: DeepSeek Harness developer preview

#196

Post by alansaber »

SwellJoe wrote: post #175

"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…

Agreed that it is a killer feature. US models obfuscate the COT (to A. make it look better and B. combat distillation) but > and the raw trace is fairly hard to reason about > but I still think this kind of feature is a big step in the right direction.

Re: DeepSeek Harness developer preview

#197

Post by ziofill »

derekdahmer wrote: post #182
culi wrote: post #170

Earlier quoted context omitted.

You're making demands (like you would to an llm) instead of asking questions (like you would to a human). The GP didn't even offer to answer questions

He explicitly asked for feedback

Exactly. “Tell me more about X” is an open ended question, not feedback.

Re: DeepSeek Harness developer preview

#198

Post by big_toast »

tianyicui wrote: post #119

Hi 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!

Sorry for the off topic question. You've been on hn a long time + work at deepseek which seems pretty uncommon. Anything you think hn doesn't know about deepseek that it should? Or any non-obvious ways hn/yc has influenced deepseek (or the broader ecosystem)?
Post reply on HN