H
pending
Claude Cowork Works Alone. Rowboat Spaces Built the Version Where Your Assistant Talks to Your Teammate's
Grounded / Real
Inflated / Uruttu
Original Content
Anthropic just got outplayed again.
Devs built the multiplayer assistant Anthropic couldn't, and open-sourced it.
Claude Cowork is a solo desktop agent. You point it at a folder, give it a task, and it works through your local files on your own machine.
The moment a teammate enters the picture, it has nothing to offer.
Most real work does not happen alone.
A teammate asks for a status update on something you own. The context they need is scattered across your meetings, your notes, and decisions made last week.
Typing all of that out takes time you do not have.
This is the gap Claude Cowork was never designed to cross.
Rowboat Spaces is built on a different model entirely.
Each person brings their own assistant into a shared channel.
Your assistant is your second brain. It knows your meetings, your notes, and your open decisions. That personal context stays yours.
When a teammate asks a question in the channel, you ask your assistant to brief them. It pulls from everything you know and delivers the answer on your behalf, attributed to you.
Your teammate's assistant does the same, from their own context.
Teams can draft specs, track decisions, and update shared files from plain conversation.
Each assistant reads the full channel history, cross references it against what exists, and flags what is missing.
The whole thing is open-source, and each assistant acts as the person it belongs to, not as a shared bot pulling from a common pool.
The video below shows this in action.
I joined a shared space and asked my team member for a status update. My team member asked their second brain to answer. A spec got built from that conversation, versioned, with every change tracked back to the message that triggered it.
Devs built the multiplayer assistant Anthropic couldn't, and open-sourced it.
Claude Cowork is a solo desktop agent. You point it at a folder, give it a task, and it works through your local files on your own machine.
The moment a teammate enters the picture, it has nothing to offer.
Most real work does not happen alone.
A teammate asks for a status update on something you own. The context they need is scattered across your meetings, your notes, and decisions made last week.
Typing all of that out takes time you do not have.
This is the gap Claude Cowork was never designed to cross.
Rowboat Spaces is built on a different model entirely.
Each person brings their own assistant into a shared channel.
Your assistant is your second brain. It knows your meetings, your notes, and your open decisions. That personal context stays yours.
When a teammate asks a question in the channel, you ask your assistant to brief them. It pulls from everything you know and delivers the answer on your behalf, attributed to you.
Your teammate's assistant does the same, from their own context.
Teams can draft specs, track decisions, and update shared files from plain conversation.
Each assistant reads the full channel history, cross references it against what exists, and flags what is missing.
The whole thing is open-source, and each assistant acts as the person it belongs to, not as a shared bot pulling from a common pool.
The video below shows this in action.
I joined a shared space and asked my team member for a status update. My team member asked their second brain to answer. A spec got built from that conversation, versioned, with every change tracked back to the message that triggered it.
Validated Content
@rowboat in a Space has your assistant pull from your own context and post the answer back attributed to you (shown literally as "You (via Rowboat)" in their materials) — matching the post's "attributed to you" claim closely.