HN user

jpeeler

395 karma

[ my public key: https://keybase.io/jpeeler; my proof: https://keybase.io/jpeeler/sigs/BmMn6aWo8TQKz19Bky8ooRYd7JavTFI6ISfEdVKKUNw ]

Posts5
Comments179
View on HN

Good question, anybody know? I've seen harnesses optimize for token efficiency (maki), simultaneous agent operations (jcode), extensibility (pi), etc... But I have no idea if each focus area is superior and if the rest of the operations are comparable.

It bothers me that the Claude Code leak (from what I read, didn't look) a few months ago showed a lot of careful consideration for context handling. I assume this means that each harness performance/correctness would differ drastically just from this alone.

The kitty developer is philosophically against multiplexers, but he also has concern about performance (which I share somewhat as well). Herde is not quite as fully featured as zellij/tmux, so that partially is biasing me. I think that a native app could be potentially nicer to avoid all those concerns, along with my setup (only in Linux really) of a tiling manager handling the windowing instead of that being part of the solution. A big part of the value add of Herde is actually the monitoring of the Claude session and not so much the multiplexing reimplementation. One of my patches allows jumping to the next blocked/finished session so I can quickly give feedback or observe different agents. I can envision a GUI solution for that workflow being something better than what a terminal easily allows.

I'm currently using herde[1] to handle/supervise multiple agents (with some patches I need to try to upstream) along with Nono[2] for sandboxing. This sandboxing approach avoids use of a microVM, which lets me use tooling I already have installed inside the sandbox. The downside is getting all the policies correct as it seems every project needs some new type of access, though Nono does try to make policy writing easy.

I've been considering switching my approach to using a microVM through microsandbox[3]. The pro of this approach is you can essentially skip the policies and rely on the security of the VM boundary. The negative is that now you've lost all your installed tools, so you need to either provision at runtime or build something (like an image) beforehand to match your dev environment.

I still don't know which is less maintenance. And while I think herde is pretty well thought out, I do think about something that works outside the terminal may be nicer.

[1] https://github.com/ogulcancelik/herdr

[2] https://github.com/always-further/nono

[3] https://github.com/superradcompany/microsandbox

Before GitHub 3 months ago

I was hoping that by now we would have an up and coming DVCS replacement that functioned as a "github in a box" (pretty sure fossil has been described as that, but it's too much on the cathedral side). Being able to mirror an entire project though version control would significantly help with mirroring if we go back to a decentralized world. Maybe going back to decentralized project hosting is just another pendulum swing similar to how compute moved to the cloud...

I work in a monorepo at work, which of course increases complexity and build time due to more work being done. But I keep wondering even with better CI options that properly handle dependencies if solving the problem at that level is too low.

Currently evaluating using moonrepo.dev to attempt to efficiently build our code. What I've noticed is (aside from Bazel) it seems a lot of monorepo tools only support a subset of languages nicely. So it's hard to evaluate fairly as language support limits one's options. I found https://monorepo.tools to be helpful in learning about a lot of projects I didn't know about.

Yes, appreciate this.

I noticed that with both models voxtral-mini-transcribe-realtime-2602 and voxtral-mini-2602 filler words are ignored. I'd like to be able to count words/sounds, specifically "um" or "uh" for improvement purposes. Any good models that handle that?

I'm embarrassed to say this is the first time I've heard about sandbox-exec (macOS), though I am familiar with bubblewrap (Linux). Edit: And I see now that technically it's deprecated, but people still continue to use sandbox-exec even still today.

Wouldn't you have the same problem with changing workspaces? Sounds like you can't keep track of anything not currently present on the screen, which before the overview was a lot harder to deal with. One thing that could help is to create a "temporary terminal" keybinding to launch in floating mode so you'll never forget to close it. Or create a focus-or-launch bind that switches to an existing terminal (tools like Nirius can help minimize scripting). The other thing that may help is adjusting your struts so you can see that windows exist to the left or the right. More of general workflow tip than one related to just terminals.

Netflix needs to do a Black Mirror episode where either a sentient AI pretends that it's "dumber" than it is while secretly plotting to overthrow humanity. Either that or a LLM is hacked by deep state actors that provides similar manipulated advice.

Same, I never remember them either. However, I use a shell (fish) that has decent command history autocompletion that helps a lot for such things.

I wish the flags between ripgrep and fd lined up as I think that's what confuses me (can't remember now haha).