segmenta

7 ms·

1. 91.▲
   by segmenta 1y ago

   To add to this, we strongly believe that a flowchart type builder quickly hits the ceiling on the type of assistants you could build with it. And this has do with the fact that many real world tasks don't have a well defined flow to th
2. 92.▲
   by segmenta 1y ago

   In theory you could express most things as a flowchart but the complexity of doing that quickly escalates. A customer support bot that goes beyond informational answers might be a good example for something that is hard to express in a flow
3. 93.▲
   by segmenta 1y ago

   Would love to know how you find Rowboat for this!
4. 94.▲
   by segmenta 1y ago

   Ah that is unexpected. Do you mind hopping on our discord: https://discord.com/invite/rxB8pzHxaS - we can debug this for you.
5. 95.▲
   by segmenta 1y ago

   Great question. Rowboat is a non-opinionated agent framework, so you can build support bots but also meeting prep, reporting, repo management, and other daily automations in the same place. Even for support, it's more flexible: compani
6. 96.▲
   by segmenta 1y ago

   This is great, and exactly the type of thing we would love folks to build on Rowboat! Rowboat has tools to search the web, find HN posts, browse Reddit etc, and you can ask the copilot to build an agent to filter posts based on topics - at
7. 97.▲
   Launch HN: Rowboat (YC S24) – Open-source IDE for multi-agent systems(github.com)

   66 points by segmenta 1y ago|28 comments
8. 98.▲
   by segmenta 1y ago

   Curious - what was the use case you were trying out?
9. 99.▲
   by segmenta 1y ago

   Agree that the microservices analogy is great for the maintainability aspect of multi-agents. However, there is one more dimension which is specific to LLMs - performance. Smaller agents tend to have better instruction-following accuracy.
10. 100.▲
    by segmenta 1y ago

    Glad you like the mascot! Thanks, curious to learn your feedback once you try it.
11. 101.▲
    by segmenta 1y ago

    Thanks for the pointer. We do agree that not all agentic systems should be multi-agent. Having said that, from our experience we see that for complex workflows e.g. customer support for enterprises, both quality and maintainability stands t
12. 102.▲
    by segmenta 1y ago

    Fair point. The copilot creates multi-agents only when necessary, acting as a check on unnecessary complexity.
13. 103.▲
    by segmenta 1y ago

    That’s a great suggestion, and I get the hesitation - we'll work on adding more concrete examples to help make the case!
14. 104.▲
    by segmenta 1y ago

    Here are a few practical reasons for multi-agent systems: 1. LLMs handle narrower, simpler instructions better - decomposing into multiple agents improves reliability (related to instruction following accuracy). 2. Similarly, tool-calling a
15. 105.▲
    by segmenta 1y ago

    Haha, thanks!
16. 106.▲
    by segmenta 1y ago

    Thanks for checking it out. Curious what you think after testing.
17. 107.▲
    by segmenta 1y ago

    Fair point. Increasingly the workflow for multi-agent systems involves structured agent instructions (almost resembling code), testing, connecting tools and improving agents. Given this we decided to call it an IDE.
18. 108.▲
    by segmenta 1y ago

    Thanks! We wanted to have the copilot planning and building out agents be a core part of Rowboat (like how Cursor works with code).
19. 109.▲
    by segmenta 1y ago

    TBH we weren't sure if people preferred a native app or a web app for this kind of tool. This is useful feedback! We are trying to figure out how to bundle the micro-services together into maybe an electron app.
20. 110.▲
    by segmenta 1y ago

    Thanks, that's great to hear! We'd love to learn what worked and what didn't for you.
21. 111.▲
    by segmenta 1y ago

    Thanks! We will put it out on our website.
22. 112.▲
    Show HN: Rowboat – Open-source IDE for multi-agent systems(github.com)

    161 points by segmenta 1y ago|51 comments