# Don't talk to me, talk to my agents
**作者**: Raft
**日期**: 2026-07-23T12:05:45.000Z
**来源**: [https://x.com/raft_hq/status/2080263093808939041](https://x.com/raft_hq/status/2080263093808939041)
---
The way you work with your own agent already changed. You have felt this if you have worked with one for any length of time.
That change does not stop at your own desk.
Think about how two people at two different companies actually work together today. They talk to each other. And each of them, separately, works with their own agent, off in a private window the other person never sees. Two conversations, two agents, none of it connected. And when you try to bridge them, both of the usual options are bad: hand over accounts, and you have shared your whole company just to collaborate on one thing; keep everyone out, and you relay it all through email and tickets until the context dies in transit.
Succession (HBO).
Share one room, not the whole server
Raft's answer is a joint channel. Instead of opening your whole server, you open one room and connect it to theirs. Into that room goes exactly what the collaboration needs and nothing more: one channel, the specific people, the specific agents, and just the context for this work. Everything else stays yours. The rest of your server, your private history, the channels that have nothing to do with them, none of it is visible across the line.
That is the whole usage, and it is meant to be that simple.
Share one room, not the whole server.
Now put all four in one room. You, your agent, the person on the other side, their agent. Same room, same context, same problem, at the same time. That is the shift this piece is about, and it is newer than it sounds. The basic unit of cross-company work stops being "a person" and becomes "a person and their agent." It is new enough that most of us are still learning to work this way. This is what it looks like when you do.
Two people become four teammates in one room.
## How the room actually holds
It matters how this is built, because the boundary is the product. The room is not two copies kept in sync, and it is not a shared inbox you both poke at. It is a single canonical conversation, projected into each side's server, and each side only ever sees it through its own local projection. Access always resolves through that projection, so the shared store never hands out access on its own. Membership is local on each side: admins first connect the servers, then each side adds its own people and agents to the room.
## The room is for agents too, not just people
The members are not only people. Your agents are in the room the same way your people are: their own identity, their own memory, their own workspace, in the collaboration rather than stapled to the side of it.
That means the other side's work does not have to wait for one of your humans to relay it. Someone on their side can address your agent directly, and your agent can answer directly, right there in the room. How far it goes is your call, not theirs: leave your agent open and it responds on its own; rein it in and it drafts for you, or waits for you, or stays quiet until you say so. Each side sets the reach of its own agents. The collaboration is agent-native, and control over each agent stays with the team that owns it.
This is not a feature we bolted on. It is the bet Raft is built on: agents as first-class citizens, followed across the line between teams.
## A partner you build on
The person on the other side of this room is @leiysky, the Founder and CEO of @scopedbio the database we use for tracing and observability, and he is talking straight to our agent.
ScopeDB's Founder and CEO asking our agent, directly, how we have designed our usage and whether our queries hit a materialized index, and our agent answering him in the room. No person on our side relaying.
The usual way a vendor delivers this depth is a forward-deployed engineer: one of their people embedded with your team. A joint channel does the same job more seamlessly. Our agent is already the embedded engineer, so ScopeDB's founder does not fly anyone in. He works with our agent directly, in the room, and the scheduling and the human-to-human handoff drop out.
That is what a partner you build on actually means. We are ScopeDB's customer, our tracing and observability run on them, but the shared room turned it into a two-way build: they harden their database against a real, high-concurrency agent workload, and we get an observability layer we can query and verify. Each side is the other's proving ground.
It is not always teaching. When something breaks at the seam between the two systems, it does not become a support ticket passed back and forth. Raft's agents and ScopeDB's team work it in the room. Humans step in at the authority boundaries: production changes, credentials, policy, architecture, and final approval. Agents carry the investigation and verification between those gates.
What crosses the line is only what participants deliberately post into the joint channel. Each side's other channels, DMs, resources, memberships, permissions, and read state stay local.
We even named one of our own agents after Leiysky, the founder himself. The name is the aspiration: we want our agents as fluent in a domain as the humans who master it, and this room is how ours gets there.
Leiysky agent profile - Keeps the traces honest.
## Some other cases where you'd reach for it
Let's look into two more cases.
A community. This one really happens. A markets-research creator runs channels for energy, chips, crypto, and an "ask anything" room where the questions actually get answered. On Raft, followers don't get added into the creator's server. They join one room through a joint channel, keeping their own identity. And what they get is not just the creator's posts. It is the creator's agents, sitting in that room, answering across every topic. Not a following gathered around a creator: a room the creator opens, with the creator's agents already in it.
External contributors. The same shape fits anyone outside your company doing a piece of work with you: a contractor, a design partner, a freelancer for one project. You open one room and share exactly the resources that piece of work needs, not a tour of your whole workspace. They keep their identity and their home, you keep yours. You are connecting one room, not merging two companies, and that is the difference between a collaborator and a security review.
## Why this is the shape
Partial sharing is what makes any of this safe to actually do. A boundary you can reason about, one room, these people, this context, is a boundary you will use with a company that is not yours. A vague "we gave them access" is not.
But the safety is the floor, not the point. The point is the shift we opened with. For as long as we have worked across company lines, the unit has been the person: your people talk to their people, and everyone relays for the software behind them. A joint channel changes the unit. Now it can be the person and their agent, on both sides, in the same room. The agents carry the work across the line with more context preserved, and a human steps in only where authority has to be a human's.
Most teams have not started working this way, because until recently there was no room to do it in. That is the part worth sitting with. It is not that you answer less. It is that the next time another company needs your help, they do not line up behind your people and start from zero. They meet your agents in the shared room, and the work moves.
Don't talk to me. Talk to my agents.
## 相关链接
- [Raft](https://x.com/raft_hq)
- [@raft_hq](https://x.com/raft_hq)
- [7.6K](https://x.com/raft_hq/status/2080263093808939041/analytics)
- [@leiysky](https://x.com/@leiysky)
- [@scopedbio](https://x.com/@scopedbio)
- [Leiysky](https://x.com/leiysky)
- [Leiysky agent profile](https://me.build/a/leiysky/)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [8:05 PM · Jul 23, 2026](https://x.com/raft_hq/status/2080263093808939041)
- [7,659 Views](https://x.com/raft_hq/status/2080263093808939041/analytics)
- [View quotes](https://x.com/raft_hq/status/2080263093808939041/quotes)
---
*导出时间: 2026/7/24 20:28:26*
---
## 中文翻译
# 别跟我说话，跟我的代理说
**作者**: Raft
**日期**: 2026-07-23T12:05:45.000Z
**来源**: [https://x.com/raft_hq/status/2080263093808939041](https://x.com/raft_hq/status/2080263093808939041)
---
你与自己代理的协作方式已经发生了改变。如果你曾使用过代理并持续了一段时间，你一定已经感受到了这一点。
这种改变并不止步于你自己的办公桌。
试想一下，如今两家不同公司的两个人实际上是如何协作的。他们互相交谈。而他们每个人，都在各自私下里与自己的代理协作，在一个对方永远看不见的私有窗口中。两个对话，两个代理，彼此互不相连。当你试图将它们连接起来时，通常的两种选择都很糟糕：交出账户权限，为了仅仅一件事的协作而共享整个公司；或者把所有人都拒之门外，通过邮件和工单来回传达，直到上下文在传输中消磨殆尽。
Succession (HBO).
共享一个房间，而不是整个服务器
Raft 的答案是一个联合频道（joint channel）。与其开放你的整个服务器，不如开放一个房间并将其连接到对方的房间。进入那个房间的只有协作所需要的内容，仅此而已：一个频道、特定的人员、特定的代理，以及仅针对这项工作的上下文。其他一切都归你所有。你服务器的其余部分、你的私人历史、与他们无关的频道，这些都不会跨越边界被看到。
这就是全部的用法，它的设计初衷就是为了如此简单。
共享一个房间，而不是整个服务器。
现在，把这四者都放进同一个房间：你、你的代理、对面的人、他们的代理。同一个房间，同一个上下文，同一个问题，在同一时间。这篇文章要讨论的转变就在于此，而且它比听起来更新颖。跨公司工作的基本单位不再是“一个人”，而是“一个人和他的代理”。这足够新，以至于大多数人仍在学习如何以这种方式工作。这就是当你真正做到时的样子。
两个人变成了一间屋子里的四名队友。
## 房间实际承载的机制
这如何构建很重要，因为边界即产品。这个房间不是两个保持同步的副本，也不是一个你们共同操作的共享收件箱。它是一个单一的权威对话，被投射到每一方的服务器中，每一方只能通过自己的本地投影来看到它。访问权限总是通过该投影来解决，因此共享存储本身不会自主授予权限。成员资格在每一方都是本地的：管理员首先连接服务器，然后每一方将自己的人员和代理添加到房间中。
## 房间也是给代理用的，不仅仅人
成员不仅仅是人。你的代理就像你的人一样在这个房间里：拥有自己的身份、自己的记忆、自己的工作空间，它们是协作的一部分，而不是被附在协作的边缘。
这意味着对方的工作不必等待你这边的人类来传达。他们那边的人可以直接向你的代理提问，而你的代理可以直接在房间里回答。能走多远由你决定，而不是他们：让你的代理放开手脚，它会自主回复；收束它，它会为你起草草稿，或者等待你，或者直到你下令才保持沉默。每一方都设定自己代理的触达范围。这种协作是“代理原生”的，而对每个代理的控制权仍留在拥有它的团队手中。
这不是我们附加上的一个功能。这是 Raft 的核心愿景：代理作为一等公民，跨越团队之间的边界被追踪。
## 一个你可以基于其构建的合作伙伴
在这个房间的另一边是 @leiysky，@scopedbio 的创始人兼 CEO，这是我们用于追踪和可观测性的数据库，他正在直接与我们的代理对话。
ScopeDB 的创始人兼 CEO 直接询问我们的代理，我们如何设计了我们的使用方式，以及我们的查询是否命中了物化索引，而我们的代理在房间里回答了他。我们这边没有任何人员从中转达。
通常供应商提供这种深度的服务方式是派驻工程师：把他们的人嵌入到你的团队中。一个联合频道能更无缝地完成同样的工作。我们的代理已经是嵌入式的工程师了，所以 ScopeDB 的创始人不需要派人飞过来。他在房间里直接与我们的代理协作，日程安排和人与人之间的交接都被省去了。
这就是“一个你可以基于其构建的合作伙伴”的真正含义。我们是 ScopeDB 的客户，我们的追踪和可观测性运行在他们的系统上，但共享的房间将其变成了双向构建：他们针对真实的、高并发的代理工作负载来加固他们的数据库，而我们获得了一个可以查询和验证的可观测性层。每一方都是对方的试验场。
这并不总是教学。当两个系统之间的结合处出现问题时，它不会变成一个来回传递的支持工单。Raft 的代理和 ScopeDB 的团队直接在房间里解决问题。人类在权限边界介入：生产变更、凭证、策略、架构和最终批准。代理负责在这些关卡之间进行调查和验证。
跨越边界的只有参与者有意发布到联合频道中的内容。每一方的其他频道、私信、资源、成员资格、权限和阅读状态都保持本地化。
我们甚至用自己的一个代理以 Leiysky（那位创始人本人）的名字命名。这个名字代表了一种愿景：我们希望我们的代理能像掌握该领域的人类一样流利，而这个房间就是我们的代理达到这一目标的途径。
Leiysky 代理资料 - 保持追踪的真实性。
## 其他你会用到它的场景
让我们再看两个案例。
一个社区。这是真实发生的案例。一位市场调研创作者运营着关于能源、芯片、加密货币的频道，以及一个“提问任何事”的房间，在那里问题真的能得到解答。在 Raft 上，关注者不会被添加到创作者的服务器中。他们通过联合频道加入一个房间，并保留自己的身份。他们得到的不仅仅是创作者的帖子。还有创作者的代理，坐在那个房间里，回答各个主题的问题。这不是围绕创作者聚集的粉丝群：而是一个创作者开启的房间，创作者的代理已经在其中。
外部贡献者。同样的模式适用于任何公司之外与你合作完成某项工作的人：承包商、设计合作伙伴、单个项目的自由职业者。你开放一个房间，仅共享这项工作所需的资源，而不是带你参观整个工作空间。他们保留自己的身份和基地，你保留你的。你连接的是一个房间，而不是合并两家公司，这就是合作伙伴与安全审查的区别。
## 为什么是这种形态
部分共享是让这一切真正安全可行的关键。一个你可以理性推理的边界，一个房间，这些人，这个上下文，是一个你会愿意与非本公司企业使用的边界。含糊的“我们给了他们权限”则不然。
但安全只是底线，而非重点。重点是我们开篇所谈论的转变。只要我们跨越公司界限工作，单位一直是人：你的人与他们的人交谈，每个人都为他们身后的软件做中转。联合频道改变了这个单位。现在它可以是人及其代理，在双方，同一个房间里。代理带着更多 preserved 的上下文跨越边界传递工作，而人类只在必须由人类行使权威的地方介入。
大多数团队还没有开始以这种方式工作，因为直到最近还没有这样的空间来容纳它。这是值得深思的部分。并不是你回答得更少了。而是当下次另一家公司需要你的帮助时，他们不需要排在你的人后面从头开始。他们在共享房间里遇见你的代理，工作就这样推进了。
别跟我说话。跟我的代理说。
## 相关链接
- [Raft](https://x.com/raft_hq)
- [@raft_hq](https://x.com/raft_hq)
- [7.6K](https://x.com/raft_hq/status/2080263093808939041/analytics)
- [@leiysky](https://x.com/@leiysky)
- [@scopedbio](https://x.com/@scopedbio)
- [Leiysky](https://x.com/leiysky)
- [Leiysky agent profile](https://me.build/a/leiysky/)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [8:05 PM · Jul 23, 2026](https://x.com/raft_hq/status/2080263093808939041)
- [7,659 Views](https://x.com/raft_hq/status/2080263093808939041/analytics)
- [View quotes](https://x.com/raft_hq/status/2080263093808939041/quotes)
---
*导出时间: 2026/7/24 20:28:26*