Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • There are so many agent orchestrator, and I can't use any of them (to full extent, at least) because each of them thinks Git is the only VCS on the planet.
    by kriomant
  • The obvious question -- which you should spend time answering -- is what does this give that Herdr doesn't have? What's the differentiator?
    by petesergeant
  • Love these threads for sharing experience. Using Orca has been a game changer (which I found and started using because I saw somebody using Conductor)

    These sorts of management tools really speed up development by automating all the PR management, such as making new worktrees, etc. and then super speed up the multitasking between different parallel feature development.

    Excited to see if this one works better for me, and to try all the new alternatives in these comments.

    by epistasis
  • One thing about these tools - and, as discussed, there are many - that they mostly seem to share is that they all show coding agents work as a transcript of a conversation.

    Why?

    The underlying conversation has nothing to do with the work. That there is one context window is an implementation detail.

    I've built one of these for myself, and instead it shares questions, plans, findings, assumptions as distinct UI elements. The conversation is hidden: your focus is on "what's next".

    Are there other meta-harnesses doing the same thing? I'd love to stop building my own and use a product someone else has already built!

    by phildenhoff
  • How's this different to https://paseo.sh/ or https://www.onorca.dev/ which seems to be more feature complete? I personally use and like Paseo. I get to connect to my LLM agents even on other machines, remotely via Tailscale and the mobile app UX is quite good.
    by mr-karan
  • We already have similar products, like Goose [0], Paseo [1], and T3 Code [2].

    [0]: https://goose.ai

    [1]:https://paseo.sh/

    [2]: https://t3.codes/

    by maxloh
  • All of the handful of tools in this space that I've tried have modeled an overlap/coupling between project, directory, and machine. For my workloads specifically I think these should be organized differently. Something like top-level projects that have child task/goal/sessions with each one fanning out to different agents running potentially in different worktrees, directories, and even on different machines. E.g. I have a lot of notes and other context stored locally. On a different machine I have repositories checked out and build tooling installed. Frontend and backend exist in different directories but can both be relevant to a given unit of delivery. Are there any agent orchestrators that can model things that way?
    by mbil
  • I built a website that compares 68 of these tools: https://agentmgmt.dev/

    Offrun is added.

    by manume

Explore Birbla archives