Can Rowboat do this? If not, does anybody know a harness that can?
Can Rowboat do this? If not, does anybody know a harness that can?
That's what Amp is built around!
By default conversations are shares in your team (you can also make them private), and the agent has access to them.
So you can do things like "how would $teammate think about this" and the agent will read your colleague's conversations with Amp to get a feel for that and evaluate your work based on that.
Or just figuring out what everyone is doing at the moment is much easier that way
What they do have is funding and distribution, but that's the same advantage every incumbent has against every startup.
The single biggest advantage we have is that the labs are tied to their ecosystems. Claude still doesn't have image generation; Gemini-flash-lite is the best cheap model, but Gemini's apps can't use the latest models from Anthropic or OpenAI. We can always use the best tool for each job.
Your end users literally do not care what model you use behind the scenes or if you're using "the right tool for the job".
> Claude still doesn't have image generation
What? It has for years. Go ask it right now.
On the labs: agreed that end users don't care about the model - only that the job gets done well, which is our argument too. At any point some model is best at a given job, so any single lab is behind for a portion of time on a portion of tasks.
Also different members of the team could steer/approve what the AI did or did not do.
Ahhh found the talk: https://www.youtube.com/watch?v=ClWD8OEYgp8
Didn't really consider putting it out in public. Is there a viable product out of this? How much would you pay.
https://zed.dev/docs/collaboration/overview
Not sure if the agent stuff is shared in the "channels", though.
I get that great pains have been made to make sure that doesn't happen by default. But if you really want to co-op on something, why not at the session level on a dedicated VM/login pair?
That's why we're exploring a peer-to-peer setup for group chats instead. Each person keeps their own machine and data, and the assistant knows who's who and can ask the primary user for permission if the secondary user wants to run something non-trivial.
Or you could use tmux and a shared login and any tui agent harness.
Obviously they would be very flawed but a place to start.