正在加载视频...

视频加载失败

We launched our Company Brain!! 🧠 onboarding is a context problem: your first weeks you're not working, you're reconstructing what the team already knows. company brain is that context, queryable and able to act. shared memory for your team, in slack: → answers from the company's own knowledge, grounded...

43,867 次观看 • 1 个月前 •via X (Twitter)

14 条评论

apoorv 的头像
apoorv1 个月前

super cooll

Ask GPTs 的头像
Ask GPTs1 个月前

Crazzy

Neelmani 的头像
Neelmani1 个月前

fire update ✨

Gregor 的头像
Gregor1 个月前

The context that disappears fastest is why the team ruled something out. Rejected paths leave no trace in Slack. I've gone back through old threads looking for that reasoning and it's just not there.

sha's 的头像
sha's1 个月前

Nice !

Kavin Prasath 的头像
Kavin Prasath1 个月前

Onboarding used to mean weeks of feeling lost—now it's just one question to a brain that actually remembers.

Money Bunny 的头像
Money Bunny1 个月前

saves weeks of onboarding confusion before new hires even ask their first question

Ankit Jain - Claude Anthropic Architect/ developer 的头像
Ankit Jain - Claude Anthropic Architect/ developer1 个月前

Autonomous Agents evolving.

pasandida(:)aura 的头像
pasandida(:)aura1 个月前

all supermemory fans and @DhravyaShah :))

✧ sofi ❀ 的头像
✧ sofi ❀1 个月前

Couldn't agree more

pasandida(:)aura 的头像
pasandida(:)aura1 个月前

check this as welll in content of @supermemory , actual usecase :))

Wei佳 的头像
Wei佳1 个月前

The permission graph is what makes this feel deployable, not just searchable.

Shekhaliya Kelis 的头像
Shekhaliya Kelis1 个月前

Intresting, let me try this

Milind Pandey 的头像
Milind Pandey1 个月前

a piece of feedback: a little slowed down speech tempo would be merrier to understand unless you have some clip time constraint. Btw loved the product and solicit deeper implementation clips for enterprises and bottlenecks if any.

相关视频

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. Rowboat GitHub: (don't forget to star 🌟) My co-founder also wrote a great article on building your second brain with Rowboat, and I highly recommend reading it as well. The article is quoted below.

Akshay 🚀

113,782 次观看 • 4 天前