二重奏是聊天机器人互动的未来
由人类所写。 不隶属于Anthropic.
我真的不想喜欢二重奏。 我不想成为Anthropic粉丝，但他们又这样做了。
我为Muse、Dot、NanoClaw以及其他许多个人协助型的用具付出了认真的努力。 Dutit是第一个觉得比乏味更有用的作品，因此
1. 速度快
其他的助理应用总是在做谁 -地狱 -知道什么在背景当我等待回应。 Dut显然优先考虑获得用户的快速响应，即使需要背景工作。 但我从未见过Opus在其它Claude UI中如此快地移动。 显然这里有些调音这对成为一个有用的助手至关重要：如果你想成为我的贝壳对于世界，我不会坐和抚摸我的拇指在命令之间。
2. 频道整洁
但我真的很喜欢Dut频道。 特别是：我喜欢Dutet能为我创建和管理频道。 与LLMs合作的一个乏味方面是试图跟踪聊天会话：工作流丢失，必须小心维护上下文，会话被误取名等。
二重奏为我安排了无聊的会议我的工作出现了一个自然的等级，我怀疑我会减少失去的线与二重奏。 Cmd -k已经对我反射了：它拉起各渠道的清单，让我迅速在它们之间互换。 频道也可以互相看见和参考，这样杜埃特就可以帮助我保持右行道的工作。
3. 准入政策是有意义的
Github repos的接入每个频道都受到限制。 我可以在一个特定的频道里增加几个相关的重置功能，不用担心该频道可能会从我的其他项目中混合工作。
也从未试图得到我的证书。 这是我的小宠物用大多数助理应用程序撒尿：在你把钥匙交给他们之前，Muse有一个认证商店，它至少使agent对数值视而不见，但它仍然可以在一些不可信的东西中输入这些。
Dut不存任何证书，并积极劝阻给予这些证书。 最多可以让您通过 Chrome 会话登录但是，它从来没有要求我这样做：它宁愿使用已经拥有的连接器生态系统Claude，而且似乎满足于留在它的航道上。
4. 答复简短
这并非杜埃特、多特和穆斯所独有，我总是要补充一些指示，试图说服我的agents给出简明的答复。 虽然我发现个性在这里有所改变：穆斯倾向于用拇指指指向一切，而杜埃特则用它来给我一个免责而无需进一步阐述，我觉得这令人愉快。
这是称
也肯定有些故障。 有时线程正在运行，但看不见。 agent启动和访问附件之间的竞争条件？
我也承认我的用例可能使Dut更适合我 Muse也许更适合别人 YMMV(英语：YMMV).
而多特仍然主导着语音交互。 Anthropic似乎并不在意对话语音模式
Dut已经取代了我大部分的AI工作流程
我并不真正喜欢管理agents的管理层：总是有些agent在某地等着我做决定或跟进一些任务。 我确信一些agent为我做了出色的工作
对我来说最重要的创新是关注的层次：Dut的顶层有鸟类的目光，这些渠道有更多的接入，但在更受限制的情况下。 由通道突起的子线在特定的密码沙盒中工作时，甚至可能进一步受限。 桌面应用程序可以到达我允许的本地主机，这通常只用于在云中进行编码后的QA或部署边缘。
大部分都是我喜欢的agents，类似的流量可能与一些胶片和API的信用被黑入。 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 Gem Box. All rights belong to the original author.