herdrdev/herdr

This new GUI looks awesome, however it's not clear how to do the agent integration? With the TUI I installed the skill via `npx skills add https://github.com/herdrdev/herdr --skill herdr` and the agent knew what I was talking about when I said herdr, now I have to tell the agent 'Read `herdr-app --skill` and ...' - seems like extra steps?

I run a similar setup, just with different models. I also use herdr, which lets me have the same project worked on side by side by different models, each in its own git worktree. https://github.com/earendil-works/pi https://github.com/herdrdev/herdr

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

How does this compare to something like herdr which does all of this? https://github.com/herdrdev/herdr

…on. pi-tmux is one such example (seems to be archived now) which inspired me to use tmux as communication layer and provide visibility of subagents of multiple models in their native harnesses [1]. There's also herdr, which is not 0-stars, but is super interesting but lesser known project [2]. This also has interesting substrates to allow agent coordination. None of these are harnesses per se, but they're pointing towards clear gaps in existing harnesses. For example, we've known for a while now that compounding knowledge of different class of models achieves better performance. Why is there no harness where this is a native functionality? And there's no harness where subagents are first …