131–140 of 148 posts
One thing I don't understand with all of these, is how they're handling different worktree infrastructure spin-up? For example, if I have a webapp, I want each of the worktrees to spin up its own infrastructure, and be accessible on its own unique local url, so that I can see the changes locally for each worktree, or I can have agents automate visual checks using something like agent-browser. Currently I use docker f…
i have created a simple setup script that reserves a couple of ports per workspace/worktree. with that, each ticket/workspace can starts it's own webserver. Allowing me to work on multiple things in parallel. that also allows me to use Claude+Chrome MCP to e2e test each implementation in parallel.
Besides my own repo I also have a couple open source repos open. so I can quickly ask Claude questions about it instead of looking at the docs, which are usually outdated.
All in all, I usually have ~5 workspace/tickets/agents running at the same time. And one as Q&A agents per OSS repo
Earlier quoted context omitted.
Could you elaborate a little on what you are doing with 40-50 agents? I use Claude, I've employed sub-agents, but I still can't wrap my head around how people are using them to that extent.
ha, I didn't mean they are all running at the same time. sorry if it sounded like this. I open a new worktree/agent session for each new feature or bugfix. Usually I start with ideation and brainstorming before doing the actual implementation. However my priorities shift daily, so I could be starting a feature on monday, but then stop during the ideation already, pick up another task on tuesday and won't go back to t…
I always feel like I want to use something like this, but then realize my NeoVim setup + tmux + Ghostty is good enough and I am not ready to learn a whole another system for modest gains. The friction I have currently is obviously things like port forwarding, in app browser etc. I keep thinking to try out cmux but haven't gotten around to it.
Why Mac only? Also - one issue I've seen with other tools doing worktree stuff is they don't deal with merge conflicts automatically. IMO the agents should just automatically resolve conflicts & rebase on their own, is that a thing here?
And on the worktree note, I find when working in a worktree the agent has a much easier time solving merge conflicts and as the number of feature branches scale and it just makes it so i dont have to worry about conflicts while working on a feature.
Earlier quoted context omitted.
Note that Anthropic specifically called out that usage through Conductor will be metered as "programmatic usage" in their June 15th pricing change: https://news.ycombinator.com/item?id=48126438
My colleagues are planning to get around this by using Conductor's big terminal mode. At which point I think it's basically just a git worktree manager?
Earlier quoted context omitted.
definitely understand the perspective. I feel like theres some dev work that completely requires me to be single threaded and just think hard, but there other modes where i can jump into whack-a-mole mode and try to work on a bunch of github issues in parallel, or sentry issues, or little ui bugs and the thinking goes more into reviewing plans and prs and i dont have to be as attentive to each individual session
There are individual tasks that can be “swarmed”. Constructing software requires supervision and a continuous feedback loop from a discerning human.
I like this app, but 40 year old me says I will buy it for onetime payment rather than 20 dollars monthly. Great app