This looks great, but let's see if I have this right ...
The "Agent Apps" (or whatever we are calling them) from the big vendors are organized around projects/folders, and we attach apps (via plugins) to the projects.
This appears to mae the apps (work surfaces) the primary artifact?
Surfaces are the primary artifact for collaborating with the assistant - each one attaches an app to a workflow and gives both you and the agent a structured place to work, instead of everything flowing through chat.
Chat is still first class, and projects/folders exist separately to organize work around it.
This is neat, excited to try it. Over the last months I’ve been exclusively using Codex for non-coding tasks. It’s not bad, but there’s much to improve. This seems like a step in the right direction!
Fair point. But our goal with Rowboat is to do the opposite, to distill down only the parts you care about. For instance, you are not expected to read meeting notes, the important parts from it are added to your knowledge graph. That way next time you want to know something like 'where are we on x', you can find exactly that without having to wade through irrelevant information to get there.
This looks great, but let's see if I have this right ...
The "Agent Apps" (or whatever we are calling them) from the big vendors are organized around projects/folders, and we attach apps (via plugins) to the projects.
This appears to mae the apps (work surfaces) the primary artifact?
Yes, that's mostly right.
Surfaces are the primary artifact for collaborating with the assistant - each one attaches an app to a workflow and gives both you and the agent a structured place to work, instead of everything flowing through chat.
Chat is still first class, and projects/folders exist separately to organize work around it.
Really cool, how long did something like this take to build?
This is neat, excited to try it. Over the last months I’ve been exclusively using Codex for non-coding tasks. It’s not bad, but there’s much to improve. This seems like a step in the right direction!
Thanks! Would love to hear what you think, after you get a chance to try it.
love this. will try this out.
Thanks, would love your feedback after trying it.
The growing problem with this and many other AI offerings is the asymmetry of effort.
All of them take my notes, meeting transcripts, jira tickets, code, websites, and give me more to read.
Then everyone else in the org is doing the same, to give me more to read. At the end of the day there is too much to read.
AI is supposed to be reducing toil, but it's just making more.
Fair point. But our goal with Rowboat is to do the opposite, to distill down only the parts you care about. For instance, you are not expected to read meeting notes, the important parts from it are added to your knowledge graph. That way next time you want to know something like 'where are we on x', you can find exactly that without having to wade through irrelevant information to get there.
Have you tried having AI read it for you? /s
The AI should be doing the reading, then deciding what to do, then doing it, right? While you are at the beach, or unemployed. That's what Sam says.
I would like to be on the beach. But seems like people are working more and not less with AI. Somebody needs to care enough.