akhisud

4 ms·

1. 1.▲
   by akhisud 1y ago

   Our ideal users are developers and product teams who want to automate everyday workflows for themselves and their users. Examples include meeting prep, daily/weekly reporting, project management, GitHub repo management, and customer su
2. 2.▲
   by akhisud 1y ago

   From our experience, n8n is great for linear workflows and connecting APIs through flowcharts. Rowboat is aimed at building agentic systems (multiple orchestration patterns, autonomous agents coordinating, non-linear decision making). Those
3. 3.▲
   by akhisud 1y ago

   Thanks for the pointer! We briefly checked them out. Looks like they use a flowchart-style canvas - that’s great for certain types of automations. Rowboat is especially designed for agentic patterns (e.g. manager-worker) which lend more aut
4. 4.▲
   by akhisud 1y ago

   Haha not yet, but we're planning to make the copilot a Rowboat multi-agent system!
5. 5.▲
   by akhisud 1y ago

   Thanks! 1. That's right - Rowboat's agent instructions are currently written in structured prompt blocks, and a lot of logic does live there (with @mentions for tools, other agents, and reusable prompts). We support oAI GPTs at th
6. 6.▲
   by akhisud 1y ago

   1. A2A is on our roadmap (still exploring), for agents built on Rowboat to communicate with external agents. I assume that's what you mean as well. 2. Rowboat agents are technically stateless in that they do not store any messages and