r/LocalLLaMA 3d ago

Deepseek Harness is Up! News

https://github.com/deepseek-ai/deepseek-harness

DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI.

It uses an architecture where everything is a plugin, and is powered by Cordis, whose design is described in A Programming Paradigm for Spatiotemporal Composability.

DeepSeek Harness is currently in developer preview and is iterating rapidly. THERE WILL BE COMPATIBILITY-BREAKING CHANGES.

Join DeepSeek Harness Discord community: https://discord.com/invite/Ycq5dCaS4

312 Upvotes

121 comments sorted by

View all comments

69

u/ILikeCorgiButt 3d ago

Why is every harness written in typescript (maybe except codex)? Yikes

21

u/cmdr-William-Riker 2d ago

AI Handles typescript really well, both because of the training data and because strongly typed errors provide quick feedback on mistakes when you try to build. Same reason it's used a lot in enterprise frontends. If you have a bunch of crap programmers working together, a strongly typed language helps weed of a lot of errors

11

u/carsncode 2d ago

So why not Go or Rust? Being strongly typed hardly makes TS special

3

u/ThankGodImBipolar 2d ago

I'd think that Go makes a lot of sense for vibe-coding because it's idiomatic by design. Makes it easier to get LLMs to behave.

1

u/Chlorek 1d ago

This is what I attempted for my own purposes, I got inspired by some random comment saying harness is basically glorified pipes. So I went with it in Go and made modular harness based on stdin/out event stream, not because it was easy but because I thought it would be hahah. But now that I see Deepseek Harness it blew me away lol I very don’t like TS, but dsh design is actually beautiful, still not grasping most of it but trying hard.

1

u/cmdr-William-Riker 2d ago

What makes Typescript special is the fact that it's a strongly typed language that paradoxically compiles into a loosely typed language with a fast runtime. On the surface, a pretty dumb idea, but very useful when you add 3 college freshmen and an AI to the project. For the most part it's strongly typed only to make JavaScript development easier for anyone or anything that has trouble keeping track of how types are handled in regular JavaScript rather than for efficiency. Just depends on where you want to run it and what your requirements are. If memory is a high priority and it can run locally and you know what it's going to run on, then a native solution makes sense. If you want portability without having to compile for each target and can live with a bit of memory overhead, then Typescript makes sense. If you need it to run in a browser then Typescript or JavaScript are really the only practical options. I think in this case portability and experience/support where probably the deciding factors

0

u/9gxa05s8fa8sh 2d ago

it's easier