Launch HN: Rowboat (YC S24) – Open-source IDE for multi-agent systems (github.com)

66 points by segmenta ↗ HN
Hi HN! We are Arjun, Ramnique, and Akhilesh, the founders of Rowboat (https://www.rowboatlabs.com), an AI-assisted IDE for building and managing multi-agent systems with a copilot. Using Rowboat, you can build both deterministic automation agents (e.g. automatically summarizing emails) and more agentic systems (e.g. a meeting prep assistant or a customer support bot).

Here are some examples:

- Meeting-prep assistant: https://www.youtube.com/watch?v=KZTP4xZM2DY

- Customer support assistant: https://www.youtube.com/watch?v=Xfo-OfgOl8w

- Gmail and Reddit assistant: https://www.youtube.com/watch?v=6r7P4Vlcn2g

Rowboat is open-source (https://github.com/rowboatlabs/rowboat) and has a growing community. We first launched it on Show HN a few months ago (https://news.ycombinator.com/item?id=43763967).

Today we are launching a major update along with a cloud offering. We’ve added built-in tool integrations for 100s of tools like Gmail, Github and Slack, RAG with documents and URLs, and triggers to invoke your assistant based on external events.

Our cloud version includes all the features of the open-source IDE, but runs instantly with no setup or API keys. For launch, we're offering $10 free usage with Gemini models so you can start building right away for free without adding any card details. Paid plans start at $20/month and give you access to additional models (OpenAI, Anthropic, Gemini, with more coming) and higher usage limits.

There’s a growing view that some tasks are better handled by single agents (https://news.ycombinator.com/item?id=45096962), while others benefit from multi-agent systems for higher accuracy ( https://www.anthropic.com/engineering/multi-agent-research-s...). The difference often comes down to scope: a focused task like coding suits a single agent, but juggling multiple domains such as email, Slack, and LinkedIn is better split across agents. Multi-agent systems also help avoid context pollution, since LLMs lose focus when asked to handle unrelated tasks. In addition, cleanly dividing responsibilities makes each agent easier to test, debug, and improve.

However, splitting work into multiple agents and getting their prompts right is challenging. OpenAI and others have published patterns that work well for different scenarios (https://cdn.openai.com/business-guides-and-resources/a-pract...). We’ve added agent abstractions, built on top of OpenAI’s Agents SDK, to support these patterns. These include user-facing agents that can decide to hand off to another agent when needed; task agents that perform internal tasks; and pipelines that deterministically call a sequence of agents.

Rowboat’s copilot (‘Skipper’) is aware of these patterns and has been seeded with tested patterns, such as a manager‑worker setup for a customer support bot, a pipeline for automated document summarization, and multi‑agent workflows for combining web search with RAG. It can:

- Build multi-agent systems from a high-level request and decide how work must be delegated across agents

- Edit agent instructions to make correct tool calls using Com...

10 comments

[ 4.4 ms ] story [ 29.3 ms ] thread
Looks very similar to relevance ai. How should we think about this product’s difference other than oss
why would I use this over n8n?
Who is your ideal customer and what could they create?

What is the plan if, like Jetbrains have recently experienced, customer usage exceeds the $20?

I want to create something that every X hours (could be 6 hours, 8 hours, 12 hours) check if there are news about a certain topic, and if there are and are interesting enough, generate an image, a text, and post it to Instagram.

The second part is done (generating it and posting it), but finding the news is the hardest part, even if I share some RSS feed. Would this help me with my use case or is something completely different?

What is the core use case here? For example instead of adopting a dedicated customer support chatbot, why should someone build one on Rowboat? As far as I can see, the customisability parameters are not that different
Not sure if this came through in the post, but with Rowboat we’re taking a strong stance: flowchart-style agent builders are useful today, but we believe they won’t scale with how LLMs are evolving.

As models get better at reasoning, you shouldn’t need to manually draw structured paths. It should feel more like onboarding a new teammate - you give high-level goals, and context, and they figure out the details. We don’t give flowcharts to teammates because it’s a lot of overhead to specify everything upfront. We think agentic systems are heading the same way. Flowcharts are helpful in some cases, but not how we’ll build long-lived assistants.

How do you build trust in a system like that? The flowchart style have the advantage that you can decide when you want a human to review/approve as well as ensuring actions that need to happen at certain conditions do happen.
(comment deleted)
Why are you giving this product a theme of a computer game?

You are a business facing startup, act like one.

The current UI[1] made me feel the target market are my elementary school kids.

[1] https://imgur.com/a/NMxz150