二重奏是聊天人互动的未来
由人类写成。 不隶属于Anthropic.
我真的不想喜欢二重奏。 我不想成为Anthropic粉丝，但他们又这样做了。
我为Muse, Dot, NanoClaw 和许多其他个人辅助型机具做出了认真的努力。 Dutit是第一个觉得比乏味更有用的作品，这就是为什么我目前喜欢这个。
1. 速度快
其他的助理应用程序总是在做谁知道什么在背景，而我等待一个答复。 Dut显然优先考虑获得用户的快速响应，即使需要背景工作。 但我从未见过Opus在其它Claude UI中如此迅速移动。 很明显这里有些调音这对成为一个有用的助手至关重要：如果你想成为我的贝壳对于世界，我不会坐和抚摸我的拇指在命令之间。
2. 频道整齐
但我真的很喜欢Dut频道。 尤其是：我喜欢Dutet能为我创建和管理频道。 与LLMs合作的一个乏味方面是试图跟踪聊天会话：工作流丢失，必须小心维护上下文，会议被误命名等。
杜埃特为我安排了无聊的会议我的工作已经出现了一个自然的等级，我想我会减少失去的线与杜埃特。 Cmd -k已经对我反射了：它拉出了频道的列表，让我在它们之间快速互换。 频道也可以互相看见和参考，这样Dutet就可以帮助我保持工作在右侧的航道。
3. 准入政策有意义
Github repos的接入每个频道都受到限制。 我可以在某个特定的频道上增加几个相关的重置功能，不用担心该频道可能会从我的其他项目中混合工作。
也从来没有试图得到我的证书。 我的宠物用大多数助理应用软件尿尿，Muse有一个证书商店，它至少使agent对数值视而不见，但它仍然可以在一些不可信的东西中输入这些。
二重奏不保存任何证书，并积极劝阻给予证书。 最多可以让你通过Chrome会议代表它登录但是，它从来没有要求我这样做：它宁愿使用已经拥有的连接器生态系统Claude，而且似乎满足于留在它的航道上。
4. 答复简短
这并非杜埃特、陶特和缪斯所独有，我总是要补充一些指示，试图说服我的agents作出简明的答复。 他们也可以在讯息中加入“反应”, Muse倾向于把一切都大拇指起来，而Dutt用它来给我一个好，而不进一步阐述，我觉得这很有趣。
这是称
也肯定有一些故障。 有时线程正在运行，但不可见。 agent启动和访问附件之间的竞争条件？
我也承认我的用例可能使Dut更适合我穆斯也许更适合别人 (原始内容存档于2018-09-21). YMMV.
而Dot仍然主导着语音交互。 Anthropic似乎根本不关心对话语音模式
Dut已经取代了我大部分的人工智能工作流程
我并不真正喜欢管理agents的管理层：总会有一些agent在某处等着我做决定或跟进一些任务。 我确信一些agent为我做了一件出色的工作
对我来说最重要的创新是关注的层次：Dut的顶级有鸟类的视线，这些频道载有更多的访问机会，但在更受限制的情况下。 在特定的密码沙盒中工作时，通过通道突起的子线甚至会受到进一步的限制。 桌面应用程序可以到达我允许的本地主机，通常只用于QA或部署边缘
多数情况都是我更喜欢安排agents, Dutit只是让这个等级体系成为核心产品的自然部分
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
Duet is the future of chatbot interaction
Written by a human. Not affiliated with Anthropic.
Look, I really didn’t want to like Duet. I don’t want to be an Anthropic fanboy and it annoys me when they do things better than the competition. But they have done it again.
I have given serious effort to Muse, Dot, NanoClaw, and a host of other personal-assistant-type harnesses. Duet is the first one that felt more useful than tedious, and it feels like a serious evolution of the chat experience rather than another “give me all your credentials to be useful” agent. Here’s why I like it so far.
1. It’s fast
Other assistant apps are always doing who-the-hell-knows-what in the background while I wait for a response. Duet clearly prioritizes getting a snappy response to the user even if background work is needed. It’s supposedly powered by Opus 5.5, but I’ve never seen Opus move this fast in other Claude UIs. Clearly some tuning went on here. This is critical to be a useful assistant: If you want to be my shell to the world, I am not going to sit and twiddle my thumbs between commands.
2. Channels are neat
Maybe I’m just Slack-brained, but I really like Duet channels. In particular: I like that Duet can create and manage channels for me. One tedious aspect of working with LLMs is trying to keep track of chat sessions: workstreams get lost, context must be carefully maintained, sessions get misnamed, etc.
Duet does the tedious session organizing for me. A natural hierarchy has emerged for my work, and I suspect I will have fewer lost threads with Duet. Cmd-k was already reflex for me: it pulls up the list of channels and lets me rapidly swap between them. Channels can also see and reference each other so Duet can help me keep work in the right lane.
3. Access policies are meaningful
Access to Github repos is restricted per channel. I can add a few related repos to a specific channel, and not worry that the channel might commingle work from my other projects.
It also never tries to get my credentials. This is my pet peeve with most assistant apps: they won’t do much until you hand them the keys. Muse has a credential store, which at least makes the agent blind to the values, but it could still enter those in something untrusted.
Duet stores no credentials and actively discourages being given them. At best it might let you login via a Chrome session on its behalf. But it has never asked me to do that: it prefers to use the connector ecosystem Claude already has, and seems content to stay in its lane otherwise.
4. Responses are short
This isn’t unique to Duet, Dot and Muse seem to get this too: Nobody wants to read a full page response to a simple question, which has been the de facto chatbot experience for years. I have always had to add a bunch of instructions trying to persuade my agents to give succinct responses. They all can also add emoji “reactions” to messages, though I find that personality makes a difference here: Muse tended to thumbs up everything, whereas Duet uses it to give me an okay without elaborating further, and I find that delightful.
THAT BEING SAID
It’s in beta, and definitely has some glitches. Sometimes threads are running but not visible. I’ve seen delegated repo access fail to attach correctly (race condition between agent start and access attachment?).
I also acknowledge my use-cases likely make Duet a better fit for me in particular. Muse might be a better fit for others. YMMV.
And Dot still reigns on voice interaction. Anthropic doesn’t even seem to care about having a conversational voice mode, it’s still just glorified speech-to-text.
Duet is already replacing most of my AI workflows
I don’t really enjoy the management side of managing agents: remembering who is running and with what context where. There is always some agent somewhere waiting on me to make a decision or follow up on some task. I’m sure some agent did brilliant work for me on a box somewhere that I’ve neglected and will be forgotten forever.
The innovation that matters to me most is the hierarchy of concerns: The top level of Duet has a bird’s eye view of all my workstreams, but no low-level access. The channels carry more access, but under more constrained context. Sub-threads spun up by the channels can be even further constrained as they work in specific code sandboxes. The Desktop app can reach local hosts where I let it, and that’s usually only for the QA or deployment edge after the coding is done in the cloud.
Most of this is how I already preferred to arrange my agents, and similar flows could be hacked together with some ducttape and API credits. Duet just makes this hierarchy a natural part of the core product, and it works so well that I suspect it’s going to be the default experience for all chatbot UIs in the near future.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.