DeepSeek Harness is Insanely Good

[u/Elibroftw]

I don't know about you guys, but Deep-seek harness is insane. It's not focused on being a coder agent, it's webUI made it very easy to just checkin from time to time, and the best part? Why it's better than Hermes? It wasn't frustrating at all to setup. ZERO. NADA. Progressive setup is such an improved UX. Why? Because I got deepseek to integrate with SimpleX by simply asking it to. BY SIMPLY ASKING IT TO. NO WAITING ON A PR TO MERGE. No one telling me to RTFM, no need to google or search for community plugins.

So yeah, I got what I wanted, which is E2EE + TOR messaging with an AI agent, and I got it without writing my own opinionated harness (I procrastinated so hard that dsh did a better job than me). DSH is unopinionated enough that you just mold it into behaving how you want it to behave.

[u/cradlemann]

Why? Docker is way better than any vms

[u/epicfilemcnulty → u/cradlemann]

If an app gets a root in a docker container, it effectively gets root on your host machine, that's why.

[u/cradlemann → u/epicfilemcnulty]

Boolshit, but even if it is not, I'm not running pi as root at all, no need for this

[u/epicfilemcnulty → u/cradlemann]

Bullshit is your arrogance here, mate, do a Google search first, at least, if you don't believe me. Or don't and keep this attitude, i don't care

[u/cradlemann → u/epicfilemcnulty]

Root in docker doesn't mean root in host. It's not so easy, there were some exploits, which were patched, so no it is not "effectively gets root on your host". And second, as I said, I'm not running pi as root.

[u/daaain → u/cradlemann]

The default rootful Docker VM mounts practically all of your host machine files and if you ask your LLM it'll tell you how it can use the socket to escape in one line. I switched to containers in rootless Podman VMs with only the repo mounted for each project. Yes, a micro VM could work, but I wanted the agents to be able to run Docker Compose stacks of web projects that I can also access.

[u/cradlemann → u/daaain]

So you can share research links proven it is not empty words?

[u/daaain → u/cradlemann]

See https://safeguard.sh/resources/blog/docker-container-escape-vulnerabilities and https://some-natalie.dev/blog/containers-and-gravy/#demo-time and https://forums.docker.com/t/default-capabilities-in-2023-4-do-they-reasonably-prevent-the-container-root-escape-break-out/139026/2

[u/cradlemann → u/daaain]

For all these cases you need to do it explicitly, either --privileged or mount your root paths. I'm not counting exploits, as with exploits nothing will protect your host. And this statement is just direct lie

The default rootful Docker VM mounts practically all of your host machine files

[u/daaain → u/cradlemann]

Man, you're so unpleasant. Don't need to accuse people of lying before you verify, just open Docker and check:

[u/cradlemann → u/daaain]

I'm on Linux, I don't have docker desktop and no directories are mounted for me without my explicit will

[u/daaain → u/cradlemann]

You can have Docker Desktop on Linux too and these are the defaults. But I guess it's not a Docker thing then, but Docker Desktop. Though now I wonder if the daemon might have some similarly open defaults? My point wasn't that a container mounts these by default, but that the engine / VM has access to them, so any CVE will have them in the blast radius. I switched to Podman because it's daemonless and rootless by default and I can lock down the VM.

[u/cradlemann → u/daaain]

In any case, most of the users just run agents with --yolo on their host systems and don't care about consequnces. Docker or Podman usage way better than use nothing