Now this is what I'm talking about — this checks all the boxes for me.
I was looking at "Agent builders" for a while now and nothing really stood out. They all seemed to use a "node" type structure, while I was looking to tell something what I need using natural language.
The only thing that came close was Vessium, but I never heard back after adding myself to the waiting list weeks ago. I also wasn’t so hot about their questions either — "Are you cool with paying for a product just to try it," or something to that effect. I’ll admit though, I said yes. =)
Either way, congrats on the launch and wishing you much success.
I will test it out. I am mildly skeptical about the use case, but that may be today's experience of current project's PM not knowing anything about background of the project they are managing, which immediately makes me realize the limitations of all similar systems.
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 state between turns. Our HTTP API [0] requires previous messages and state to be explicitly passed from the previous turn to the next turn. For now, the state is pretty simple - just the name of the last agent that responded to the user. This allows the system to start off directly from where the previous agent left off. The Python SDK [1] manages the state for you. Does that make sense?
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.
Just to add more details here - currently the dashboard is a Next.js app, but the agents runtime (and Copilot) are Python apps since they're using the OpenAI agents sdk. We're trying to figure out the best way to bundle these into a single native app.
Yes, I know. And an IDE by any acceptable definition needs a text editor.
An integrated development environment (IDE) is a software application that provides comprehensive facilities for software development. An IDE normally consists of at least a source-code editor, build automation tools, and a debugger.
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.
Now this is what I'm talking about — this checks all the boxes for me.
I was looking at "Agent builders" for a while now and nothing really stood out. They all seemed to use a "node" type structure, while I was looking to tell something what I need using natural language.
The only thing that came close was Vessium, but I never heard back after adding myself to the waiting list weeks ago. I also wasn’t so hot about their questions either — "Are you cool with paying for a product just to try it," or something to that effect. I’ll admit though, I said yes. =)
Either way, congrats on the launch and wishing you much success.
Thanks! We wanted to have the copilot planning and building out agents be a core part of Rowboat (like how Cursor works with code).
I will test it out. I am mildly skeptical about the use case, but that may be today's experience of current project's PM not knowing anything about background of the project they are managing, which immediately makes me realize the limitations of all similar systems.
Thanks for checking it out. Curious what you think after testing.
This sounds really really nice. Potentially exactly what I've been hoping would exist. Thank you for putting it out there!
Will try it out over the weekend. Exciting stuff.
Thanks, that's great to hear! We'd love to learn what worked and what didn't for you.
1. Are you going to support Google's A2A protocol?
2. Are you going to support stateless chat?
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 state between turns. Our HTTP API [0] requires previous messages and state to be explicitly passed from the previous turn to the next turn. For now, the state is pretty simple - just the name of the last agent that responded to the user. This allows the system to start off directly from where the previous agent left off. The Python SDK [1] manages the state for you. Does that make sense?
[0] API docs - https://docs.rowboatlabs.com/using_the_api/
[1] SDK docs - https://docs.rowboatlabs.com/using_the_sdk/
It would be awesome if this could be wrapped around a native app rather than another webapp. Otherwise, great job!
Why do you want to shove a web app into a native window?
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.
Just to add more details here - currently the dashboard is a Next.js app, but the agents runtime (and Copilot) are Python apps since they're using the OpenAI agents sdk. We're trying to figure out the best way to bundle these into a single native app.
You could use tauri and use the native webview of the particular os
We'll check this out, thanks!
Web is native
Congratulations on the launch. Suggest adding the demo video right in the landing page. That is the first thing I would be looking for. IMO.
Thanks! We will put it out on our website.
Your rowing mascot is cute.
Haha, thanks!
I'm happy it is not another VSCode fork. But isn't this missing a text editor to be called a proper IDE?
IDE just stands for Integrated Development Environment, so something that doesn't edit text could still be an IDE
Yes, I know. And an IDE by any acceptable definition needs a text editor.
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.