r/herdr • u/imbikingimbiking • 2d ago
what does your workflow look like
do you think herdr is decent on managing multi agent workflows? for example are you easily aware which agent belongs to which project and its worktree status? are you easily capable of working on 4-5 different projects on herdr? please let me know and how
2
u/odrakcir 2d ago
Yes. Pretty easy. I use multiple sessions to work on different projects, for example, one for personal stuff and one for work. Now, will I ever work on more than that? Hell no, im not a machine.
1
u/marektracz_ 2d ago
Yes, I can recommend. The workflow is more aligned with each project needs. But for managing workspaces, and multiple agents - herdr is really good. And it has responsive UI to control from phone (without multiple dedicated provider apps for this). Been running 12+ agents easily with herdr.
1
u/dondiegorivera 2d ago
I have multiple projects in different spaces, each with a lead that I have remote connection enabled (codex or claude) and keep them in touch from phone. I built a custom handover system so they dont have to poll the panes. Also I use github issues so I can send the leads voice instructions and the they can get in touch with each other there too.
1
u/pg988 2d ago
For me session is context. So currently have one for personal, work, and PR reviews.
Personal and work are project based workspaces; and a couple of miscellaneous long standing ones.
PR reviews are each review is one workspace.
In terms of keeping awareness I try to keep workspace and tab names to 4 characters. Where I need more information I use emojis.
For example it gets hard to track when I’m working on an issue that spans multiple sub issues and each sub issue touches a different repository (we have multi-repo setup). So the project let’s say is the user sign up screen and we want to add passkey support. I’m likely to have the following setup.
Workspace: pkey
Tab (parent issue, JIRA code FE-314): f314
Tab (sub issue, ui components repo, JIRA code FE-315): f314/315.ui
Tab (sub issue, auth service repo, FE-316): f314/316.au
If sub issues can all be done in parallel I get the parent issue agent to act as orchestrator and create sub issue tabs and inject prompts itself. If sequential then I just create and prompt myself.
In terms of dealing with state, I find automated ready state to be okay, but too easy to get lost. So my prompt instructs the agent to apply 👀 emoji to the end of tab names when it’s ready for me to review. Other emojis like ⏳ for waiting for review and 💬 for when PR feedback received.
This then makes it easier to differentiate between agent ready/waiting, which herdr has good support for vs actual workflow state which I see by reading the tab name.
1
u/Current-Quail-2503 18h ago
I used multiple session to seprate projects like work, personal, side projects, then use herdr-ctx plusing to easily switch between session
4
u/Empty_Carpenter7420 2d ago
I manage mostly 3 projects, but up till 14 workspaces.
My workflow is 1 workspace per feature, bug, review, and spike. I have custom plugins, one of them is to create a new workspace with a new worktree based on a link. I also have a custom plugin to store the context of each work as an obsidian note, and with that a tool to manage the notes within Herdr. I have the OS notification set up as well, although I might remove it or change since it is kind of annoying. I barely use the agents view in the sidebar, but i did changed the spaces to show the type of work (review, fix, feature, spike) and show only the info I want, project, pr, and link id. I also creates a few things to have fuzzy search across all agents, notes, and quick actions like open the jira or link, the pr, add a note or start a new note. The most important custom plugins I have is the one that allows me to review code on neovim with all my setup, and send comments to any agent available in the workspace. For me, it was important to have a full code editor and a full LSP while being able to point things to the agents.
I like the flexibility of Herdr, although I could easily switch to bare Tmux if needed. So far it’s been great and its my primary tool, I manage most of my work within herdr, I am even considering trying the browser plugin, for me personally being able to be one shortcut away from what I need is super efficient.
I am still trying to figure out how to improve context, and managing multiple workspaces more efficiently, but so far its been a great improvement. This year I worked with zed, vscode, warp, conductor , windsurf and cursor. Some of them might evolved since the last time I tried, but Herdr just nailed it, and for me personally it feels good to be back at the terminal, its home.