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

271–280 of 346 posts

Re: DeepSeek Harness developer preview

#271

Post by Sha1rholder »

big_toast wrote: post #248
Sha1rholder wrote: post #226

Earlier 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?

Not exactly sure why that wouldn't be the default assumption. It's a pretty small subset afaict. Seems like size 1 before 2024 from a brief search. Presumably more people there have read hn at least some. But there's perspective having seen the ebb and flow of hn/the rest of the ecosystem for the last 16 years and how that intersects with deepseek culture. It's clear openai culture is influenced by yc culture, which…

It *is* a small subset, but I don’t see what’s so surprising. HN is just an ordinary tech community; it’s not surprising for people from any tech company to show up there.

Re: DeepSeek Harness developer preview

#272

Post by Sha1rholder »

grimgrin wrote: post #244
Sha1rholder wrote: post #226

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

I (a primate) have been using this About for six years. Miss the days when no one had any doubts about this statement.

Re: DeepSeek Harness developer preview

#273

Post by tw1984 »

not very impressed.

in the era of AI, telling me that the core design is a plugin system that can be reloaded and extended easily is just not exciting.

it is something you feel excited 20 years ago back in the 2000s, in 2026, the expectation is agentic capabilities and self improving.

Re: DeepSeek Harness developer preview

#274

Post by gagan2020 »

root_axis wrote: post #230
gagan2020 wrote: post #181

I was working on same idea but left in between and thank god they did it. Why I left that idea is because as a developer I know that was needed but I have limited time so I need to build that is really next path forward. I am working on whole dev space that can run on my Mac M4 or similar specs. I needed to revamp everything (LLM thinking) from ground up even models. My idea is mixing deterministic nature of existing…

> My idea is mixing deterministic nature of existing tooling (non-LLM tooling) with non-deterministic nature of LLMs. This is the fundamental idea behind every LLM harness.

LLM harness is making tools work with LLMs. My idea is making LLM work with tooling. Creating LLMs to work with tooling. By this process, LLM can be made smaller & efficient as well.

Re: DeepSeek Harness developer preview

#275

Post by partyficial »

KyleJune wrote: post #242
anramon wrote: post #236

Earlier quoted context omitted.

AI slop reply.

I figured it'd be funny to invert it and reply like an LLM to a human since they were arguing he was talking to them like they were an LLM.

it was funny. and it's a matter of pride that they accused you of being AI.

Re: DeepSeek Harness developer preview

#276

Post by throwaway7783 »

prettyblocks wrote: post #100
invaliduser wrote: post #89

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

This works pretty well for these coding harnesses though (see Pi). I like the model where the harness ships with minimal tools and you can spin up plugins for extra functionality. You can usually have the model/harness you're using just create the plugin that you need for you. The advantage of this is that these harnesses aren't optimized for their frontier models like claude/codex are so you can fine tune your envir…

Also a very nice attack surface.

Re: DeepSeek Harness developer preview

#278

Post by roywiggins »

shostack wrote: post #265
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…

Could memories and blocks of context be made pluggable and unpluggable in this manner to "hot swap" context?

Not without nuking your cache, I figure.

Re: DeepSeek Harness developer preview

#279

Post by hankbond »

lalitmaganti wrote: post #118
lxdlam wrote: 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…

This is basically similar to what bb ( https://getbb.app/ ) is also doing. It's interesting to see many different people exploring things in this space...

certainly a time of great convergence. I set out to build a very similar thing both to build my own agent applications but also to learn more about how to build extensible software.

Re: DeepSeek Harness developer preview

#280

Post by slashdave »

m_ke wrote: post #11
syntaxing wrote: post #5

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

> it's built for async

You do know that node is event driven, right?

Post reply on HN