Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Herdr: One terminal to rule them all

herdr.dev

Post reply on HN
Print view View original

21–30 of 189 posts

Re: Herdr: One terminal to rule them all

#21

Post by spudlyo »

jonfw wrote: post #18
spudlyo wrote: post #8

So I've tried to figure out why you might want to use this over Tmux, and essentially I think it comes to down to: - 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 &…

Mobile support?

The example I saw of "mobile support" was connecting via a mobile terminal emulator. I don't see how that is any different than using tmux with the same mobile terminal emulator.

Re: Herdr: One terminal to rule them all

#23

Post by tim-projects »

dagss wrote: post #6

Is there git worktree support? 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 lookin…

I haven't been able to use worktrees because when there are major conflicts I find the ai can't handle it. Often it ends up dropping a lot of code.

How do you manage that? How do you successfully navigate complex merges using ai?

Re: Herdr: One terminal to rule them all

#24

Post by codybontecou »

spudlyo wrote: post #21
jonfw wrote: post #18

Earlier quoted context omitted.

Mobile support?

The example I saw of "mobile support" was connecting via a mobile terminal emulator. I don't see how that is any different than using tmux with the same mobile terminal emulator.

The clickable areas work on mobile as well - at least using supported clients like Moshi

Re: Herdr: One terminal to rule them all

#26

Post by dagss »

dv_dt wrote: post #9
dagss wrote: post #6

Is there git worktree support? 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 lookin…

what is the advantage of git worktree vs using a git remote set to a local file upstream.

As the sibling comments note, this is kind of off-topic to my post.

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

Re: Herdr: One terminal to rule them all

#27

Post by dools »

dagss wrote: post #6

Is there git worktree support? 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 lookin…

I use this bash script that creates tmux windows and panes in a worktree and then undoes the process:

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.

Re: Herdr: One terminal to rule them all

#29

Post by obmelvin »

graypegg wrote: post #22

> Popular with engineers from... (bunch of logos) > Individual engineers, not company endorsements. Bold haha. Maybe that's fine with the disclaimer, but feels like lawyer-bait.

I've seen a lot of companies list logos if just a single engineer or team is using the product.

Re: Herdr: One terminal to rule them all

#30

Post by dools »

tim-projects wrote: post #23
dagss wrote: post #6

Is there git worktree support? 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 lookin…

I haven't been able to use worktrees because when there are major conflicts I find the ai can't handle it. Often it ends up dropping a lot of code. How do you manage that? How do you successfully navigate complex merges using ai?

I always rebase the worktree back to the source branch before merging, and resolve conflicts on the branch. I have a resolve conflicts skill and just say:

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.

Post reply on HN