Live data from Hacker News

DeepSeek Harness developer preview

deepseek.com

101–110 of 346 posts

Re: DeepSeek Harness developer preview

#101
I just installed DeepSeek Harness with the latest Bun version and am using it with a local 9B, speculative decoding Qwen 3.x variant, running in llama.cpp and it works GREAT for small python projects, so far.

It was very easy to connect the harness to the local model and it seems to run quite fast, compared to other harnesses that I have tried.

Re: DeepSeek Harness developer preview

#102
post #11

Is there a reason why so many of these agent harness are written in node.js?

1. it's built for async 2. runs everywhere 3. interpreted, making it fast to iterate on 4. decent performance 5. most popular language, llms are decent at writing it

decent performance, lol! compared to what? a shell script? "i'll only take up 200MB of disk and 4GB of RAM to output flickering text on a terminal. boy this is high performance"

fast iteration is for POCs. once you have the app built and working, you need performance and stability much more than fast iteration

Re: DeepSeek Harness developer preview

#103

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

Most vendors that create a plugin-based system end up creating a large library of plugins to kickstart the ecosystem, which many users end up trusting those more because they're "official", so they essentially created an mono-vendor ecosystem with extra steps.

Re: DeepSeek Harness developer preview

#104

«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.

Re: DeepSeek Harness developer preview

#105
post #93

Earlier quoted context omitted.

New coding harness that seems to have some novel concepts and one of the pretty cool things on their landing page for it here: https://deepseek.com/harness/en/ is the Every Run is Traceable view: "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…

I promise this isn't meant to be snarky, but is that not just...logs?

It's only logging if an obsolete human does it.

But the future is here and thus it's called "Agentic causality's reified temporal traceability."

Re: DeepSeek Harness developer preview

#106
post #24

Earlier quoted context omitted.

Probably for the ease of coding extensions — which strikes me as outdated thinking: if it’s open source and you’re outsourcing the coding to LLMs, why not use a compiled, safe language? There’s an interesting counter example for DeepSeek called CodeWhale, though: https://github.com/Hmbown/CodeWhale

Also isn't OpenAI's Codex written in Rust?

I don’t think so. The ChatGPT app was, which is the “Classic” app now. The Codex app that they’re carrying forward is an Electron app and if you forget to quit it before you walk away it’ll make even your M5 Max unresponsive eventually. Sad days.

Re: DeepSeek Harness developer preview

#107
post #95

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

Sounds like a Linux architecture, innit?

Many of the libraries and executables in Linux are cross-compilable with other ecosystems. It's the difference between opening the door to an existing ecosystem and birthing one.

Re: DeepSeek Harness developer preview

#108
post #58

I have read the underlying paper, and found it may be useful, but not that useful. For those who want to know what it achieves: it adds hot-reload and dynamic enable/dispose capabilities to a plugin system, like the one in Pi agents, though they push the boundaries further, to the UI components and so on. For those who want to know what it does: if you have some PLT knowledge, ask your agent to explain the algebra to…

The paper mentions agent harness self improvement as one of the use cases. I don't know what's the advantage vs. iterating over a monolithic harness.

Re: DeepSeek Harness developer preview

#109
post #106

Earlier quoted context omitted.

Also isn't OpenAI's Codex written in Rust?

I don’t think so. The ChatGPT app was, which is the “Classic” app now. The Codex app that they’re carrying forward is an Electron app and if you forget to quit it before you walk away it’ll make even your M5 Max unresponsive eventually. Sad days.

Sorry, I meant the Codex CLI harness. I don't understand why OpenAI decided to start using the "Codex" name for everything.

Re: DeepSeek Harness developer preview

#110
post #58

I have read the underlying paper, and found it may be useful, but not that useful. For those who want to know what it achieves: it adds hot-reload and dynamic enable/dispose capabilities to a plugin system, like the one in Pi agents, though they push the boundaries further, to the UI components and so on. For those who want to know what it does: if you have some PLT knowledge, ask your agent to explain the algebra to…

> it adds hot-reload and dynamic enable/dispose capabilities to a plugin system, like the one in Pi agents, though they push the boundaries further, to the UI components and so on.

That actually sounds amazing.

Post reply on HN