A few small downsides: I can't copy/paste in wezterm using the keyboard/vim keys because it is constantly drawing the screen and unselects my selection. The mouse drag in herdr works very well though. It'd also be nice if you could rebind key mappings in the UI, because I still haven't rebound the keys and am using the mouse.
So I will start a workspace for each different thing I'm working on, label it "Studio Shed Packet", "Teapot game", "Mux experiment". Then in each one I run a Claude Code. Then I can see the status of my Claude Codes just by glancing at the sidebar, rather than having to switch between screens to see what is waiting next.
I've been using it around a week so far.
With the long waits for agents to do stuff I really don't see how one can get anything done without multitasking with multiple worktrees in parallel. So I'd want support for listing the worktrees and then have a list of agents within each worktree.
Emdash and Nimbalyst have this kind of UI. Unfortunately both of them want to manage the state of each worktree group themselves; I'm looking for something that just would just call git worktree directly so that I can switch more seamlessly between CLI and IDE/TUI..
But I think git worktrees are a bit more ergonomic, I don't have to think about local vs upstream there's just one place to push.
I like to organize my projects like this:
myproject/.repo/git # bare repository .. my own convention..
myproject/main # worktrees from ../.repo/git
myproject/feature1
myproject/feature2- everything is mouse clickable
- tmux style display-popups are used for friendly UI interactions everywhere
- it has a UI for agents running in panes, with a cool status (idle/working) display
- has opinionated defaults like automatic clipboard copy on mouse text select
- makes nested sessions easier & has default affordances for remote SSH attach
- is generally prettier
- uses display-popups for notifications
Otherwise it seems exactly like tmux.
Doesn't tmux and zellij do all of these things that 'herdr' does?
How does one describe what's happening with stuff like this? Where a business tries to intercept people who are still learning the lay of some land, to get them to pay for something that they just haven't learned yet can be essentially free to them? Is there a word for it?
I do separation of concerns with the agent orchestrator (Nemesis8): https://github.com/deepbluedynamics/nemesis8. That can be run with or without Hyperia. I do not suggest anyone run agents on their bare metal. Putting them in a container gets a lot of wins, especially around log aggregation. Working now on a Splunk/Loggly-like interface for searching logs, tool runs (useful in tuning a custom local MoE drafter) and full session suspend, stop, detach, and search. It also does single MCP tool installs for all agents. Nemesis also supports dynamic port exposure to the host metal, for testing agent builds inside their containers.
Hyperia has a lot of extra features as well that I have found personally useful:
- Sticky notes (search too) - addressable panes in addressable tabs, tabs in windows, multiple windows - full ACLs across panes, notes, tabs, windows - Poke-a-pane to keep an agent going (any agent, not just CC which has a timer function) - webpanes with markdown extraction, JavaScript injection - directory pickers for people who find cd'ing to things confusing or those weary of typing nearly the same directory path over and over again in new terminals (not perfect, but I'm iterating on it) - a built in agent loop (in the Rust sidecar) that allows using local models for tool calls (needs a trained drafter to make it viable) or using a local model for token maxxing (compresses reads of panes by frontier models) - pane splits down/up/left/right and quick layouts.
As for whether it was "vibe coded" or not, or Herdr for that matter, I don't think that term is useful, other than for quick judgment. No, this is not a one-prompt project. I've spent 100s of hours on it, started out with Hyper, and did a crazy amount of planning on how to architect it. I have done systems architecture for a living before, and have a strong search background. People who hate on AI, and therfore projects done with AI, are threatened. Nothing more. That's why they shortcut with "AI slop" or "Vibecoded. Nope". That's just ignorance speaking from a standpoint of fear.
Slop, whether AI or human, is an effort problem: https://deepbluedynamics.com/blog/ai-slop-effort-problem. Looking at Herdr, it looks solid. Judge the product by it's outcomes, it's use, not whether or not AI wrote it or not. That's the moment we're in though, for now, so downvote or not. I don't care.
> Popular with engineers from... (bunch of logos)
> Individual engineers, not company endorsements.
How do you manage that? How do you successfully navigate complex merges using ai?
echo “resolve conflicts” | runpi
Where runpi is my pi -p wrapper. I’ve never had a regression from it, but it gives me a report at the end so I can double check the decisions if I need to.
The skill is basically don’t use automatic resolvers, err on the side of including both sides, refer to recent commits, missions and runfiles for context and in your report to me use real branch names not HEAD and incoming because I can never remember what those refer to.
But I do have many years of experience working in a larger team and it's the same problem there (just that people want to merge after some days of working).
I'm not sure if AI changes the picture much vs working in a team.
Either way one has to plan ahead a bit and select tasks that are not going to trample on each other. I can typically imagine roughly what the code generated is going to be (at least what files will likely be involved in what way) and when selecting tasks to work on I take into account if it's going to likely cause conflicts.
https://gist.github.com/iaindooley/cc8a61a1ff0fe23526c850906...
You include a script .worktree in your repo that does any copying or symlinking to setup the target directory.
It also has a headless mode so that it does the worktree operations without the tmux which I use for executing pi -p prompts in worktrees.
ori_b•56m ago
andhug•14m ago