news.ycombinator.com

Untitled

tianyicui · 0 points · 0 comments · há 19 horas

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!

Comments

5 preview comments · loading full thread
juliushá 2 horas

The best kept secret in AI training. Tianyi, since you are our insider. When you walk by the training teams office - how often do you see Pelicans on their screens?

big_toasthá 18 horas

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

krautsourcedhá 14 horas

By MIT currently, do you mean it will eventually change to a different OSS license, or it may become a closed source product? That latter would be rather sad...

JonChesterfieldhá 11 horas

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.

cnxhkhá 13 horas

Hey Tianyi, one question is that do you think in the future harness would become more simpler and its behavior should match a guideline or we would add more complexities to make it more robust? Is it important to use the same harness for RL and inference?